DL 360 G5 blue screen USB error on server 2008 installation

Hi i am getting a error "USB, Blue screen followed by a memory dump while trying to install server 2008 on my DL360 G5, I have already tried the Smart start dvd (recommended to fix the problem on other forums) downloaded at the drivers web page for the server, i have the same problem. any help would be greatly appreciated bugcode_Usb_drivererror

Hi:
You may also want to post your question in the HP Business Support Forum -- DL Servers Section.
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264

Similar Messages

  • Blue Screen Crashes in Windows Server 2008

    Our Windows 2008 server which has been running fine for several years now has started to record a series of blue screen crashes in the past week, almost daily.  Our hosting company ran a chkdsk and didn't find any errors. The also ran an sfc scan which
    they said identified and fixed several system files, however we are still seeing blue screen crashes.
    I have put the minidump from the latest crash in my public skydrive folder at -
    https://skydrive.live.com/?cid=446280106bb642de#cid=446280106BB642DE&id=446280106BB642DE%21140
    Can anyone help me identify the problem that is causing the blue screen crashes?
    Thanks,
    Gary
    Gary Frickey

    Hi,
    Gary
    Regarding to Dump files that you provided, I have used WinDbg tool to analysis them. For more detailed results, please refer to the following.
    1.Analyze 120213-41636-01.dump
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 1A, {5200, fffffa80130e0000, ac326f8a3564698d, ac366f8a3564698d}
    Probably caused by : volsnap.sys ( volsnap!VspDoubleBufferIncomingWrite+9a )
    Followup: MachineOwner
    4: kd> !analyze -v
    * Bugcheck Analysis *
    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005200, The subtype of the bugcheck.
    Arg2: fffffa80130e0000
    Arg3: ac326f8a3564698d
    Arg4: ac366f8a3564698d
    Debugging Details:
    BUGCHECK_STR: 0x1a_5200
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: mcupdate.exe
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from fffff802e920536f to fffff802e9076440
    STACK_TEXT:
    fffff880`0d61bcb8 fffff802`e920536f : 00000000`0000001a 00000000`00005200 fffffa80`130e0000 ac326f8a`3564698d : nt!KeBugCheckEx
    fffff880`0d61bcc0 fffff802`e90be5a6 : 00000000`00000000 00000000`00001000 00000000`00000200 fffffa80`13ac14d0 : nt! ?? ::FNODOBFM::`string'+0x2f301
    fffff880`0d61bd00 fffff802`e928c81c : 00000000`00000000 fffff802`e92a8a00 fffff880`133792c0 00000000`00000200 : nt!ExpAllocateBigPool+0xd6
    fffff880`0d61bde0 fffff880`01dab74a : 00000000`00000001 fffff880`121da000 00000000`00001000 fffff880`01da9e2d : nt!ExAllocatePoolWithTag+0x80a
    fffff880`0d61beb0 fffff880`01da9372 : fffffa80`13e738b8 fffffa80`13e73560 fffffa80`0aaaf160 00000000`00000000 : volsnap!VspDoubleBufferIncomingWrite+0x9a
    fffff880`0d61bf00 fffff880`00a26b69 : fffff880`0d61c000 fffffa80`1340db00 fffffa80`06cc4ab0 fffff8a0`24ebd3c8 : volsnap!VolsnapWriteFilter+0x361
    fffff880`0d61bf50 fffff802`e9070b67 : fffff880`0da372c8 00000000`0361e4d8 00000000`03610000 00000000`77a675a4 : Ntfs!NtfsStorageDriverCallout+0x16
    fffff880`0d61bf80 fffff802`e9070b2d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
    fffff880`13378700 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    volsnap!VspDoubleBufferIncomingWrite+9a
    fffff880`01dab74a 488bf8 mov rdi,rax
    SYMBOL_STACK_INDEX: 4
    SYMBOL_NAME: volsnap!VspDoubleBufferIncomingWrite+9a
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: volsnap
    IMAGE_NAME: volsnap.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 51a9661e
    IMAGE_VERSION: 6.2.9200.16628
    BUCKET_ID_FUNC_OFFSET: 9a
    FAILURE_BUCKET_ID: 0x1a_5200_volsnap!VspDoubleBufferIncomingWrite
    BUCKET_ID: 0x1a_5200_volsnap!VspDoubleBufferIncomingWrite
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x1a_5200_volsnap!vspdoublebufferincomingwrite
    FAILURE_ID_HASH: {c0542499-747b-bb38-39b0-9680350f4757}
    2.Analyze 120213-42713-01.dump
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 24, {b50019060b, fffff8800e413e38, fffff8800e413670, fffff802e26a85cc}
    Probably caused by : memory_corruption ( nt!MiReleaseReadListResources+14 )
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
    Arguments:
    Arg1: 000000b50019060b
    Arg2: fffff8800e413e38
    Arg3: fffff8800e413670
    Arg4: fffff802e26a85cc
    Debugging Details:
    EXCEPTION_RECORD: fffff8800e413e38 -- (.exr 0xfffff8800e413e38)
    ExceptionAddress: fffff802e26a85cc (nt!MiReleaseReadListResources+0x0000000000000014)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    CONTEXT: fffff8800e413670 -- (.cxr 0xfffff8800e413670;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=fffbfa80138f7f80
    rdx=fffffa8009fa3e81 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802e26a85cc rsp=fffff8800e414070 rbp=0000000000000000
    r8=fffffa8009fa3e80 r9=0000000000000001 r10=fffff802e249c610
    r11=fffffa8012e1b010 r12=fffffa8006d92ef0 r13=fffffa80074e29c0
    r14=fffbfa80138f7f80 r15=0000000000000001
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    nt!MiReleaseReadListResources+0x14:
    fffff802`e26a85cc 4883792800 cmp qword ptr [rcx+28h],0 ds:002b:fffbfa80`138f7fa8=????????????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=fffbfa80138f7f80
    rdx=fffffa8009fa3e81 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802e26a85cc rsp=fffff8800e414070 rbp=0000000000000000
    r8=fffffa8009fa3e80 r9=0000000000000001 r10=fffff802e249c610
    r11=fffffa8012e1b010 r12=fffffa8006d92ef0 r13=fffffa80074e29c0
    r14=fffbfa80138f7f80 r15=0000000000000001
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    nt!MiReleaseReadListResources+0x14:
    fffff802`e26a85cc 4883792800 cmp qword ptr [rcx+28h],0 ds:002b:fffbfa80`138f7fa8=????????????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: TrustedInstall
    CURRENT_IRQL: 0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: ffffffffffffffff
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802e256b168
    GetUlongFromAddress: unable to read from fffff802e256b1f8
    ffffffffffffffff
    FOLLOWUP_IP:
    nt!MiReleaseReadListResources+14
    fffff802`e26a85cc 4883792800 cmp qword ptr [rcx+28h],0
    FAULTING_IP:
    nt!MiReleaseReadListResources+14
    fffff802`e26a85cc 4883792800 cmp qword ptr [rcx+28h],0
    BUGCHECK_STR: 0x24
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from fffff802e2305e46 to fffff802e26a85cc
    STACK_TEXT:
    fffff880`0e414070 fffff802`e2305e46 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiReleaseReadListResources+0x14
    fffff880`0e4140a0 fffff802`e22fea09 : 00000000`00005000 fffff980`2cb80000 00000000`00005000 00000000`00000000 : nt!MmWaitForCacheManagerPrefetch+0x42
    fffff880`0e4140e0 fffff802`e26af71f : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`0e4141e0 : nt!CcFetchDataForRead+0xe9
    fffff880`0e414130 fffff802`e2304e3e : fffffa80`06d92ef0 00000000`00000000 00000000`00040000 00000000`00004301 : nt!CcMapAndCopyFromCache+0xcf
    fffff880`0e4141d0 fffff880`01903b58 : fffff8a0`06e3cc50 fffffa80`074b86b0 00000000`00000000 00000000`00000000 : nt!CcCopyReadEx+0xfe
    fffff880`0e414240 fffff880`0191a91a : 00000000`00000000 fffff880`0e4144a0 00000000`00060900 fffff8a0`06e3cc50 : Ntfs!NtfsCachedRead+0x148
    fffff880`0e4142b0 fffff880`0191c42b : fffffa80`0f799a10 fffffa80`074b86b0 00000000`00000001 fffffa80`074b8600 : Ntfs!NtfsCommonRead+0x68a
    fffff880`0e414470 fffff880`016e34ee : fffffa80`074a3010 fffffa80`074b86b0 fffffa80`074b86b0 fffffa80`074b8a50 : Ntfs!NtfsFsdRead+0x1db
    fffff880`0e414520 fffff880`016e10b6 : fffffa80`098479a0 fffffa80`074e29c0 fffffa80`074b86b0 fffff802`e24b3140 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x25e
    fffff880`0e4145c0 fffff802`e267e868 : 00000000`00000000 fffff880`0e4146a1 fffffa80`074e29c0 00000000`00000018 : fltmgr!FltpDispatch+0xb6
    fffff880`0e414620 fffff802`e26ae513 : fffffa80`074e29c0 fffff8a0`028ca000 ffffffff`800012c4 fffffa80`074e29c0 : nt!IopSynchronousServiceTail+0x158
    fffff880`0e4146f0 fffff802`e26f415a : fffff880`000004a2 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x661
    fffff880`0e4147f0 fffff802`e26ef1bf : fffff880`0e414918 00000000`00000003 fffff802`e2665870 fffff802`e248310e : nt!PfSnGetPrefetchInstructions+0x19a
    fffff880`0e414900 fffff802`e26f1935 : fffffa80`074be080 fffff880`0e4149e0 00000000`00000000 fffff880`0e414a30 : nt!PfSnBeginScenario+0x18f
    fffff880`0e4149b0 fffff802`e26a0070 : fffffa80`074be080 00000000`3cc531e5 fffff880`0e414cc0 fffffa80`074be080 : nt!PfSnBeginAppLaunch+0x115
    fffff880`0e414a70 fffff802`e268c2cf : fffffa80`074be080 fffffa80`0723c6e0 00000000`00000000 fffffa80`07110080 : nt!PfProcessCreateNotification+0x70
    fffff880`0e414aa0 fffff802`e22f4915 : fffff880`02e57180 fffffa80`07110080 fffff802`e268c1cc fffffa80`07110080 : nt!PspUserThreadStartup+0x103
    fffff880`0e414b00 fffff802`e22f4897 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
    fffff880`0e414c40 000007fd`9e59d5e8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
    000000c9`60f5fa28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fd`9e59d5e8
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: nt!MiReleaseReadListResources+14
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 51a966cd
    IMAGE_VERSION: 6.2.9200.16628
    STACK_COMMAND: .cxr 0xfffff8800e413670 ; kb
    IMAGE_NAME: memory_corruption
    BUCKET_ID_FUNC_OFFSET: 14
    FAILURE_BUCKET_ID: 0x24_nt!MiReleaseReadListResources
    BUCKET_ID: 0x24_nt!MiReleaseReadListResources
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x24_nt!mireleasereadlistresources
    FAILURE_ID_HASH: {12e84aa1-b4fa-6138-fa2a-d3b77e82b2b2}
    3.Analyze 120213-48687-01.dump
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck C2, {d, fffff901007059c0, 64704344, fffbfa8015d6a940}
    Probably caused by : win32k.sys ( win32k!W32pProcessCallout+86 )
    Followup: MachineOwner
    2: kd> !analyze -v
    * Bugcheck Analysis *
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 000000000000000d, type of pool violation the caller is guilty of.
    Arg2: fffff901007059c0
    Arg3: 0000000064704344
    Arg4: fffbfa8015d6a940
    Debugging Details:
    OVERLAPPED_MODULE: Address regions for 'dump_iaStor' and 'dump_iaStor.' overlap
    FAULTING_IP:
    win32k!W32pProcessCallout+86
    fffff960`0014bad6 33d2 xor edx,edx
    BUGCHECK_STR: 0xc2_d
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: WerFault.exe
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from fffff80295c78027 to fffff80295a60440
    STACK_TEXT:
    fffff880`10ffe908 fffff802`95c78027 : 00000000`000000c2 00000000`0000000d fffff901`007059c0 00000000`64704344 : nt!KeBugCheckEx
    fffff880`10ffe910 fffff960`0014bad6 : fffff901`007059c0 fffffa80`15d6adb0 fffff901`007059c0 00000000`64704344 : nt!ExFreePoolWithTag+0xec7
    fffff880`10ffe9f0 fffff960`00184630 : fffff880`10ffeb40 fffffa80`15d6a940 00000000`00000000 00000000`00000000 : win32k!W32pProcessCallout+0x86
    fffff880`10ffea20 fffff802`95e9db5a : fffffa80`15d6a940 fffffa80`15d6adb0 00000000`00000000 00000000`00000008 : win32k!W32CalloutDispatch+0x2f1
    fffff880`10ffea80 fffff802`95e72004 : fffffa80`0a18ed20 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ExCallCallBack+0x3a
    fffff880`10ffeab0 fffff802`95e9d86d : 00000000`00000000 fffffa80`15d6a901 00000000`00000000 fffffa80`152d7080 : nt!PspExitThread+0x414
    fffff880`10ffebd0 fffff802`95a5f453 : fffffa80`15d6a940 fffffa80`152d7080 fffff880`10ffecc0 00000000`7f62b000 : nt!NtTerminateProcess+0xfd
    fffff880`10ffec40 000007fd`bb652eaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00cde078 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fd`bb652eaa
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    win32k!W32pProcessCallout+86
    fffff960`0014bad6 33d2 xor edx,edx
    SYMBOL_STACK_INDEX: 2
    SYMBOL_NAME: win32k!W32pProcessCallout+86
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME: win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5216eef4
    IMAGE_VERSION: 6.2.9200.16699
    BUCKET_ID_FUNC_OFFSET: 86
    FAILURE_BUCKET_ID: 0xc2_d_win32k!W32pProcessCallout
    BUCKET_ID: 0xc2_d_win32k!W32pProcessCallout
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0xc2_d_win32k!w32pprocesscallout
    FAILURE_ID_HASH: {9d5e1858-9d8c-dc1b-8469-c4e8abf71b98}
    Based on the above prompt messages, you can refer to the following article and get detailed information of Bug Check 1A, Bug Check 24 and Bug Check C2.
    Bug Check 0x1A: MEMORY_MANAGEMENT
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557391%28v=vs.85%29.aspx
    Bug Check 0x24: NTFS_FILE_SYSTEM
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557433(v=vs.85).aspx
    Bug Check 0xC2: BAD_POOL_CALLER
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff560185(v=vs.85).aspx
    Based on current state, I suggest you should update volsnap.sys and win32k.sys drivers. Then check if this issue can be solved. Meanwhile, you also should check the memory
    in your computer. For detailed operations, please refer to the following article.
    Run Diagnostics to Check Your System for Memory Problems
    http://technet.microsoft.com/en-us/magazine/ff700221.aspx
    If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist
    with your request.
    To obtain the phone numbers for specific technology request, please refer to the web site listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
    Hope this helps.
    Best regards,                                                                                   
    Justin Gu

  • My macbook13in has a blue screen with error code 10813

    my macbook 13in has a blue screen with error code 10813

    Reinstalling OS X Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall OS X: Select Reinstall OS X and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    Also see:
    Reinstall OS X Without Erasing the Drive
    OS X Yosemite- Reinstall OS X
    OS X Mavericks- Reinstall OS X
    OS X Mountain Lion- Reinstall OS X
    OS X Lion- Reinstall Mac OS X
         Note: You will need an active Internet connection. I suggest using Ethernet
                     if possible because it is three times faster than wireless.

  • Blue screen with error code and I have no recovery disks for HP Pavilion dv6-1260se

    I have a HP Pavilion dv6-1260se with factory installed operating system of Vista. When booting up the computer, I receive a blue screen with this error message: STOP:  c000021a {Fatal System Error}.
                                                                The verification of a KnownDLL failed.  system process terminated unexpectedly with
                                                                 a status of 0x0000221  (0x007fb9c0  0x00000000).
                                                                 The system has been shut down.
    I do not have recovery disks for this computer.  I tried to order them but them seem to not be available.  This is my daughter's computer.  She says she started to have trouble after downloading Frost Wire (music share) and then she removed it.  We tried going back to an earlier time and that didn't help and then the blue screen with error message appeared. What do I do now?
    This question was solved.
    View Solution.

    Hi,
    Assuming your in the US, recovery discs are available to order for that model here.  That may be the best option.
    You should also be able to do a recovery without the discs as well.  Take a look at this document: Recover Windows Vista Operating System Using HP Recovery, and look for the section Restore the PC to its original condition with the HP Recovery Manager if Windows Vista is not accessible.  This should allow you to recover the PC.
    R
    Although I am an HP Employee, I am speaking for myself and not for HP.

  • Restarting After a Blue Screen Stop Error

    I have received a Blue Screen Stop Error on my Toshiba Satellite 5200 Series laptop.
    I could report it here, in full, if that would be helpful. However, it begins by telling me to restart the machine but the unit's Power button is not allowing me to switch it off.
    What action should I take ?

    Crikey ! Someone at another forum just told me to hold the button down for 5 seconds..... and it worked !

  • Satellite A350 - Blue screen with error message

    When starting windows7, I am getting blue screen with error message 0x0000116.
    Can anyone assist please?

    It looks like a graphic card driver is a trouble maker.Try to reinstall a graphic card driver in safe mode (f8 on startup). Read this article for information:
    http://social.answers.microsoft.com/Forums/en-US/vistahardware/thread/eb584685-6b8b-4ad7-b6cc-ae5ee78095fb
    It's for VISTA but should be the same for win 7 too.

  • Blue screen fatal error messages - laptop always crashes and now won't even let me restore

    My dv6920ea laptop has developed a fault and keeps crashing with blue screen errors, such as "IRQL_NOT_LESS_OR_EQUAL". The problem has become so bad that it happens everytime I turn the laptop on. The laptop ran "Windows memory diagnostic tool" which said that there was a hardware fault. I've tried running a full system recovery to factory setting but sometimes the laptop crashes, and when it doesn't it asks me to insert a windows disc, but my laptop didn't come with one. The laptop is a year and a half old. What can I do to fix this issue? I don't mind completely recovering the laptop to factory settings and I have most(!) of my files backed up.

    Hello djbless,
    You’re getting blue screens with error IRQL_NOT_LESS_OR_EQUAL.
    Run diagnostics to make sure that you are not having a problem with any of the hardware.
    Turn off the computer.
    As you power it back on tap the F2 key. This will load hardware diagnostics.
    Run the startup test.
    Go to HP.com and update the drivers, there is a button that says Let HP scan your system for out-of-date and missing drivers and software
    Here is a link to the updates.
    Clicking the White Kudos star on the left is a way to say Thanks!
    Let me know how everything goes.
    Have a good day.

  • Blue screen with error message

    Product Name: HP Media Center M7250n Desktop PC
    Product #ED842aa-aba
    I have been getting a blue screen with error messages that ask if this is the first time i get the error and then at the end it says it is dumping memory. I would like to wipe my harddrive and reinstall XP but my system is out of warrenty and HP won't provide me a recovery CD. What are my options.
    This question was solved.
    View Solution.

    Hi,
           You are most welcome. 
    "I work for HP."
    Please click the "White Kudos" star to say thanks for helping.
    Please mark "Accept As Solution" if my help has solved your problem.

  • Hp g6-1278sa get blue screen and error message when trying to load xp pro

    I have setup a new 500gb toshiba SATA 2 harddrive to run daul boot.
    Windows XP pro 32bit and windows 64bit.
    Unable to install XP pro, just goes into error and blue screen.
    Ive removed the harddrive and placed it in my Packard Bell, loaded XP pro 32bit and win 8 64bit with no problem, and both run fine.
    Removed the harddrive from the packard bell laptop and place it back into the HP g6-1278sa, daul boot screen on start up.
    Opptions windows 8 or earlyer windows.
    Windows 8 works fine.
    Windows XP pro starts to load and then we get the blue screen with error message.

    Hi     Powlers
       Ok read this tutorial ( link below ) in how to install XP within Windows 8 OR running Virtual Machine 
        http://www.howtogeek.com/171395/how-to-get-windows-xp-mode-on-windows-8/
                                                                                                    OR
        http://www.fixedbyvonnie.com/2014/03/legally-install-windows-xp-free-windows-8-using-virtualbox/
              Quick question :: What operating system was your machine shipped with initially ??? Windows 7 ???
                                                           Checkurtech
    ****Click the White Kudos star to say thanks****
    ****Please mark Accept As Solution if it solves your problem****

  • Microsoft Report Viewer Redistributable 2008 setup encountered Error on Server 2008 R2 Enterprise

    Hi,               
    I need help Microsoft Report Viewer Redistributable 2008 setup encountered Error on Server 2008 R2 Enterprise.  I tried to install many time failed every
    time. Please advise how I fix this issue
    After click OK
    Here is the next error message

    This one might sort it.
    http://support.microsoft.com/kb/970652
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Win7 can't boot in USB hard drive blue screen 7b error,but can boot when use PD8

    Install Win7 64bit in a USB hard drive through some tools,when start windows the microsoft logo appear,get blue screen.
    ***stop:0x0000007B(0x80786B58,0xC0000034,0x00000000,0x00000000)
    problem has been detected and windows has been shut down to prevent  damage to your computer.If  this is the first you've seen this stop  error screen restart your computer .If this screen appears again.follow these steps:Check for viruses on  your computer.Remove any newly hard drives or hard drive  controllers.Check your hard drive to make sure it is  properly.Configured and terminated.Run DCHKDSK/F to check for hard  drive corrption,and then restart your computer.
    Technical:
    ***stop:0x0000007B(0x80786B58,0xC0000034,0x00000000,0x00000000)
    But when use Parallels Desktop 8 My boot camp ,the win7 can boot normally.
    Any solution?
    Thank you.

    Hi,
    If this issue is related with firmare, then it's recommend to contact the vender\manufacture, if you got any update of this issue, we'd be appreciate that you could share your experience with us.
    Regards
    Yolanda Zhu
    TechNet Community Support

  • MSI 770-C45 locking up/blue screening/other errors on boot

    I recently built a new HTPC and have been having allot of problems getting it to boot.  It may take 10-15min of trying to boot up over and over with random blue screens, lockups, or errors that the C drive needs to be checked for consistency before Windows will finally load up and work.  At first I thought it was a bad drive, but according to Western Digital’s HDD Diag util, both the controller and the drives surface checks out OK.  I just wiped the drive out and reinstalled Windows 7 again, and this time went with IDE instead of AHCI, hoping it was a driver issue.  It only worked well for a day before the same problems started rearing their ugly head again.
    At this point I don’t know if I have a memory issue, a CMOS setting wrong (which are All Auto), or what.  I hoping someone here might have an idea of what this problem could be.   
    My system specs: 
    MSI 770-C45 Motherboard -  BIOS v1.9 05182010
    AMD Phenom II X4 945 Deneb 3.0GHz 4 x 512KB L2 Cache 6MB L3 Cache Socket AM3 95W Quad-Core Processor HDX945WFGIBOX
    4GB RAM – Memory Master-2-Pack 2GB PC3-10666 DDR3 DIMM Memory Kit-MMD4096KD3-1333 SKU: 9360032
    MSI R4550-MD1GH Radeon HD 4550 1GB 64-bit GDDR3 PCI Express 2.0 x16
    Drive C: - Western Digital 320GB WD3200AAKS
    Drive D: - Western Digital 1.5TB WD15EARS
    Linksys WUSB54GC v3 Wireless USB Adapter
    Windows 7 64bit Enterprise
    All recent MSI 770 and Radeon Drivers

    Quote from: Mavrick007 on 23-July-10, 02:39:51
    According to MSI, my motherboard supports the following modules:
    DDR3 800/1066/1333/1600*(OC)
    http://www.msi.com/index.php?func=prodmbspec&maincat_no=1&cat2_no=171&cat3_no=656&prod_no=1812
    This are the speeds of the DDR 3 RAM supported ,1600Mhz beeing done with overclocking ,because the CPU memory controller is no able to do 1600 by default.
    Quote from: Mavrick007 on 23-July-10, 02:39:51
    When I look at the test results for my Motherboard:
    http://www.msi.com/uploads/test_report/TR10_1812.pdf
     I see 1333 RAM list like PC11000 DDR III RAM (DDR-1333).  However, If I go to a site like Bestbuy or NewEgg and search for DDR3 1333, it shows results like Corsair - 2-Pack 2GB PC3-10666 DDR3 DIMM Memory Kit.  I see PC3-10666 and PC3-10600, but nothing for PC11000.
    The only mention of 1333 modules on the test report is for 1333 OC
    When you see the PC 11000 DDR3 or PC3 10666 specifications they are refering to the theoretical bandwidth ,it s related to the frequency of course ,but it s something else it s a data rate.Its wikipedia but it s good enough -> http://en.wikipedia.org/wiki/DDR_3 Some specs are atipical like 10666 ,marketing thngyes
    Search the internet for memory that works ok with your CPU ,look for "real" DDR 3 1066Mhz or DDR 3 1333Mhz."real" means that that memory should be able to run at those frequencies without voltage increase over the default one.Usually when a memory vendor says you need to increase voltage for a specific frequency it means that you overclock and that there is no warranty they will work in your configuration.
    So you need DDR 3 1066Mhz or DDR 3 1333Mhz ,it needs to be AMD tested memory and it needs to be a known to work RAM on MSI motherboards timings wise.Look up on newegg and see what works.
    The performance gaps between 1066 and 1333 are small in real practice and you can overcome some loss by using a "real" DDR 3 1066Mhz , tweaking different timings ,using Command Rate of 1T for example ( you may "feel" it smoother in desktop than a 1333Mhz at 2T).

  • Apple iPhone 5S blue screen and error 14 while restoring

    Got my new iPhone 5S for 2 weeks. Suddenly he became to show blue screen of death and restore after about an hour. I read, that it can be caused by iWork apps, but i didn`t even open them. After another blue screen iPhone moved in a cyclic reboot. Tried to restore via itunes, but never finished because of blue screen when installing iOS and occured error #14. Tried many hints, but still haven`t solution. Please help!

    i`ve tried all hints. disabled antivirus and firewall. cleaned hosts, many usb ports, 2 pc`s (win7). in dfu mode error 40 appears.

  • Blue Screen and error 14 to Restore

    my iphone 5s present esta Problem and remains stuck in DFU mode, so WHEN I connect a Blue Screen Restore it and THEN Presents Presents Error 14 ... someone help me with this problem

    Hi carpeiron,
    Welcome to the Apple Support Communities!
    I understand that you are experiencing a blue screen on your iPhone 5s and furthermore when you try to restore, you receive error 14. Error 14 can come up for either a USB related issue or a Hardware issue. Please use the attached article to troubleshoot this restore error 14. 
    Resolve iOS update and restore errors - Apple Support
    Best regards,
    Joe

  • Blue Screen + Spotlight error message... I can't reboot!

    Hi All,
    Upon startup, iMac with 2+GB RAM running OS X 10.5.6 does the following:
    1. Normal startup chime
    2. Blue screen appears
    3. Spotlight error message "Spotlight quit unexpectedly"
    I can't reboot, or boot in Safe Mode or launch Disk Utility from DVD and obviously I can't reinstall Leopard
    I'm really frustrated
    Message was edited by: Pacopeluca

    Pacopeluca wrote:
    I can't do any of that
    If you're really holding down those keys immediately after pressing the power button, yet they don't behave as expected, you may have some sort of hardware problem.
    Do you have access to another keyboard that you could try?
    How is that keyboard connected to your iMac? Your iMac probably has three USB ports. I'd try the keyboard in each of them in turn.

Maybe you are looking for