Get your fill of sci-fi, science, and mockery of stupid people
* FAQ    * Search   * Register   * Login 
Want to support this site? Click

Quote of the Week: "A great civilization is not conquered from without until it has destroyed itself from within." - Will Durant, American historian (1885-1981)


All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: BSOD issues PostPosted: 2012-10-22 06:12am
Offline
SMAKIBBFB
User avatar

Joined: 2002-07-28 12:30pm
Posts: 19195
(I have tried to include all relevant data according to posting rules, but if I have missed something, please let me know and I will supply it ASAP)

About 12 months ago I upgraded my RAM and GPU - since then I have had fairly regular BSODs having previous experienced no issues aside from a PSU failure. These have come and gone at times (after a format and OS reinstall and at other random intervals they seemed to go away for a few weeks and sometimes a month or so) but recently they're on the rise again to the point where I get on average one every two days (I had previously posted about this here, but there'd be no real consensus about the cause).

There are no immediately obvious symptoms for this issue. Temperatures and voltages are all stable and within the acceptable limits. The BSODs happen without warning and can occur while the system is under load or idling. There is no artefacting or other glitchiness prior to the BSOD occuring.

My own attempts at reading these crashdumps has given me some insight, but nothing solid enough that I'm willing to stake my cash on to fix it. Any assistance you could give would be greatly appreciated.


System info:
CPU - Intel E8500 (not OC'd)
MoBo - Gigabyte EP45T-UD3LR
Memory - 8gb G.Skill DDR3 (Suspect A)
GPU - Radeon HD6900 (Suspect B)
PSU - Coolermaster Extreme 650
OS - Windows 7 64 Home Premium
No special cooling

DXDiag:
Code:
------------------
System Information
------------------
Time of this report: 10/22/2012, 19:33:25
       Machine name: SPQR
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120830-0333)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: EP45T-UD3LR
               BIOS: Award Modular BIOS v6.00PG
          Processor: Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz (2 CPUs), ~2.8GHz
             Memory: 8192MB RAM
Available OS Memory: 8190MB RAM
          Page File: 3718MB used, 12661MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
      Display Tab 2: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
          Input Tab: No problems found.



Oldest BSOD on current system (post OS install)

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051612-28312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e57670
Debug session time: Wed May 16 18:52:03.104 2012 (UTC + 11:00)
System Uptime: 6 days 14:16:30.254
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002cb5efe, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cb5efe, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec1100
GetUlongFromAddress: unable to read from fffff80002ec11c0
 0000000000000000 Nonpaged pool

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!MiRemoveAnyPage+13e
fffff800`02cb5efe f0410fba6c241000 lock bts dword ptr [r12+10h],0

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  ArmA2OA.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002cdcdb8 to fffff80002c921c0

STACK_TEXT: 
fffff880`0aba1c48 fffff800`02cdcdb8 : 00000000`0000001e ffffffff`c0000005 fffff800`02cb5efe 00000000`00000000 : nt!KeBugCheckEx
fffff880`0aba1c50 fffff800`02c91842 : fffff880`0aba2428 00000000`00000022 fffff880`0aba24d0 fffffa80`06900f50 : nt! ?? ::FNODOBFM::`string'+0x48d3d
fffff880`0aba22f0 fffff800`02c9014a : 00000000`00c87604 00000000`00000201 fffffa80`07bc75e8 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`0aba24d0 fffff800`02cb5efe : 00000000`00000000 fffffa80`0801cec8 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`0aba2660 fffff800`02cbfd91 : 00000000`00000054 fffffa80`00000000 00000000`0000002a fa800712`20c80460 : nt!MiRemoveAnyPage+0x13e
fffff880`0aba2780 fffff800`02cb025c : fa800712`20c80460 fffffa80`0801cec8 fffff8a0`0e2b3d60 f8a00e2b`3d600400 : nt!MiResolveMappedFileFault+0xb01
fffff880`0aba28e0 fffff800`02caeac3 : 00000000`000bd959 00000000`005a3f6f fffff680`00002d18 fffffa80`0801cec8 : nt!MiResolveProtoPteFault+0x47c
fffff880`0aba2970 fffff800`02c9e769 : 00000000`00000000 00000000`005a3f6f 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0aba2a80 fffff800`02c902ee : 00000000`00000008 00000000`005a3f6f 00000000`00000001 00000000`00000005 : nt!MmAccessFault+0x359
fffff880`0aba2be0 00000000`005a3f6f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0182f530 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5a3f6f


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiRemoveAnyPage+13e
fffff800`02cb5efe f0410fba6c241000 lock bts dword ptr [r12+10h],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiRemoveAnyPage+13e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiRemoveAnyPage+13e

BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiRemoveAnyPage+13e

Followup: MachineOwner
---------



And then these ones from throughout October:
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\100612-18218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02ea9670
Debug session time: Sat Oct  6 22:10:48.534 2012 (UTC + 11:00)
System Uptime: 1 days 2:54:29.893
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
...................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ca6eb1, fffff880009a9998, fffff880009a91f0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ca6eb1, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a91f0, Context Record Address

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!MmZeroPageThread+3c4
fffff800`02ca6eb1 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80002ca6eb1 (nt!MmZeroPageThread+0x00000000000003c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a91f0 -- (.cxr 0xfffff880009a91f0)
rax=0000000000000022 rbx=1cffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8006900f50 rdi=0000000000000022
rip=fffff80002ca6eb1 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=0000000000000008 r12=0000000000000000 r13=6ffffa7fffffffd0
r14=0000000000000040 r15=fffff80002c65000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MmZeroPageThread+0x3c4:
fffff800`02ca6eb1 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:6ffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_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 fffff80002f13100
GetUlongFromAddress: unable to read from fffff80002f131c0
 ffffffffffffffff

FOLLOWUP_IP:
nt!MmZeroPageThread+3c4
fffff800`02ca6eb1 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002f7ae6a to fffff80002ca6eb1

STACK_TEXT: 
fffff880`009a9bd0 fffff800`02f7ae6a : fffffa80`06a04b50 00000000`00000080 fffffa80`06a04040 fffff800`02cd4eb9 : nt!MmZeroPageThread+0x3c4
fffff880`009a9d00 fffff800`02cd4ec6 : fffff800`02e56e80 fffffa80`06a04b50 fffff800`02e64cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

STACK_COMMAND:  .cxr 0xfffff880009a91f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

Followup: MachineOwner
---------



Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\100712-22296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02ea3670
Debug session time: Sun Oct  7 20:07:35.887 2012 (UTC + 11:00)
System Uptime: 0 days 21:55:48.000
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50853, fffff8800b497578, fffff8800b496dd0, fffff80002d01ede}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000050853
Arg2: fffff8800b497578
Arg3: fffff8800b496dd0
Arg4: fffff80002d01ede

Debugging Details:
------------------


EXCEPTION_RECORD:  fffff8800b497578 -- (.exr 0xfffff8800b497578)
ExceptionAddress: fffff80002d01ede (nt!MiRemoveAnyPage+0x000000000000013e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800b496dd0 -- (.cxr 0xfffff8800b496dd0)
rax=0000000000000002 rbx=0000000000000032 rcx=0000000000000002
rdx=0000000000000001 rsi=fffffa80069011d0 rdi=00ffffffffffffff
rip=fffff80002d01ede rsp=fffff8800b4977b0 rbp=fffff8800b497800
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=2ffffa7fffffffd0 r13=0000000000000000
r14=000000000000003f r15=000000000000003f
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!MiRemoveAnyPage+0x13e:
fffff800`02d01ede f0410fba6c241000 lock bts dword ptr [r12+10h],0 ds:002b:2ffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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 fffff80002f0d100
GetUlongFromAddress: unable to read from fffff80002f0d1c0
 ffffffffffffffff

FOLLOWUP_IP:
nt!MiRemoveAnyPage+13e
fffff800`02d01ede f0410fba6c241000 lock bts dword ptr [r12+10h],0

FAULTING_IP:
nt!MiRemoveAnyPage+13e
fffff800`02d01ede f0410fba6c241000 lock bts dword ptr [r12+10h],0

BUGCHECK_STR:  0x34

LAST_CONTROL_TRANSFER:  from fffff80002c9d8a0 to fffff80002d01ede

STACK_TEXT: 
fffff880`0b4977b0 fffff800`02c9d8a0 : fa80098b`3a9004c0 00000000`00000000 00000000`0000007e 00000000`00000000 : nt!MiRemoveAnyPage+0x13e
fffff880`0b4978d0 fffff800`02f7639a : fffffa80`0714d430 fffffa80`00000001 fffffa80`0714d430 00000000`00000005 : nt!MiPfPutPagesInTransition+0x7c7
fffff880`0b497a40 fffff800`02c86887 : fffffa80`0714d430 00000000`30caf000 00000000`30caf000 fffff800`02e7b280 : nt!MmPrefetchForCacheManager+0x8e
fffff880`0b497a90 fffff800`02d231ae : fffffa80`0a9b4f20 fffffa80`06f57b00 00000000`0000002a fffff800`02edc8b8 : nt!CcPerformReadAhead+0x2f3
fffff880`0b497bc0 fffff800`02ce7841 : fffffa80`06a79cc0 fffff800`02fd0601 fffff800`02edc8d0 fffffa80`00000002 : nt!CcWorkerThread+0x21e
fffff880`0b497c70 fffff800`02f74e6a : 00000000`00000000 fffffa80`06f57b50 00000000`00000080 fffffa80`06a21040 : nt!ExpWorkerThread+0x111
fffff880`0b497d00 fffff800`02cceec6 : fffff880`009e7180 fffffa80`06f57b50 fffffa80`06a31660 00000000`00020000 : nt!PspSystemThreadStartup+0x5a
fffff880`0b497d40 00000000`00000000 : fffff880`0b498000 fffff880`0b492000 fffff880`0b4979a0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiRemoveAnyPage+13e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

STACK_COMMAND:  .cxr 0xfffff8800b496dd0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x34_nt!MiRemoveAnyPage+13e

BUCKET_ID:  X64_0x34_nt!MiRemoveAnyPage+13e

Followup: MachineOwner
---------



Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\100812-20734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e97670
Debug session time: Mon Oct  8 22:26:53.632 2012 (UTC + 11:00)
System Uptime: 0 days 4:49:22.976
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002d02cf2, fffff8800b3186b0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002d02cf2, Address of the instruction which caused the bugcheck
Arg3: fffff8800b3186b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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!KxWaitForLockOwnerShip+12
fffff800`02d02cf2 48890a          mov     qword ptr [rdx],rcx

CONTEXT:  fffff8800b3186b0 -- (.cxr 0xfffff8800b3186b0)
rax=00000000fffffa80 rbx=fffffa8000edc630 rcx=fffff8800b319120
rdx=8100000000000000 rsi=000000000004f421 rdi=fffff8800b319120
rip=fffff80002d02cf2 rsp=fffff8800b319090 rbp=fffff8800b319100
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8006900f48
r11=fffff80002f04ac0 r12=0000000000000001 r13=0000000000123300
r14=0000000000000528 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02d02cf2 48890a          mov     qword ptr [rdx],rcx ds:002b:81000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002d02cf2

STACK_TEXT: 
fffff880`0b319090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x12


FOLLOWUP_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02d02cf2 48890a          mov     qword ptr [rdx],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

STACK_COMMAND:  .cxr 0xfffff8800b3186b0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12

BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12

Followup: MachineOwner
---------



Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\101012-21390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eab670
Debug session time: Wed Oct 10 09:10:28.723 2012 (UTC + 11:00)
System Uptime: 0 days 1:04:21.067
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ca8eb1, fffff880009a9998, fffff880009a91f0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ca8eb1, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a91f0, Context Record Address

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!MmZeroPageThread+3c4
fffff800`02ca8eb1 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80002ca8eb1 (nt!MmZeroPageThread+0x00000000000003c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a91f0 -- (.cxr 0xfffff880009a91f0)
rax=0000000000000012 rbx=00ffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8006900cd0 rdi=0000000000000012
rip=fffff80002ca8eb1 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=0000000000000008 r12=0000000000000000 r13=2ffffa7fffffffd0
r14=0000000000000040 r15=fffff80002c67000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210202
nt!MmZeroPageThread+0x3c4:
fffff800`02ca8eb1 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:2ffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_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 fffff80002f15100
GetUlongFromAddress: unable to read from fffff80002f151c0
 ffffffffffffffff

FOLLOWUP_IP:
nt!MmZeroPageThread+3c4
fffff800`02ca8eb1 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002f7ce6a to fffff80002ca8eb1

STACK_TEXT: 
fffff880`009a9bd0 fffff800`02f7ce6a : fffffa80`06a04b50 00000000`00000080 fffffa80`06a04040 fffff800`02cd6eb9 : nt!MmZeroPageThread+0x3c4
fffff880`009a9d00 fffff800`02cd6ec6 : fffff800`02e58e80 fffffa80`06a04b50 fffff800`02e66cc0 0013541c`0015641c : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

STACK_COMMAND:  .cxr 0xfffff880009a91f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

Followup: MachineOwner
---------



Code:
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\101512-17625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02ea5670
Debug session time: Mon Oct 15 09:41:43.907 2012 (UTC + 11:00)
System Uptime: 1 days 1:12:59.251
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002d109b2, 0, ffffffffffffffff}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d109b2, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0f100
GetUlongFromAddress: unable to read from fffff80002f0f1c0
 0000000000000000 Nonpaged pool

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02d109b2 48890a          mov     qword ptr [rdx],rcx

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d2aa88 to fffff80002cdffc0

STACK_TEXT: 
fffff880`0d1448c8 fffff800`02d2aa88 : 00000000`0000001e ffffffff`c0000005 fffff800`02d109b2 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d1448d0 fffff800`02cdf642 : fffff880`0d1450a8 fffffa80`025af730 fffff880`0d145150 00000000`000c8fd1 : nt! ?? ::FNODOBFM::`string'+0x487ad
fffff880`0d144f70 fffff800`02cddf4a : fffff880`0d1454c0 fffffa80`08d37338 00000000`00000000 fffffa80`08d37338 : nt!KiExceptionDispatch+0xc2
fffff880`0d145150 fffff800`02d109b2 : 00000000`00000000 00000000`00000001 fffffa80`06a1fc58 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`0d1452e0 fffff800`02cef88d : fffffa80`025af730 00000000`00000000 fffff880`0d145380 fffffa80`06a1fb50 : nt!KxWaitForLockOwnerShip+0x12
fffff880`0d145310 fffff800`02d11f67 : 00000000`00000000 fffff680`000553f8 00000000`00000000 fffff880`0697366b : nt!MiInsertPageInFreeOrZeroedList+0x55d
fffff880`0d145420 fffff800`02d111b7 : 00000000`00000000 fffff680`00055448 fffffa80`0989c060 fffff800`02e0b1de : nt!MiDeletePteRun+0x4ed
fffff880`0d1455d0 fffff800`02ccc81f : fffffa80`00000000 00000000`0aa89fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`0d145790 fffff800`02cdf253 : ffffffff`ffffffff fffff880`0d145a60 fffff880`0d145ac8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0d145890 fffff800`02cdb810 : fffff960`000e7068 00000000`00000001 00000000`00000000 fffff900`c256c9f0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0d145a28 fffff960`000e7068 : 00000000`00000001 00000000`00000000 fffff900`c256c9f0 00000000`00000000 : nt!KiServiceLinkage
fffff880`0d145a30 fffff960`000e73c4 : ffffffff`00000000 fffff880`00000000 fffff900`c256c9f0 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`0d145b80 fffff960`000a7f95 : ffffffff`db051795 fffff900`c256c9f0 00000000`00001795 00000000`00000002 : win32k!bDeleteSurface+0x34
fffff880`0d145bb0 fffff800`02cdf253 : fffffa80`06c49750 fffff900`c00bf010 00000000`00000001 00000000`03d8d8bc : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`0d145be0 00000000`74e92e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02e2ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74e92e09


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!SURFACE::bDeleteSurface+3c8
fffff960`000e7068 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`000e721d)

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5006fd0d

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1E_c0000005_R_win32k!SURFACE::bDeleteSurface+3c8

Followup: MachineOwner
---------



Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\101512-18468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e5c670
Debug session time: Mon Oct 15 21:02:46.399 2012 (UTC + 11:00)
System Uptime: 0 days 11:20:09.053
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002c59861, fffff880009a9998, fffff880009a91f0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c59861, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a91f0, Context Record Address

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!MmZeroPageThread+3c4
fffff800`02c59861 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80002c59861 (nt!MmZeroPageThread+0x00000000000003c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a91f0 -- (.cxr 0xfffff880009a91f0)
rax=0000000000000022 rbx=54ffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8006900f50 rdi=0000000000000022
rip=fffff80002c59861 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=0000000000000008 r12=0000000000000008 r13=effffa7fffffffd0
r14=0000000000000040 r15=fffff880009e7180
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
nt!MmZeroPageThread+0x3c4:
fffff800`02c59861 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:effffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_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 fffff80002ec6100
GetUlongFromAddress: unable to read from fffff80002ec61c0
 ffffffffffffffff

FOLLOWUP_IP:
nt!MmZeroPageThread+3c4
fffff800`02c59861 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002f2de5a to fffff80002c59861

STACK_TEXT: 
fffff880`009a9bd0 fffff800`02f2de5a : fffffa80`06a13b50 00000000`00000080 fffffa80`06a13040 fffff800`02c87d19 : nt!MmZeroPageThread+0x3c4
fffff880`009a9d00 fffff800`02c87d26 : fffff800`02e09e80 fffffa80`06a13b50 fffff800`02e17cc0 0013541c`0015641c : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

STACK_COMMAND:  .cxr 0xfffff880009a91f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

Followup: MachineOwner
---------



Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\101712-24406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02ea3670
Debug session time: Wed Oct 17 18:06:26.185 2012 (UTC + 11:00)
System Uptime: 1 days 21:02:47.529
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ca0861, fffff880009a9998, fffff880009a91f0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ca0861, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a91f0, Context Record Address

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!MmZeroPageThread+3c4
fffff800`02ca0861 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80002ca0861 (nt!MmZeroPageThread+0x00000000000003c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a91f0 -- (.cxr 0xfffff880009a91f0)
rax=0000000000000032 rbx=00ffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa80069011d0 rdi=0000000000000032
rip=fffff80002ca0861 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=0000000000000009 r12=0000000000000009 r13=2ffffa7fffffffd0
r14=0000000000000040 r15=fffff880009e7180
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MmZeroPageThread+0x3c4:
fffff800`02ca0861 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:2ffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_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 fffff80002f0d100
GetUlongFromAddress: unable to read from fffff80002f0d1c0
 ffffffffffffffff

FOLLOWUP_IP:
nt!MmZeroPageThread+3c4
fffff800`02ca0861 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002f74e5a to fffff80002ca0861

STACK_TEXT: 
fffff880`009a9bd0 fffff800`02f74e5a : fffffa80`06a13b50 00000000`00000080 fffffa80`06a13040 fffff800`02cced19 : nt!MmZeroPageThread+0x3c4
fffff880`009a9d00 fffff800`02cced26 : fffff800`02e50e80 fffffa80`06a13b50 fffff800`02e5ecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

STACK_COMMAND:  .cxr 0xfffff880009a91f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

Followup: MachineOwner
---------



Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\102012-20671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e93670
Debug session time: Sat Oct 20 22:35:58.921 2012 (UTC + 11:00)
System Uptime: 0 days 6:57:45.265
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002c90861, fffff880009a9998, fffff880009a91f0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

Followup: MachineOwner
---------

0: kd> !analyze -v

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c90861, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a91f0, Context Record Address

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!MmZeroPageThread+3c4
fffff800`02c90861 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80002c90861 (nt!MmZeroPageThread+0x00000000000003c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a91f0 -- (.cxr 0xfffff880009a91f0)
rax=0000000000000012 rbx=79ffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8006900cd0 rdi=0000000000000012
rip=fffff80002c90861 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=0000000000000008 r12=0000000000000001 r13=dffffa7fffffffd0
r14=0000000000000040 r15=fffff80002e40e80
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!MmZeroPageThread+0x3c4:
fffff800`02c90861 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:dffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_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:  ffffffffffffffff

FOLLOWUP_IP:
nt!MmZeroPageThread+3c4
fffff800`02c90861 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002f64e5a to fffff80002c90861

STACK_TEXT: 
fffff880`009a9bd0 fffff800`02f64e5a : fffffa80`06a04b50 00000000`00000080 fffffa80`06a04040 fffff800`02cbed19 : nt!MmZeroPageThread+0x3c4
fffff880`009a9d00 fffff800`02cbed26 : fffff800`02e40e80 fffffa80`06a04b50 fffff800`02e4ecc0 0013541c`0015641c : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

STACK_COMMAND:  .cxr 0xfffff880009a91f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

Followup: MachineOwner
---------



Code:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\101812-19984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02ea4670
Debug session time: Thu Oct 18 15:42:05.488 2012 (UTC + 11:00)
System Uptime: 0 days 21:34:15.832
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ca1861, fffff880009a9998, fffff880009a91f0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ca1861, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a91f0, Context Record Address

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!MmZeroPageThread+3c4
fffff800`02ca1861 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80002ca1861 (nt!MmZeroPageThread+0x00000000000003c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a91f0 -- (.cxr 0xfffff880009a91f0)
rax=0000000000000032 rbx=00ffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa80069011d0 rdi=0000000000000032
rip=fffff80002ca1861 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=0000000000000008 r12=0000000000000008 r13=2ffffa7fffffffd0
r14=0000000000000040 r15=fffff80002e51e80
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MmZeroPageThread+0x3c4:
fffff800`02ca1861 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:2ffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_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 fffff80002f0e100
GetUlongFromAddress: unable to read from fffff80002f0e1c0
 ffffffffffffffff

FOLLOWUP_IP:
nt!MmZeroPageThread+3c4
fffff800`02ca1861 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002f75e5a to fffff80002ca1861

STACK_TEXT: 
fffff880`009a9bd0 fffff800`02f75e5a : fffffa80`06a13b50 00000000`00000080 fffffa80`06a13040 fffff800`02ccfd19 : nt!MmZeroPageThread+0x3c4
fffff880`009a9d00 fffff800`02ccfd26 : fffff800`02e51e80 fffffa80`06a13b50 fffff800`02e5fcc0 0013541c`0015641c : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

STACK_COMMAND:  .cxr 0xfffff880009a91f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4

Followup: MachineOwner
---------




Image
What is Project Zohar?

Top
 Profile  
 Post subject: Re: BSOD issues PostPosted: 2012-10-22 06:55am
Offline
Emperor's Hand
User avatar

Joined: 2002-10-22 12:00am
Posts: 6682
Location: \m/
Looks like a memory error. Run Memtest or something similar on your RAM.



ASS Marine | Ex 40K Nut | Metalhead | BattleTecher | Maximal
The vision never dies; life's a never-ending wheel
1337 posts as of 16:34 GMT-7 June 2nd, 2003

"IS names suck, Clan names forever. That there is a Timber Wolf." - Uraniun235

Top
 Profile  
 Post subject: Re: BSOD issues PostPosted: 2012-10-22 09:10am
Offline
Lore Monkey
User avatar

Joined: 2002-07-04 06:35am
Posts: 5371
Have you tried testing each memory module and slot individually?



「かかっ―」

Top
 Profile  
 Post subject: Re: BSOD issues PostPosted: 2012-10-22 03:17pm
Offline
Jedi Council Member
User avatar

Joined: 2003-06-26 04:24pm
Posts: 2235
Location: Texas
I had an issue like this with a board years back. The problem screamed "bad RAM," but it all passed memory checks without issue. It even worked fine when I put it back on the old mainboard I replaced. It turned out upon close inspection, I had a blown capacitor that was being covered by my rather large CPU cooler. Provided your PC passes a RAM check: Check your MB over for any blown capacitors and scrutinize the top (and bottom if you can get to it) with a flashlight for any scratches or burn marks. Also, recheck all your mouting screws to make sure they are tight and aren't shifting to ground out your MB, although this in my experience, this usually results in a black screen, not a blue screen.

Top
 Profile  
 Post subject: Re: BSOD issues PostPosted: 2012-10-22 04:08pm
Offline
Hardware Lover
User avatar

Joined: 2002-07-07 03:04am
Posts: 7660
Location: Frolicing in the fields of amateur pontificating
Quick lesson.
BSODs happen for a reason, the reason is the BugCheck number. Usually, when you have a driver issue (buggy code) or buggy hardware (broken GPU?) you get consistent bugcheck types.
What you have here is random bugchecks spread all over the operating system. Which means that your entire system is buggy. We can therefore conclude you have a basic hardware issue.
This may be either RAM (most likely component to have issues) or motherboard/power problems. Power problems are rather rare with modern PSUs, so lets scratch that.

Run Memtest on your computer, or try removing RAM modules. If (as per TheFeniX's example) all tests pass, check your motherboard.



Sig left blank in the name of the Society for conservation of Bits

Top
 Profile  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot] and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group