BSOD - Memory corruption or something else?
evening guys,
been having a few random hard locks over the last week or so - mainly while gaming. now not everyone bsods, in fact a couple of them have just rebooted the system without a bsod. i have attached the 2 dump files i have related to these crashes and the bsod screen via bluescreenreview - apologies if this is wrong.
rand memtest for a good 6 or so hours with no errors at all, anyone have a clue whats going on - as this is doing my pickle now and it's hit and miss weather i can have a game without crashing/locking up.
evening guys,
been having a few random hard locks over the last week or so - mainly while gaming. now not everyone bsods, in fact a couple of them have just rebooted the system without a bsod. i have attached the 2 dump files i have related to these crashes and the bsod screen via bluescreenreview - apologies if this is wrong.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010211-23306-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`0304ce50
Debug session time: Sun Jan 2 20:58:26.272 2011 (UTC + 0:00)
System Uptime: 0 days 1:35:01.818
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
............................................
Loading User Symbols
Loading unloaded module list
.....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 1cdfb, 2, 1cddd}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
2: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000001cdfb, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000001cddd, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: BlackOpsMP.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002f0f38c to fffff80002e7f740
STACK_TEXT:
fffff880`0943f718 fffff800`02f0f38c : 00000000`0000004e 00000000`00000099 00000000`0001cdfb 00000000`00000002 : nt!KeBugCheckEx
fffff880`0943f720 fffff800`02e25281 : fffff880`07be2000 ba700000`1cdfb96b fffffa80`00569f10 fffffa80`041deb60 : nt!MiBadShareCount+0x4c
fffff880`0943f760 fffff800`0322f260 : fffff880`07be2000 fffff800`0000001e fffffa80`06b3aa60 fffff880`05185e00 : nt! ?? ::FNODOBFM::`string'+0x2e21d
fffff880`0943f8b0 fffff800`0322f333 : fffff8a0`02af61e0 fffff880`0943fca0 fffff8a0`0bd46000 fffffa80`05f3b000 : nt!MiRemoveFromSystemSpace+0x1d0
fffff880`0943f910 fffff880`0519ab1e : fffffa80`05671de0 fffff880`0519b5fd 00000000`00000000 00000000`00000000 : nt!MmUnmapViewInSystemSpace+0x73
fffff880`0943f940 fffff880`051a97b7 : 00000000`40000140 fffffa80`0686e010 fffff880`0943fca0 00000000`00000174 : dxgmms1!VIDMM_GLOBAL DestroyOneAllocation+0x146
fffff880`0943fa20 fffff880`0518324b : fffffa80`03e379a0 00000000`75212450 fffffa80`6d4d6956 00000000`00000174 : dxgmms1!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+0x 117
fffff880`0943fa70 fffff880`051831d3 : fffff8a0`0de71860 00000000`fffa7000 fffff8a0`0acefc40 00000000`40000140 : dxgmms1!VIDMM_DMA_POOL::`scalar deleting destructor'+0x6b
fffff880`0943faa0 fffff880`050d53f9 : fffff8a0`0acefc00 fffff8a0`0de71860 00000000`00000000 00000000`fffa7000 : dxgmms1!VidMmDestoryDmaPool+0x13
fffff880`0943fad0 fffff880`050d729d : fffff8a0`0de71860 fffff8a0`0de71860 fffff880`0943fca0 00000000`fffa7000 : dxgkrnl!DXGCONTEXTDestroy+0x16d
fffff880`0943fb50 fffff880`050d4366 : 00000000`0df4dc74 fffffa80`041deb60 fffff880`0943fbc8 00000000`07a7e7c8 : dxgkrnl!DXGDEVICEDestroyContext+0xb9
fffff880`0943fb80 fffff960`001eba06 : 00000000`00000020 ffffffff`ffb3b400 00000000`000007f8 00000000`75245f70 : dxgkrnl!DxgkDestroyContext+0x1a6
fffff880`0943fbf0 fffff800`02e7e993 : fffffa80`041deb60 fffff880`0943fca0 00000000`fffa7000 fffffa80`04110060 : win32k!NtGdiDdDDIDestroyContext+0x12
fffff880`0943fc20 00000000`7526121a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`07a7e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7526121a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`02f0f38c cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
Followup: MachineOwner
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010211-23150-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Sun Jan 2 22:14:06.310 2011 (UTC + 0:00)
System Uptime: 0 days 1:14:51.245
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
............................................
Loading User Symbols
Loading unloaded module list
.....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8994426c2, b3b7465eebc1f6a8, fffff80002e2871c, 1}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
3: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See [URL="http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx"]http://www.microsoft.com/whdc/driver...tPatching.mspx[/URL]
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8994426c2, Reserved
Arg2: b3b7465eebc1f6a8, Reserved
Arg3: fffff80002e2871c, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
Debugging Details:
------------------
BUGCHECK_STR: 0x109
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ed7740
STACK_TEXT:
fffff880`031bd5d8 00000000`00000000 : 00000000`00000109 a3a039d8`994426c2 b3b7465e`ebc1f6a8 fffff800`02e2871c : nt!KeBugCheckEx
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
fffff80002e28796 - hal!HalpHpetClockInterruptWork+7a
[ 15:55 ]
1 error : !hal (fffff80002e28796)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
rand memtest for a good 6 or so hours with no errors at all, anyone have a clue whats going on - as this is doing my pickle now and it's hit and miss weather i can have a game without crashing/locking up.
Last edited:
My Computer
- Computer Manufacturer/Model Number
- Home/Custom Built
- OS
- Windows 7 Pro x64
- CPU
- Q9450
- Motherboard
- Asus P5Q Deluxe
- Memory
- 4Gb Geil DDR2-800
- Graphics Card(s)
- XFX 1Gb 4870
- Sound Card
- On-Board SoundMAX 7.1
- Monitor(s) Displays
- 22" IIyama 2209HDS
- Screen Resolution
- 1920x1080
- Hard Drives
- 250Gb Samsung Spinpoint
320Gb Samsung F1
- PSU
- 750w Silerstone Strider II
- Case
- Coolermaster HAF-932
- Cooling
- Corsair H50 soon to be custom water
- Keyboard
- Zboard MERC Stealth
- Mouse
- El Cheapo wireless & MS Sidewinder for gaming
- Internet Speed
- 20mb down / 2mb up cable