Windows rebooted from a bug check..

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff8026303b73e).
Hello! I've been having bluescreens for about 2 months now. I thought it was my graphic card so I bought a new one and that did not work. I've formatted 4 times - running Windows 8.1 w/ all updates. Any deciphering of the bug check would be great, thanks
for your time.

KMODE_EXCEPTION_NOT_HANDLED (1e)
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
BugCheck 1E, {ffffffffc0000005, fffff80307127fd8, 0, ffffffffffffffff}
1: kd> ln fffff80307127fd8
(fffff803`07127ad0) nt!MiResolveProtoPteFault+0x508 | (fffff803`071283e0) nt!MiCompleteProtoPteFault
The exception occurred in nt!MiResolveProtoPteFault+0x508.
1: kd> kv
Child-SP RetAddr : Args to Child : Call Site
ffffd000`22e9ed88 fffff803`07219d47 : 00000000`0000001e ffffffff`c0000005 fffff803`07127fd8 00000000`00000000 : nt!KeBugCheckEx
ffffd000`22e9ed90 fffff803`071dabc2 : 00000000`c64430c0 fffff803`07332420 00000000`0000007d ffffe000`c5ada638 : nt! ?? ::FNODOBFM::`string'+0x3a897
ffffd000`22e9f480 fffff803`071d90fe : 00000000`0000043d 00007ffb`890e3001 ffff0000`00000001 0000ffff`fffff000 : nt!KiExceptionDispatch+0xc2
ffffd000`22e9f660 fffff803`07127fd8 : ffffe000`c9361dd8 00007ffb`890e3e88 00000001`60c4f021 ffffe000`c9361dd8 : nt!KiGeneralProtectionFault+0xfe (TrapFrame @ ffffd000`22e9f660)
ffffd000`22e9f7f0 fffff803`0712638d : fffff6e0`00da6610 00007ffb`8901a13c fffff6bf`fdc480d0 ffffe000`c9361dd8 : nt!MiResolveProtoPteFault+0x508
ffffd000`22e9f890 fffff803`070e258a : ffffe000`c94b1880 00007ffb`8901a13c ffffe000`c94b1880 ffffe000`00000000 : nt!MiDispatchFault+0x29d
ffffd000`22e9f9c0 fffff803`071d922f : 00000000`00000008 00000000`037cfb30 ffffe000`c94b1801 ffffd000`22e9fb00 : nt!MmAccessFault+0x36a
ffffd000`22e9fb00 00007ffb`8901a13c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f (TrapFrame @ ffffd000`22e9fb00)
00000000`206fda78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`8901a13c
1: kd> .trap ffffd000`22e9f660
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000073752860 rbx=0000000000000000 rcx=e000c93bf5780460
rdx=0000000000165396 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80307127fd8 rsp=ffffd00022e9f7f0 rbp=0000000000000000
r8=0000058000000000 r9=ffffe000c9361dd8 r10=ffffd00022e9fb00
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiResolveProtoPteFault+0x508:
fffff803`07127fd8 488b3f mov rdi,qword ptr [rdi] ds:00000000`00000000=????????????????
1: kd> u @rip
nt!MiResolveProtoPteFault+0x508:
fffff803`07127fd8 488b3f mov rdi,qword ptr [rdi]
fffff803`07127fdb 4885ff test rdi,rdi
fffff803`07127fde 0f841efcffff je nt!MiResolveProtoPteFault+0x132 (fffff803`07127c02)
fffff803`07127fe4 488bc7 mov rax,rdi
fffff803`07127fe7 4883e0f8 and rax,0FFFFFFFFFFFFFFF8h
fffff803`07127feb 4883f808 cmp rax,8
fffff803`07127fef 0f840dfcffff je nt!MiResolveProtoPteFault+0x132 (fffff803`07127c02)
fffff803`07127ff5 400fb6c7 movzx eax,dil
fffff803`07127d12 0f84f0020000 je nt!MiResolveProtoPteFault+0x538 (fffff803`07128008)
fffff803`07127d18 480fbae708 bt rdi,8
fffff803`07127d1d 0f82f0020000 jb nt!MiResolveProtoPteFault+0x543 (fffff803`07128013)
fffff803`07127d23 4c8bc3 mov r8,rbx
fffff803`07127d26 49c1e805 shr r8,5
fffff803`07127d2a 4183e01f and r8d,1Fh
fffff803`07127d2e 4184d9 test r9b,bl
fffff803`07127d31 0f857c370e00 jne nt! ?? ::FNODOBFM::`string'+0x2c003 (fffff803`0720b4b3)
fffff803`07127d37 488b442448 mov rax,qword ptr [rsp+48h]
fffff803`07127d3c 488d0dade1f5ff lea rcx,[nt!MiReadWrite (fffff803`07085ef0)]
Verify Flags Level 0x0002092b
STANDARD FLAGS:
[X] (0x00000000) Automatic Checks
[X] (0x00000001) Special pool
[X] (0x00000002) Force IRQL checking
[X] (0x00000008) Pool tracking
[ ] (0x00000010) I/O verification
[X] (0x00000020) Deadlock detection
[ ] (0x00000080) DMA checking
[X] (0x00000100) Security checks
[X] (0x00000800) Miscellaneous checks
[X] (0x00020000) DDI compliance checking
We have Driver Verifier enabled at the time of the crash, yet we have a ton of memory related stuff going on, and an exception occurring in one as well. Although Memtest failed, at this point I am going to say we're either not catching a problematic low-level
driver causing corruption, or we have a RAM/motherboard problem despite Memtest passing.
1. Uninstall any/all Asus bloatware (AI Suite, PC Probe, etc... whatever you have).
2. Uninstall/disable the nVidia Streaming Service ASAP.
3. If the above fails, faulty RAM and/or motherboard. Although before definitely concluding this, I'd try a BIOS update if available.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

Similar Messages

  • Windows 2003 Memory Dump - Bug check Analysis attached

    Hi all
    I recently have had a Windows 2003 Standard with SP2 server crash with a memory dump
     I have used WinDBG to read the file and output below
    can anyone shed any light on the faults, or point me in the right direction?
    *                        Bugcheck Analysis                                   
    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8081c630, The address that the exception occurred at
    Arg3: b7487c30, Trap Frame
    Arg4: 00000000
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    nt!IoGetAttachedDevice+c
    8081c630 8b4810          mov     ecx,dword ptr [eax+10h]
    TRAP_FRAME:  b7487c30 -- (.trap 0xffffffffb7487c30)
    ErrCode = 00000000
    eax=000007f6 ebx=85e76068 ecx=000007f6 edx=00000000 esi=85e76068 edi=89d42020
    eip=8081c630 esp=b7487ca4 ebp=b7487ca4 iopl=0         nv up ei pl nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
    nt!IoGetAttachedDevice+0xc:
    8081c630 8b4810          mov     ecx,dword ptr [eax+10h] ds:0023:00000806=????????
    Resetting default scope
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    BUGCHECK_STR:  0x8E
    PROCESS_NAME:  DocTransport.ex
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
    LAST_CONTROL_TRANSFER:  from 8082db20 to 80827f7d
    STACK_TEXT: 
    b74877fc 8082db20 0000008e c0000005 8081c630 nt!KeBugCheckEx+0x1b
    b7487bc0 8088c12a b7487bdc 00000000 b7487c30 nt!KiDispatchException+0x3a2
    b7487c28 8088c0de b7487ca4 8081c630 badb0d00 nt!CommonDispatchException+0x4a
    b7487ca4 8081c7e1 89d42020 b7487d64 00000000 nt!KiExceptionExit+0x186
    b7487cb8 808f44c7 85e76068 b7487d64 08a9ea50 nt!IoGetRelatedDeviceObject+0x63
    b7487d38 8088b658 00001e20 00000000 00000000 nt!NtReadFile+0x55
    b7487d38 7c82845c 00001e20 00000000 00000000 nt!KiSystemServicePostCall
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    08a9ea8c 00000000 00000000 00000000 00000000 0x7c82845c
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    nt!IoGetAttachedDevice+c
    8081c630 8b4810          mov     ecx,dword ptr [eax+10h]
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  nt!IoGetAttachedDevice+c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrpamp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  51d4c567
    IMAGE_VERSION:  5.2.3790.5190
    FAILURE_BUCKET_ID:  0x8E_nt!IoGetAttachedDevice+c
    BUCKET_ID:  0x8E_nt!IoGetAttachedDevice+c
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x8e_nt!iogetattacheddevice+c
    FAILURE_ID_HASH:  {22c1c728-5bf3-efb9-fff4-40d5ae0d47e2}
    Followup: MachineOwner

    Hi,
    For Bug Check 0x8E, it
    indicates that a kernel-mode application generated an exception that the error handler did not catch. For more details, please refer to following article and check if can help you.
    Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Did you remember that which operation (or any change) you do before this issue occurred? Or just the server
    crashed suddenly?
    Please check if all necessary updates were installed and drivers were updated.
    à
    PROCESS_NAME: 
    DocTransport.exe
    Did you install any third-party application on the server? Please
    perform a clean boot and monitor the result.
    By the way, as you know, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. However, it is not
    effective for us to debug the crash dump file here in the forum. 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

  • Windows 8.1 rebooting overnight with a bug check

    Windows 8.1 is rebooting overnight with a bug check in the system logs.
    Event files saved:
    https://onedrive.live.com/redir?resid=7DE1274A30A8AE63!1788&authkey=!AGhpLBq-8hDqCok&ithint=file%2c.zip
    I also tried verifier to check out device drivers but could not figure out how to use it.  I got it configured and started, but did not know what to do once the computer rebooted....   Sounds like I need to download a windows debugger and
    so I thought I would start with the event log files.  Any link on how to interpret the even logs, dump or mini dump files?
    Thanks,
    Ross

    Hi,
    According to the Event Log:
    Session "ReadyBoot" stopped due to the following error: 0xC0000188
    After that:
    The previous system shutdown at 7:07:39 PM on ‎6/‎3/‎2014 was unexpected.
    This problem probably caused by ReadyBoot problem, While you needn't worry about it,
    The logging of this error will not affect the operation of your computer.  ReadyBoot is used by the ReadyBoost service that optimizes the boot time of your computer to a minimum.
    You can refer to the link below for more details about this error:
    http://support.microsoft.com/kb/2001347
    In addition, I found another error message in your event log:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000020, 0xffffc0016d9657f0, 0xffffc0016d966040, 0x000000000585000a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060314-18953-01.
    If you still need assistance about this problem, please upload the memory.dmp file and share with us. We would help you try to analysize this log to find further reason of this problem.
    Roger Lu
    TechNet Community Support

  • Event ID 1001 Bug check Occurred, After updation of Kaspersky Windows 7

    Hi, 
    Recently I have updated my Anti Virus Kaspersky 10 on my Windows 7 Ultimate System 32 bit. After that it restart automatically  again and again. Then i restore it on Last known good configuration. It resolve the issue. In event viewr i found out the
    Error 1001 Bug check .. 
    I exactly want to know that what happened to my system . For this How can i send my dmp files to support team . 
    I have face the problem non my multiple systems but not all .. . 
    Please guide me asap . 

    The following log occurred 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c9 (0x0000024d, 0x9047b25a, 0x8d5ed0b8, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041714-22230-01.
    when i run verifier.exe 
    and select " Create standard Setting"  then select "Automatically select drivers build for older version of windows" and press Next
    it display the Kl1.sys driver 
    what does it means .. is there any problem with this file?

  • The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xe3045048, 0x00000000, 0x819c02bf, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: %3.

    Hello Guys,
    I hope someone can help me with this error.  I have been searching from forums but typically, causes and resolutions are generalized.  This is the first time it happened on our Win 2008 Server and we have not installed any (hardware/Software/Drivers)
    for the past 3 years.
    We do install monthly security patches and that is it...  This server of ours is running on VM (VMWARE).
    I hope you can shed light as I do not understand crash dumps..
    Thank you
    ===============================
    Opened log file 'c:\debuglogrlo.txt'
    3: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    3: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e3045048, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 819c02bf, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 00000000, (reserved)
    Debugging Details:
    READ_ADDRESS:  e3045048
    FAULTING_IP:
    nt!CmpCheckKey+61b
    819c02bf 394724          cmp     dword ptr [edi+24h],eax
    MM_INTERNAL_CODE:  0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre
    TRAP_FRAME:  8d9bf9ec -- (.trap 0xffffffff8d9bf9ec)
    .trap 0xffffffff8d9bf9ec
    ErrCode = 00000000
    eax=00000000 ebx=cecec024 ecx=3162f75f edx=00000035 esi=b52b1940 edi=e3045024
    eip=819c02bf esp=8d9bfa60 ebp=8d9bfa8c iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!CmpCheckKey+0x61b:
    819c02bf 394724          cmp     dword ptr [edi+24h],eax ds:0023:e3045048=????????
    .trap
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 81891de4 to 818dc292
    STACK_TEXT: 
    8d9bf9d4 81891de4 00000000 e3045048 00000000 nt!MmAccessFault+0x10b
    8d9bf9d4 819c02bf 00000000 e3045048 00000000 nt!KiTrap0E+0xdc
    8d9bfa8c 819c681a 01000001 009c4020 009c3f70 nt!CmpCheckKey+0x61b
    8d9bfabc 819c6e48 b52b1940 01000001 00000006 nt!CmpCheckRegistry2+0x8c
    8d9bfb04 819c186e 01000001 8d9bfc60 80002f38 nt!CmCheckRegistry+0xf5
    8d9bfb60 819c3fdd 8d9bfbb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    8d9bfbd8 819c627d 8d9bfc60 00000000 8d9bfc4c nt!CmpInitHiveFromFile+0x19e
    8d9bfc18 819bc4c5 8d9bfc60 00000000 8d9bfc7b nt!CmpCmdHiveOpen+0x36
    8d9bfd14 819bc6fa 00000002 8193c5a0 00000002 nt!CmpFlushBackupHive+0x2fd
    8d9bfd38 81a9bcbd 8194613c 84da3020 818e9d4a nt!CmpSyncBackupHives+0x90
    8d9bfd44 818e9d4a 00000000 00000000 84da3020 nt!CmpPeriodicBackupFlushWorker+0x32
    8d9bfd7c 81a1a01c 00000000 bcf90a9f 00000000 nt!ExpWorkerThread+0xfd
    8d9bfdc0 81882eee 818e9c4d 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    nt!CmpCheckKey+61b
    819c02bf 394724          cmp     dword ptr [edi+24h],eax
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  nt!CmpCheckKey+61b
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrpamp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  51da1840
    IMAGE_VERSION:  6.0.6002.18881
    FAILURE_BUCKET_ID:  0x50_nt!CmpCheckKey+61b
    BUCKET_ID:  0x50_nt!CmpCheckKey+61b
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x50_nt!cmpcheckkey+61b
    FAILURE_ID_HASH:  {b0c48432-dfba-c9e0-33fc-874f17d1f0e6}
    Followup: MachineOwner
    eax=8d948120 ebx=00000000 ecx=81944200 edx=000003f0 esi=8d94813c edi=00000000
    eip=818dc292 esp=8d9bf960 ebp=8d9bf9d4 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000202
    nt!MmAccessFault+0x10b:
    818dc292 8b03            mov     eax,dword ptr [ebx]  ds:0023:00000000=????????
    ChildEBP RetAddr  Args to Child             
    8d9bf9d4 81891de4 00000000 e3045048 00000000 nt!MmAccessFault+0x10b
    8d9bf9d4 819c02bf 00000000 e3045048 00000000 nt!KiTrap0E+0xdc (FPO: [0,0] TrapFrame @ 8d9bf9ec)
    8d9bfa8c 819c681a 01000001 009c4020 009c3f70 nt!CmpCheckKey+0x61b
    8d9bfabc 819c6e48 b52b1940 01000001 00000006 nt!CmpCheckRegistry2+0x8c
    8d9bfb04 819c186e 01000001 8d9bfc60 80002f38 nt!CmCheckRegistry+0xf5
    8d9bfb60 819c3fdd 8d9bfbb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    8d9bfbd8 819c627d 8d9bfc60 00000000 8d9bfc4c nt!CmpInitHiveFromFile+0x19e
    8d9bfc18 819bc4c5 8d9bfc60 00000000 8d9bfc7b nt!CmpCmdHiveOpen+0x36
    8d9bfd14 819bc6fa 00000002 8193c5a0 00000002 nt!CmpFlushBackupHive+0x2fd
    8d9bfd38 81a9bcbd 8194613c 84da3020 818e9d4a nt!CmpSyncBackupHives+0x90
    8d9bfd44 818e9d4a 00000000 00000000 84da3020 nt!CmpPeriodicBackupFlushWorker+0x32 (FPO: [1,0,2])
    8d9bfd7c 81a1a01c 00000000 bcf90a9f 00000000 nt!ExpWorkerThread+0xfd
    8d9bfdc0 81882eee 818e9c4d 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
    start    end        module name
    8060e000 80615000   kdcom    kdcom.dll    Sat Apr 11 14:25:29 2009 (49E037D9)
    80615000 80685000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Apr 11 14:23:19 2009 (49E03757)
    80685000 80696000   PSHED    PSHED.dll    Sat Apr 11 14:25:32 2009 (49E037DC)
    80696000 8069e000   BOOTVID  BOOTVID.dll  Sat Jan 19 15:27:15 2008 (4791A653)
    8069e000 806df000   CLFS     CLFS.SYS     Sat Apr 11 12:13:51 2009 (49E018FF)
    806df000 807bf000   CI       CI.dll       Sat Apr 11 14:25:22 2009 (49E037D2)
    807d7000 807e5000   WDFLDR   WDFLDR.SYS   Thu Jul 26 10:36:38 2012 (5010AD36)
    807e5000 807fc000   dfsc     dfsc.sys     Thu Apr 14 22:59:03 2011 (4DA70BB7)
    81811000 81844000   hal      halmacpi.dll Sat Apr 11 12:13:13 2009 (49E018D9)
    81844000 81bfe000   nt       ntkrpamp.exe Mon Jul 08 09:39:12 2013 (51DA1840)
    81e01000 81f0c000   NDIS     NDIS.SYS     Sat Apr 11 12:45:52 2009 (49E02080)
    81f0c000 81f37000   msrpc    msrpc.sys    Sat Apr 11 12:37:32 2009 (49E01E8C)
    81f37000 81f72000   NETIO    NETIO.SYS    Sat Apr 11 12:46:21 2009 (49E0209D)
    81f72000 81ff3000   Wdf01000 Wdf01000.sys Sat Jun 22 10:29:37 2013 (51C50C11)
    8c805000 8c84b000   acpi     acpi.sys     Sat Apr 11 12:19:03 2009 (49E01A37)
    8c84b000 8c854000   WMILIB   WMILIB.SYS   Sat Jan 19 13:53:08 2008 (47919044)
    8c854000 8c85c000   msisadrv msisadrv.sys Sat Jan 19 13:32:51 2008 (47918B83)
    8c85c000 8c883000   pci      pci.sys      Sat Apr 11 12:19:16 2009 (49E01A44)
    8c883000 8c892000   partmgr  partmgr.sys  Sat Apr 11 12:39:19 2009 (49E01EF7)
    8c892000 8c894900   compbatt compbatt.sys Sat Jan 19 13:32:47 2008 (47918B7F)
    8c895000 8c89f000   BATTC    BATTC.SYS    Sat Jan 19 13:32:45 2008 (47918B7D)
    8c89f000 8c8ae000   volmgr   volmgr.sys   Sat Jan 19 13:49:51 2008 (47918F7F)
    8c8ae000 8c8f8000   volmgrx  volmgrx.sys  Sat Apr 11 12:39:25 2009 (49E01EFD)
    8c8f8000 8c8ff000   intelide intelide.sys Sat Jan 19 13:49:42 2008 (47918F76)
    8c8ff000 8c90d000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 12:39:09 2009 (49E01EED)
    8c90d000 8c91cb80   vmci     vmci.sys     Tue May 01 09:12:40 2012 (4F9F3888)
    8c91d000 8c92d000   mountmgr mountmgr.sys Sat Jan 19 13:49:13 2008 (47918F59)
    8c92d000 8c93a580   vsock    vsock.sys    Sat Sep 29 12:59:03 2012 (50668017)
    8c93b000 8c943000   atapi    atapi.sys    Sat Apr 11 12:39:09 2009 (49E01EED)
    8c943000 8c961000   ataport  ataport.SYS  Sat Apr 11 12:39:10 2009 (49E01EEE)
    8c961000 8c979000   lsi_sas  lsi_sas.sys  Sat Jun 30 09:01:01 2007 (4685AB4D)
    8c979000 8c9ba000   storport storport.sys Sat Apr 11 12:39:19 2009 (49E01EF7)
    8c9ba000 8c9ec000   fltmgr   fltmgr.sys   Sat Apr 11 12:13:59 2009 (49E01907)
    8ca0d000 8ca6c000   SYMDS    SYMDS.SYS    Tue Jul 24 06:57:53 2012 (500DD6F1)
    8ca6c000 8ca95000   vsepflt  vsepflt.sys  Tue Oct 30 18:37:14 2012 (508FADDA)
    8ca95000 8cb7d000   SYMEFA   SYMEFA.SYS   Thu Oct 04 02:59:21 2012 (506C8B09)
    8cb7d000 8cbef000   ksecdd   ksecdd.sys   Sat Jun 02 05:56:07 2012 (4FC93A77)
    8cc0a000 8ccf4000   tcpip    tcpip.sys    Fri Jul 05 10:08:19 2013 (51D62A93)
    8ccf4000 8cd0f000   fwpkclnt fwpkclnt.sys Sat Apr 11 12:45:42 2009 (49E02076)
    8cd0f000 8cd16e00   storflt  storflt.sys  Sun Nov 18 10:29:44 2007 (473FA398)
    8cd17000 8cd2a000   i8042prt i8042prt.sys Sat Jan 19 13:49:17 2008 (47918F5D)
    8cd2a000 8cd35000   mouclass mouclass.sys Sat Jan 19 13:49:14 2008 (47918F5A)
    8cd35000 8cd4d000   parport  parport.sys  Sat Jan 19 13:49:32 2008 (47918F6C)
    8cd4d000 8cd67000   serial   serial.sys   Sat Jan 19 13:49:34 2008 (47918F6E)
    8cd67000 8cd71000   serenum  serenum.sys  Sat Jan 19 13:49:29 2008 (47918F69)
    8cd71000 8cd7c000   fdc      fdc.sys      Sat Jan 19 13:49:37 2008 (47918F71)
    8cd7c000 8cd94000   cdrom    cdrom.sys    Sat Apr 11 12:39:17 2009 (49E01EF5)
    8cd94000 8cdc2000   vm3dmp   vm3dmp.sys   Fri Oct 19 02:55:17 2012 (50805095)
    8cdc2000 8cdd8000   tdx      tdx.sys      Sat Apr 11 12:45:56 2009 (49E02084)
    8cdd8000 8cdf6000   EraserUtilRebootDrv EraserUtilRebootDrv.sys Thu Oct 10 04:46:53 2013 (5255C0BD)
    8ce09000 8cf19000   Ntfs     Ntfs.sys     Sun Mar 03 05:02:58 2013 (51326902)
    8cf19000 8cf52000   volsnap  volsnap.sys  Thu Aug 16 21:53:34 2012 (502CFB5E)
    8cf52000 8cf5a000   spldr    spldr.sys    Fri Jun 22 08:29:17 2007 (467B17DD)
    8cf5a000 8cf69000   mup      mup.sys      Sat Apr 11 12:14:12 2009 (49E01914)
    8cf69000 8cf7a000   disk     disk.sys     Sat Apr 11 12:39:14 2009 (49E01EF2)
    8cf7a000 8cf9b000   CLASSPNP CLASSPNP.SYS Sat Apr 11 12:39:05 2009 (49E01EE9)
    8cf9b000 8cfab000   agp440   agp440.sys   Sat Jan 19 13:32:49 2008 (47918B81)
    8cfab000 8cfb4000   crcdisk  crcdisk.sys  Sat Jan 19 13:50:29 2008 (47918FA5)
    8cfe3000 8cfee000   tunnel   tunnel.sys   Sat Jan 19 13:55:50 2008 (479190E6)
    8cfee000 8cff9000   kbdclass kbdclass.sys Sat Jan 19 13:49:14 2008 (47918F5A)
    8cff9000 8cffa380   vmmouse  vmmouse.sys  Mon Jun 04 17:15:28 2012 (4FCC7CB0)
    92404000 924a4000   dxgkrnl  dxgkrnl.sys  Thu Aug 01 09:31:36 2013 (51F9BA78)
    924a4000 924b0000   watchdog watchdog.sys Sat Apr 11 12:22:43 2009 (49E01B13)
    924b0000 924cd000   E1G60I32 E1G60I32.sys Wed Aug 08 00:14:13 2007 (46B89A55)
    924cd000 924d0780   CmBatt   CmBatt.sys   Sat Jan 19 13:32:47 2008 (47918B7F)
    924d1000 924e0000   intelppm intelppm.sys Sat Jan 19 13:27:20 2008 (47918A38)
    924e0000 924e0c80   lmimirr  lmimirr.sys  Wed Apr 11 06:32:11 2007 (461C106B)
    924e1000 92502000   VIDEOPRT VIDEOPRT.SYS Sat Jan 19 13:52:10 2008 (4791900A)
    92502000 92531000   msiscsi  msiscsi.sys  Sat Apr 11 12:40:07 2009 (49E01F27)
    92531000 9253c000   TDI      TDI.SYS      Sat Jan 19 13:57:10 2008 (47919136)
    9253c000 92553000   rasl2tp  rasl2tp.sys  Sat Jan 19 13:56:33 2008 (47919111)
    92553000 9255e000   ndistapi ndistapi.sys Sat Jan 19 13:56:24 2008 (47919108)
    9255e000 92581000   ndiswan  ndiswan.sys  Sat Apr 11 12:46:31 2009 (49E020A7)
    92581000 92590000   raspppoe raspppoe.sys Sat Apr 11 12:46:30 2009 (49E020A6)
    92590000 925a4000   raspptp  raspptp.sys  Sat Jan 19 13:56:34 2008 (47919112)
    925a4000 925b9000   rassstp  rassstp.sys  Sat Apr 11 12:46:40 2009 (49E020B0)
    925b9000 925e3000   SYMEVENT SYMEVENT.SYS Wed Aug 22 13:32:47 2012 (50346EFF)
    925e3000 925f1000   Npfs     Npfs.SYS     Sat Apr 11 12:14:01 2009 (49E01909)
    92a0a000 92a93000   rdpdr    rdpdr.sys    Sat Apr 11 12:52:32 2009 (49E02210)
    92a93000 92aa3000   termdd   termdd.sys   Sat Apr 11 12:51:14 2009 (49E021C2)
    92aa3000 92aa4380   swenum   swenum.sys   Sat Jan 19 13:49:20 2008 (47918F60)
    92aa5000 92acf000   ks       ks.sys       Sat Apr 11 12:38:47 2009 (49E01ED7)
    92acf000 92ad9000   mssmbios mssmbios.sys Sat Jan 19 13:32:55 2008 (47918B87)
    92ad9000 92ae6000   umbus    umbus.sys    Sat Jan 19 13:53:40 2008 (47919064)
    92ae6000 92af0000   flpydisk flpydisk.sys Sat Jan 19 13:49:37 2008 (47918F71)
    92af0000 92b01000   NDProxy  NDProxy.SYS  Sat Jan 19 13:56:28 2008 (4791910C)
    92b01000 92b25000   ccSetx86 ccSetx86.sys Fri Aug 17 05:15:38 2012 (502D62FA)
    92b25000 92bb8000   SRTSP    SRTSP.SYS    Fri Nov 02 04:14:38 2012 (5092D82E)
    92bb8000 92bc8000   SRTSPX   SRTSPX.SYS   Wed Nov 16 06:27:18 2011 (4EC2E746)
    92bc8000 92bf5000   Ironx86  Ironx86.SYS  Tue Jul 24 08:34:17 2012 (500DED89)
    93600000 93609000   rasacd   rasacd.sys   Sat Jan 19 13:56:31 2008 (4791910F)
    93609000 93790e00   NAVEX15  NAVEX15.SYS  Fri Aug 23 03:57:57 2013 (52166D45)
    937a9000 937b7000   SymEPSecFlt SymEPSecFlt.sys Wed Mar 14 22:36:50 2012 (4F60AD02)
    937b7000 937c0000   Fs_Rec   Fs_Rec.SYS   Wed Feb 29 21:32:36 2012 (4F4E28F4)
    937c0000 937c7000   Null     Null.SYS     Sat Jan 19 13:49:12 2008 (47918F58)
    937c7000 937ce000   Beep     Beep.SYS     Sat Jan 19 13:49:10 2008 (47918F56)
    937ce000 937d5980   vmrawdsk vmrawdsk.sys Sat Mar 23 22:24:00 2013 (514DBB00)
    937d6000 937e2000   vga      vga.sys      Sat Jan 19 13:52:06 2008 (47919006)
    937e2000 937ea000   RDPCDD   RDPCDD.sys   Sat Jan 19 14:01:08 2008 (47919224)
    937ea000 937f2000   rdpencdd rdpencdd.sys Sat Jan 19 14:01:09 2008 (47919225)
    937f2000 937fd000   Msfs     Msfs.SYS     Sat Jan 19 13:28:08 2008 (47918A68)
    97c0d000 97c69000   SYMTDIV  SYMTDIV.SYS  Sat Jul 21 10:01:00 2012 (500A0D5C)
    97c69000 97c7d000   smb      smb.sys      Sat Apr 11 12:45:22 2009 (49E02062)
    97c7d000 97cc5000   afd      afd.sys      Thu Apr 21 21:58:25 2011 (4DB03801)
    97cc5000 97cf7000   netbt    netbt.sys    Sat Apr 11 12:45:35 2009 (49E0206F)
    97cf7000 97d00000   ws2ifsl  ws2ifsl.sys  Sat Jan 19 13:56:49 2008 (47919121)
    97d00000 97d16000   pacer    pacer.sys    Sat Apr 11 12:45:51 2009 (49E0207F)
    97d16000 97d24000   netbios  netbios.sys  Sat Jan 19 13:55:45 2008 (479190E1)
    97d24000 97d46700   vmhgfs   vmhgfs.sys   Sat Mar 23 22:17:43 2013 (514DB987)
    97d47000 97d5a000   wanarp   wanarp.sys   Sat Jan 19 13:56:31 2008 (4791910F)
    97d5a000 97d96000   rdbss    rdbss.sys    Sat Apr 11 12:14:26 2009 (49E01922)
    97d96000 97da0000   nsiproxy nsiproxy.sys Sat Jan 19 13:55:50 2008 (479190E6)
    97da0000 97dff000   eeCtrl   eeCtrl.sys   Thu Oct 10 04:46:53 2013 (5255C0BD)
    9800e000 9811d000   BHDrvx86 BHDrvx86.sys Fri Mar 14 10:34:18 2014 (53226AAA)
    9811d000 9812a000   crashdmp crashdmp.sys Sat Apr 11 12:39:12 2009 (49E01EF0)
    9812a000 98134000   dump_diskdump dump_diskdump.sys Sat Apr 11 12:39:11 2009 (49E01EEF)
    98134000 9814c000   dump_LSI_SAS dump_LSI_SAS.sys Sat Jun 30 09:01:01 2007 (4685AB4D)
    9814c000 98156000   Dxapi    Dxapi.sys    Sat Jan 19 13:36:12 2008 (47918C4C)
    98156000 98165000   monitor  monitor.sys  Sat Jan 19 13:52:19 2008 (47919013)
    98165000 98180000   luafv    luafv.sys    Sat Jan 19 13:30:35 2008 (47918AFB)
    98180000 981ab000   ofant    ofant.sys    Tue Nov 22 03:55:32 2011 (4ECAACB4)
    981ab000 981b5000   LMIRfsDriver LMIRfsDriver.sys Tue Jul 15 00:26:22 2008 (487B7E2E)
    9d440000 9d646000   win32k   win32k.sys   Fri Feb 07 18:38:29 2014 (52F4B7A5)
    9d660000 9d669000   TSDDD    TSDDD.dll    Sat Jan 19 14:01:09 2008 (47919225)
    9d680000 9d68e000   cdd      cdd.dll      Thu Aug 01 10:49:32 2013 (51F9CCBC)
    a0606000 a06b6000   spsys    spsys.sys    Wed Mar 11 01:10:28 2009 (49B69F04)
    a06b6000 a06c6000   lltdio   lltdio.sys   Sat Jan 19 13:55:03 2008 (479190B7)
    a06c6000 a06d9000   rspndr   rspndr.sys   Sat Jan 19 13:55:03 2008 (479190B7)
    a06d9000 a06f2000   bowser   bowser.sys   Tue Feb 22 21:23:54 2011 (4D63B8EA)
    a06f2000 a0713000   mrxdav   mrxdav.sys   Sat Apr 11 12:14:39 2009 (49E0192F)
    a0713000 a0732000   mrxsmb   mrxsmb.sys   Fri Apr 29 21:24:39 2011 (4DBABC17)
    a0732000 a076b000   mrxsmb10 mrxsmb10.sys Wed Jul 06 23:31:46 2011 (4E147FE2)
    a076b000 a0783000   mrxsmb20 mrxsmb20.sys Fri Apr 29 21:24:41 2011 (4DBABC19)
    a0783000 a07f0000   HTTP     HTTP.sys     Sun Feb 21 04:53:31 2010 (4B804BCB)
    a07f0000 a07f7000   parvdm   parvdm.sys   Sat Jan 19 13:49:28 2008 (47918F68)
    a07f7000 a07f9080   vmmemctl vmmemctl.sys Sat Mar 23 22:23:46 2013 (514DBAF2)
    a07fa000 a07fb800   RaInfo   RaInfo.sys   Sat Jan 05 02:57:12 2008 (477E8188)
    a4808000 a48e6000   peauth   peauth.sys   Mon Oct 23 16:55:32 2006 (453C8384)
    a48e6000 a48f0000   secdrv   secdrv.SYS   Wed Sep 13 21:18:32 2006 (45080528)
    a48f0000 a490d000   srvnet   srvnet.sys   Fri Apr 29 21:25:08 2011 (4DBABC34)
    a490d000 a4919000   tcpipreg tcpipreg.sys Wed Dec 09 01:26:18 2009 (4B1E8C3A)
    a4919000 a491ce80   vstor2_mntapi10_shared vstor2-mntapi10-shared.sys Fri Nov 05 02:33:35 2010 (4CD2FC7F)
    a491d000 a4945000   srv2     srv2.sys     Fri Apr 29 21:25:09 2011 (4DBABC35)
    a4945000 a4994000   srv      srv.sys      Fri Feb 18 22:03:28 2011 (4D5E7C30)
    a4994000 a49aa000   cdfs     cdfs.sys     Sat Jan 19 13:28:02 2008 (47918A62)
    a49aa000 a49b3000   asyncmac asyncmac.sys Sat Jan 19 13:56:29 2008 (4791910D)
    a49b3000 a49c3000   fileinfo fileinfo.sys Sat Jan 19 13:34:27 2008 (47918BE3)
    a49dd000 a49f2000   NAVENG   NAVENG.SYS   Fri Aug 23 03:59:23 2013 (52166D9B)
    Unloaded modules:
    a49c8000 a49dd000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    93609000 93791000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    a49b3000 a49c8000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    93609000 93791000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    a49dd000 a49f2000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    93609000 93791000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    a49c8000 a49dd000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    93609000 93791000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    a49b3000 a49c8000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    93609000 93791000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    a49dd000 a49f2000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    93609000 93791000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    a49c8000 a49dd000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    93609000 93791000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    a49b3000 a49c8000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    93609000 93791000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    93794000 937a9000   NAVENG.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00015000
    9360c000 93794000   NAVEX15.SYS
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00188000
    8cfb4000 8cfc1000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000D000
    8cfc1000 8cfcb000   dump_storport.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000A000
    8cfcb000 8cfe3000   dump_LSI_SAS.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00018000
    807bf000 807d7000   sacdrv.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00018000
    Closing open log file c:\debuglogrlo.txt

    Hi,
    Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM
    cache, or video RAM).
    Another common cause is the installation of a faulty system service.
    Antivirus software can also trigger this error, as can a corrupted NTFS volume.
    Try the solution provided in this article:
    Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx
    And this one:
    Stop error message in Windows 7 or Windows Server 2008 R2: "Stop error code 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)" or "Stop error code 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA)"
    http://support.microsoft.com/kb/979538
    Hope this helps.

  • Computer has rebooted from a bugcheck windows 8.1

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe001ad9b05d8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\021715-15656-01.dmp. Report Id: 021715-15656-01.
    My computer is rebooting and that's the error I'm getting in the event viewer. A link to the dump can be found below. Please help and thank you.

    Patrick
    Better and no worries it happens
    These are called BCC124 and are related to hardware.  Read how to diagnose and hopefully to fix them read this
    wiki
    Since they refer to "authentic AMD" I would start by running a CPU stress test
    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\021715-15656-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is:
    SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    Machine Name:
    Kernel base = 0xfffff802`cca1a000 PsLoadedModuleList = 0xfffff802`cccf0370
    Debug session time: Tue Feb 17 08:37:15.708 2015 (UTC - 5:00)
    System Uptime: 0 days 0:00:06.408
    Loading Kernel Symbols
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, ffffe001ad9b05d8, 0, 0}
    Probably caused by : AuthenticAMD
    Followup: MachineOwner
    0: kd> !analyze -v
    * Bugcheck Analysis *
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe001ad9b05d8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR: 0x124_AuthenticAMD
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    STACK_TEXT:
    ffffd000`e116f500 fffff802`ccd9ffd0 : ffffd000`e5950180 ffffe001`ad9b05b0 fffff802`cccff800 fffff802`cca9a339 : nt!WheapCreateLiveTriageDump+0x81
    ffffd000`e116fa30 fffff802`ccbde454 : ffffe001`ad9b05b0 ffffd000`e116fb50 fffff802`cccff8e0 ffffe001`ab557880 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
    ffffd000`e116fa60 fffff802`ccbdf271 : fffff802`cccff8e0 ffffd000`e116fb50 fffff802`cccff8e0 ffffd000`e116fb50 : nt!WheapProcessWorkQueueItem+0x48
    ffffd000`e116faa0 fffff802`cca895e3 : fffff802`ccf2ed20 fffff802`ccbdf24c ffffc001`7f38d280 ffffe001`ab557880 : nt!WheapWorkQueueWorkerRoutine+0x25
    ffffd000`e116fad0 fffff802`ccb18e70 : 00000000`00000000 ffffe001`ab557880 ffffe001`ab557880 ffffe001`ab4ac040 : nt!ExpWorkerThread+0x293
    ffffd000`e116fb80 fffff802`ccb6f7c6 : fffff802`ccd1a180 ffffe001`ab557880 fffff802`ccd73a00 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`e116fbe0 00000000`00000000 : ffffd000`e1170000 ffffd000`e1169000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME: AuthenticAMD
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    IMAGE_VERSION:
    FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_bus_prv
    FAILURE_ID_HASH: {6fd7875b-9a1b-9e09-d6d6-816026a875c8}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Need hotfix for BUG Check reboots for 2012R2

    I have 5 Node cluster of 2012R2 which will go to production in next few days, but am struck with the Bug check issue, which reboots atleast 3 nodes frequently. Am aware of this bug check and know the hotfixes for 2012 and 2008. However am not able to find
    the hotfix  or steps to resolve this issue on 2012r2.
    Need assistance to fix this problem.
    Thanks in advance, below the debug report.
    3: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    USER_MODE_HEALTH_MONITOR (9e)
    One or more critical user mode components failed to satisfy a health check.
    Hardware mechanisms such as watchdog timers can detect that basic kernel
    services are not executing. However, resource starvation issues, including
    memory leaks, lock contention, and scheduling priority misconfiguration,
    may block critical user mode components without blocking DPCs or
    draining the nonpaged pool.
    Kernel components can extend watchdog timer functionality to user mode
    by periodically monitoring critical applications. This bugcheck indicates
    that a user mode health check failed in a manner such that graceful
    shutdown is unlikely to succeed. It restores critical services by
    rebooting and/or allowing application failover to other servers.
    Arguments:
    Arg1: ffffe8010a271900, Process that failed to satisfy a health check within the
     configured timeout
    Arg2: 00000000000004b0, Health monitoring timeout (seconds)
    Arg3: 0000000000000005
    Arg4: 0000000000000000
    Debugging Details:
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    ADDITIONAL_DEBUG_TEXT: 
    You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
    MODULE_NAME: netft
    FAULTING_MODULE: fffff80021089000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  5215f788
    PROCESS_OBJECT: ffffe8010a271900
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  0x9E
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
    LAST_CONTROL_TRANSFER:  from fffff800a291ac08 to fffff800211dcfa0
    STACK_TEXT: 
    ffffd001`d60c6938 fffff800`a291ac08 : 00000000`0000009e ffffe801`0a271900 00000000`000004b0 00000000`00000005 : nt!KeBugCheckEx
    ffffd001`d60c6940 fffff800`a291a892 : 00000000`00000000 00000000`00000000 ffffd001`d601c180 ffffe001`1f716ec8 : netft+0x2c08
    ffffd001`d60c6980 fffff800`210e2810 : ffffd001`d60c6b00 ffffe001`1f716ec8 ffffe001`24e7d220 ffffd001`d601c180 : netft+0x2892
    ffffd001`d60c69b0 fffff800`211e0aea : ffffd001`d601c180 ffffd001`d601c180 ffffd001`d6028dc0 ffffe001`24e7d080 : nt!KeRemoveQueueEx+0x3b80
    ffffd001`d60c6c60 00000000`00000000 : ffffd001`d60c7000 ffffd001`d60c1000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2efa
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    netft+2c08
    fffff800`a291ac08 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  netft+2c08
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  netft.sys
    BUCKET_ID:  WRONG_SYMBOLS
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:wrong_symbols
    FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
    Followup: MachineOwner
    ndraj

    Hi, 
    Try to install all recommended cluster hot-fixes to stop further BSODs. Bug check ID 0x9E is recorded for this shutdown & image name netft.sys cause of server shutdown.
    As suggested in
    similar kind of thread netft.sys is driver of MS Cluster Virtual Adapter. Try to to update firmware/drivers of NICs.
    Here is another useful link for your reference 
    Regards, Ravikumar P

  • Updated documentation for "Bug Check 0xDA: SYSTEM_PTE_MISUSE" for Windows 7?

    Hi,
    I upgraded my Vista x64 (Dell Optiplex 755) to Windows 7 RTM and I'm getting the above bug check. The following site nicely describes the various bug check parameters - http://msdn.microsoft.com/en-us/library/ms796150.aspx - but I don't see an entry for parameter 1 that I'm seeing (504). I assume the 504 is new for Windows 7? If anyone has updated information on this bug check, that'd be much appreciated. From windbg:
    BugCheck DA, {504, fffff6fc4002a2e0, 30, 545c}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b47b )
    Thanks
    Hans
    HK

    Hi Hans
    Thanks for letting us know how you resolved the problem.
    Regards,
    Thank You for using Windows 7
    Ronnie Vernon MVP

  • I want to have all my tabs return after closing. In Tools/Options/General/ I have' Show my Windows and Tabs from last time' checked, but it does not work. When I open FF again none of my formerly open Tabs show... FF v.4.

    When I open FF up again after I have closed it, I want all tabs to return. In Tools/Options/General/ I have' Show my Windows and Tabs from last time' checked-does not work. In addition, the feedback window fails to 'Submit...!'

    Some things to check:
    #'''Browsing history must be saved'''
    #*Firefox button: Firefox button > Options > Options > Privacy > [X] Remember my browsing history
    #*Menu Bar: Tools > Options > Privacy > [X] Remember my browsing history
    #'''Also make sure you do not clear "Browsing History" when using Clear Recent History or when closing Firefox'''
    #*Using Clear Recent History
    #**Firefox button: Firefox button > History >Clear Recent History
    #**Menu Bar: Tools > Clear Recent History
    #*When closing Firefox
    #**Firefox button: Firefox button > Options > Options > Privacy (checked) > Settings
    #**Menu Bar: Tools > Options > Privacy (checked) > Settings
    #**See: https://support.mozilla.com/en-US/kb/Clear%20Recent%20History
    #'''Make sure you are not in Private Browsing mode''' or '''in permanent Private Browsing mode''':
    #*See: https://support.mozilla.com/en-US/kb/Private%20Browsing
    #'''If you have the'''Tab Mix Plus'''extension''', then disable the built-in session restore.

  • I want to install my photoshop 5.0 limited edition but the pc displays i should check if it is a 32 or 64 bit application. i changed my windows os  from xp to win7 64 bit (i think that is the problem) how can i run my photoshop on this system?

    i want to install my photoshop 5.0 limited edition but the pc displays i should check if it is a 32 or 64 bit application. i changed my windows os  from xp to win7 64 bit (i think that is the problem) how can i install and run my photoshop 5.0 le on this system?

    Kglad Creative Suite 2 is only applicable to individuals affected by the activation server shut down.  A complete list of affected software titles can be found at Activation server shut down for Creative Suite 2, Acrobat 7, and Macromedia products.

  • ProLiant DL580 G5 : Abnormal Program Terminatio​n (Windows bug check, STOP: 0x0000007E

    We have an ProLiant DL580 G5 server which get blue screen every few minutes. In ILO logs (IML) i get the message.
    Abnormal Program Termination (Windows bug check, STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF880018B346C, 0xFFFFF88002FD93F8, 0xFFFFF88002FD8C50))
    Tried booting in safe mode, but no go. Please advise.

    Hi:
    You may also want to post your question on the HP Business Support Forum -- Proliant DL Servers section.
    http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-D​L-SL/bd-p/itrc-264#.VCbIEnl0y9I

  • Non-system disk Error when rebooting from Windows Disk

    Hello,
    I'm trying to run Windows 7 Pro on a partition on my Macbook pro retina display. I have reached the step where through bootcamp you reboot from the wondows disk. I have the windows disk in an external optical drive and have tried both 32 and 64 bit installation disks and still getting the same error"
    "Non-system disk
    Press and key to reboot"
    When I hit any key nothing happends, have to turn off computer by holding power button.
    I have also tried turning the computer on and holding cammad R, and selecting the boot disk manually, same error occurs.
    Any suggestions?

    Reboot your Mac while holding down the Alt/Option-key until the Boot Selection screen comes up.
    Choose to boot into oSX.
    Once in OSX go to System Preferences then Startup Volume and reset OSX to be the default.
    Btw.: there are no OSX Lion discs unless you made one yourself.
    Lion has Recovery instead OS X Lion: About Lion Recovery
    Stefan

  • Windows 2008 R2 SP1 BSOD Bug Check 0x0000003b

    Hi,
    I have a Win 2k8 R2 SP1 VM that keeps crashing every night for the past 2 days. Every time is the same bug check code 0x0000003b. I looked around and found 2 KBs for this specific code: 
    http://support.microsoft.com/kb/980932/en-gb - does not apply to my system
    http://support.microsoft.com/kb/2836373/en-gb - installed the hotfix yesterday but got another crash today
    The server has 30 printers installed on it and during the night only one is used so I tend to think that it is causing the crash. The printer has the latest driver installed (Konica Minolta Universal Printing Driver v2.4).
    I looked through the dump files generated by every BSOD but I cannot find anything that would point me in the right direction... or I might have missed it. 
    Here is a bit more info on the server:
    Windows 2008 R2 Standard SP1
    System is a VM
    IIS role installed
    30 printers installed - all drivers are up to date
    I have stored the dump files here: http://1drv.ms/1kpL9vh
    Any help with this would be greatly appreciated. 
    Thanks

    Hi gogu2008,
    First , please keep the VM and Host up-to-date then check if the issue persists .
    What is the Host OS ?
    How much RAM does the VM have ?
    If the VM is using dynamic memory , for troubleshooting you may try to configure  fixed RAM for the VM.
    As for the DUMP , you can change the "mini dump  " to  "kernel memory dump " then analysis the file after BSOD .
    Hope it helps
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Black screen on reboot from windows to mac?

    Hello,
    A black screen is stalking me... I'd be much obliged if anyone can help.
    The problem:
    I have Windows 7 installed with Bootcamp. Every time I shut down / restart from  Windows  to get to the Mac side, the chime rings, but the screen stays black. I can tell the Mac is running though, because of the sound I hear when I press the volume up/down keys on the keyboard. Then, at some point (5 - 30 - 60 mins later) the computer decides out of nowhere it's time to unveil the desktop... This never happens when I reboot from the Mac side (unless I force shutdown while the black screen is still there).
    Things I tried that didn't work:
    - Command-Option-P-R to reset NVRAM (worked once but didn't fix it, and now when I try the screen stays black)
    - Resetting SMC
    - Apple Diagnostics came back with no issues found (when I restarted after the diagnostics, I got hit with the black screen again...)
    - Erasing the Windows partition and reinstalling it.
    Things I should probably mention:
    The mac is a late 2013 iMac, Intel Core i5 with NVIDIA GeForce GT 750M, running OSX 10.9.1
    I apologize if this has an obvious solution I somehow missed, or if it was answered in another post.
    Thanks for your time.

    One way is to wipe the iPod clean and use it as a hard drive to carry the files over to the new comptuer. You must format the iPod in what's called Fat32, the older formatting for DOS. If you do this on a Mac, you use the Disk Utility to Erase the disk, and you choose MS-DOS for the format.
    Then you plug in the iPod to the Mac, drag the iTunes Music folder to the iPod disk. Then you plug it into the Windows machine and drag the files to your iTunes folder there. See some instructions here:
    http://docs.info.apple.com/article.html?artnum=300173
    On the other hand, you might try using a 3rd party program that takes songs off the iPod. But Windows doesn't read the Mac files, I bet they won't help you move the music cross-platform.
    Hope this helps...

  • Event 1001 Bug Check Windows 7 Ultimate 64-bit

    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          1/17/2014 6:56:51 PM
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      KT-PC
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000003, 0xfffff8a0245c2580, 0xfffff8a0245c2580, 0x73634946030c030c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 011714-30997-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-01-17T23:56:51.000000000Z" />
        <EventRecordID>389585</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>KT-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x00000019 (0x0000000000000003, 0xfffff8a0245c2580, 0xfffff8a0245c2580, 0x73634946030c030c)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">011714-30997-01</Data>
      </EventData>
    </Event>

    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.
    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask
    Please provide us with your Event Viewer administrative logs by following these steps:
    Click Start Menu
    Type eventvwr into Search programs and files (do not hit enter)
    Right click eventvwr.exe and click Run as administrator
    Expand Custom Views
    Click Administrative Events
    Right click Administrative Events
    Save all Events in Custom View As...
    Save them in a folder where you will remember which folder and save as Errors.evtx
    Go to where you saved Errors.evtx
    Right click Errors.evtx -> send to -> compressed (zipped) folder
    Upload the .zip file to skydrive or a file sharing service and put a link to it in your next post
    If you have updated to win 8.1 and you get the error message "the system cannot find the file specified" it is a known problem.  The
    work around is to edit the registry.  If you are not comfortable doing this DONT.  If you are, backup the key before you do
    Press Win+"R" and input regedit
    Navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"
    Wanikiya and Dyami--Team Zigzag

Maybe you are looking for

  • Java Plug-in 1.4.0 throws an IllegalStateException: zip file closed

    Cross-posting to reach a wider audience: Java Plug-in 1.4.0 throws an IllegalStateException: zip file closed Author: remyb Jul 23, 2002 6:36 AM A IllegalStateException is thrown when the class loader try to load a class from my applet JAR file. The a

  • Is there a device that my mom can use to plug in her iphone to the bose wave soundsystem and play music?

    Is there a device that can be used to plug in an iphone 4 to a bose wave sound system and play music?

  • Can't understand Error Activation

    I downloaded Adobe Digital edition 3.0 at first i can authorize my computer but i cant add the ebook that i purchased. So what i did I changed my Adobe Id and entered it again to authorize my computer It did authorize my computer but when i am adding

  • Reciever IDoc Configuration.

    Hi All, I've a doubt which is like: 1) In IDoc Sender: We don't need a Sender Agreement, Sender Communication Channel as IDoc resides in ABAP stack i.e. it can interact directly with the Integration Server (Reason 1) Is there any other reason for it?

  • Is my Mac mini broken?

    Hi, Ive been trying to get my audio working with ichat and imovie to no avail. I hook up my camera with a firewire cable, In ichat the video signal comes through fine but no audio. If I go to system preferences and choose the audio device it works th