Frequent BSOD's, can't find a clear pattern. dump attached

wikke · 10 Feb 2012

Update:

- I physically removed the Sweex PCI wifi card and connected an ethernet cable
- Temperates = good
- PSU = CORSAIR CMPSU-650TX (650 W)
- replacement NIVIDIA GPU is still installed.. so It cant be GPU card afaik

2 more crashes since then. Meaning 2 more Minidumps

I made screenshots of BIOS settings (21 pics).
If anyone is interested, I'm willing to post them.

[In that case anyone know a good host ? Or should I zip them up?]

writhziden · 11 Feb 2012

Code:


Loading Dump File [E:\BSODDmpFiles\wikke\021012-23790-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e90670
Debug session time: Fri Feb 10 12:32:01.842 2012 (GMT-7)
System Uptime: 0 days 3:19:25.606
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa00047f3180, 2, 1, fffff88011f870a4}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa00047f3180, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88011f870a4, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa100
 fffffa00047f3180 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
fffff880`11f870a4 48897108        mov     qword ptr [rcx+8],rsi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff88002479bf0 -- (.trap 0xfffff88002479bf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa00047f3178
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011f870a4 rsp=fffff88002479d80 rbp=fffffa80047eb3b0
 r8=fffff88002479da0  r9=0000000000000000 r10=fffff880031d3a60
r11=fffff8a00552be00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30:
fffff880`11f870a4 48897108        mov     qword ptr [rcx+8],rsi ds:fffffa00`047f3180=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc71e9 to fffff80002cc7c40

STACK_TEXT:  
fffff880`02479aa8 fffff800`02cc71e9 : 00000000`0000000a fffffa00`047f3180 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02479ab0 fffff800`02cc5e60 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`047eb5b8 : nt!KiBugCheckDispatch+0x69
fffff880`02479bf0 fffff880`11f870a4 : fffff880`11e4077b fffffa80`047eb5b8 fffffa80`047eb5a8 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02479d80 fffff880`11fb1ae1 : fffffa80`0348c000 fffffa80`0346b010 00000000`00000000 fffff880`11e84122 : dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30
fffff880`02479dd0 fffff880`11f78c93 : fffffa80`0348c000 fffffa80`03538180 fffff8a0`0dbc5150 fffffa80`0346b010 : dxgmms1!VidSchiAllocateQueuePacket+0x45
fffff880`02479eb0 fffff880`11eba98e : fffff8a0`00c00000 fffff8a0`00c00000 00000000`00000001 00000000`00000000 : dxgmms1!VidMmTerminateAllocation+0x177
fffff880`02479f90 fffff880`11ebe79c : fffff8a0`0bf40c00 fffff880`0247a3e0 fffffa80`0346c000 fffff880`11e853af : dxgkrnl!DXGDEVICE::TerminateAllocations+0x166
fffff880`02479fe0 fffff880`11ec0e57 : fffff8a0`00c00000 fffff880`0247a0f0 00000000`fffdb001 fffff800`02cd1801 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`0247a070 fffff960`001cf51a : ffffffff`8701062a fffffa80`03a29550 00000000`00000020 00000000`72cf6168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0247a330 fffff800`02cc6ed3 : 00000000`00000002 fffff880`0247a3e0 00000000`047b2340 00000000`fffdb000 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0247a360 00000000`72d1141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0024cb08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72d1141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
fffff880`11f870a4 48897108        mov     qword ptr [rcx+8],rsi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

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

Try uninstalling firefox and re-installing the latest version.

Also, follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

Download the latest drivers for your display card(s)
Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Expand Display adapters
Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the latest driver for the display cards once Windows starts

Alternatively:

Login as an adminstrative user
Download the latest drivers for your display card(s)
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Expand Display adapters
Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the latest driver for the display cards once Windows starts

wikke · 20 Feb 2012

writhziden said:

Try uninstalling firefox and re-installing the latest version.

Done today.

writhziden said:

Restart your computer after uninstalling drivers for all display cards. Install the latest driver for the display cards once Windows starts

Done today.
Also made changes to BIOS (put most settings on auto)
Then ran Prime to stress the machine. BSOD'd after 1-2 hrs.
Then tried scan for viruses from a distance (don't really suspect this but u never know). BSOD'ed.

writhziden · 20 Feb 2012

Code:


Loading Dump File [D:\Kingston\BSODDmpFiles\wikke\022012-24226-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e45670
Debug session time: Mon Feb 20 10:31:16.052 2012 (GMT-7)
System Uptime: 0 days 0:34:15.815
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff82003cc4340, 1, fffff8800140d7d1, 5}

Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys

Could not read faulting driver name
Probably caused by : MpFilter.sys ( MpFilter+d7d1 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff82003cc4340, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800140d7d1, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eaf100
 fffff82003cc4340 

FAULTING_IP: 
MpFilter+d7d1
fffff880`0140d7d1 48894108        mov     qword ptr [rcx+8],rax

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031566b0 -- (.trap 0xfffff880031566b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a003ded678 rbx=0000000000000000 rcx=fffff82003cc4338
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800140d7d1 rsp=fffff88003156840 rbp=0000000000000000
 r8=0000000000000008  r9=ffffffffffffffff r10=fffff8a003d16b40
r11=fffff8a002b44968 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
MpFilter+0xd7d1:
fffff880`0140d7d1 48894108        mov     qword ptr [rcx+8],rax ds:00ae:fffff820`03cc4340=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c273bf to fffff80002c7cc40

STACK_TEXT:  
fffff880`03156548 fffff800`02c273bf : 00000000`00000050 fffff820`03cc4340 00000000`00000001 fffff880`031566b0 : nt!KeBugCheckEx
fffff880`03156550 fffff800`02c7ad6e : 00000000`00000001 fffff820`03cc4340 00000000`00000400 fffff8a0`02b449b0 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`031566b0 fffff880`0140d7d1 : 00000000`00000000 fffff8a0`02b449b0 00000000`00000000 fffff880`0119c2c8 : nt!KiPageFault+0x16e
fffff880`03156840 00000000`00000000 : fffff8a0`02b449b0 00000000`00000000 fffff880`0119c2c8 fffff8a0`03f03840 : MpFilter+0xd7d1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MpFilter+d7d1
fffff880`0140d7d1 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  MpFilter+d7d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MpFilter

IMAGE_NAME:  MpFilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9cc801

FAILURE_BUCKET_ID:  X64_0x50_MpFilter+d7d1

BUCKET_ID:  X64_0x50_MpFilter+d7d1

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

Loading Dump File [D:\Kingston\BSODDmpFiles\wikke\022012-23758-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e9c670
Debug session time: Mon Feb 20 08:59:53.853 2012 (GMT-7)
System Uptime: 0 days 0:02:59.242
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff88011076ecb}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+2fecb )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88011076ecb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f06100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+2fecb
fffff880`11076ecb 41b811000000    mov     r8d,11h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003f42640 -- (.trap 0xfffff88003f42640)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88011076e79 rbx=0000000000000000 rcx=fffff88011c35fa0
rdx=0000000080000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011076ecb rsp=fffff88003f427d0 rbp=0000000000000000
 r8=000000000000ff00  r9=0000000000000000 r10=fffffa8003ecda28
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x2fecb:
fffff880`11076ecb 41b811000000    mov     r8d,11h
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd31e9 to fffff80002cd3c40

STACK_TEXT:  
fffff880`03f424f8 fffff800`02cd31e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03f42500 fffff800`02cd1e60 : 00000000`0346d230 fffffa80`01c5a4e0 fffffa80`03dbc480 fffff880`03f42940 : nt!KiBugCheckDispatch+0x69
fffff880`03f42640 fffff880`11076ecb : fffff880`00006300 fffff880`03f42940 fffffa80`00000000 fffffa80`02514000 : nt!KiPageFault+0x260
fffff880`03f427d0 fffff880`00006300 : fffff880`03f42940 fffffa80`00000000 fffffa80`02514000 fffff880`11076d1e : nvlddmkm+0x2fecb
fffff880`03f427d8 fffff880`03f42940 : fffffa80`00000000 fffffa80`02514000 fffff880`11076d1e fffffa80`02514000 : 0xfffff880`00006300
fffff880`03f427e0 fffffa80`00000000 : fffffa80`02514000 fffff880`11076d1e fffffa80`02514000 fffffa80`03dbc480 : 0xfffff880`03f42940
fffff880`03f427e8 fffffa80`02514000 : fffff880`11076d1e fffffa80`02514000 fffffa80`03dbc480 fffffa80`03d6a550 : 0xfffffa80`00000000
fffff880`03f427f0 fffff880`11076d1e : fffffa80`02514000 fffffa80`03dbc480 fffffa80`03d6a550 fffffa80`03ecd8b0 : 0xfffffa80`02514000
fffff880`03f427f8 fffffa80`02514000 : fffffa80`03dbc480 fffffa80`03d6a550 fffffa80`03ecd8b0 00000000`00000000 : nvlddmkm+0x2fd1e
fffff880`03f42800 fffffa80`03dbc480 : fffffa80`03d6a550 fffffa80`03ecd8b0 00000000`00000000 00000000`00000000 : 0xfffffa80`02514000
fffff880`03f42808 fffffa80`03d6a550 : fffffa80`03ecd8b0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`03dbc480
fffff880`03f42810 fffffa80`03ecd8b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00006300 : 0xfffffa80`03d6a550
fffff880`03f42818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00006300 00000000`00000c98 : 0xfffffa80`03ecd8b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+2fecb
fffff880`11076ecb 41b811000000    mov     r8d,11h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+2fecb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+2fecb

BUCKET_ID:  X64_0xD1_nvlddmkm+2fecb

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

Loading Dump File [D:\Kingston\BSODDmpFiles\wikke\021712-12745-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5a000 PsLoadedModuleList = 0xfffff800`02e9f670
Debug session time: Fri Feb 17 07:42:01.090 2012 (GMT-7)
System Uptime: 0 days 4:33:21.854
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa0002960380, 2, 1, fffff880041640a4}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa0002960380, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880041640a4, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f09100
 fffffa0002960380 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
fffff880`041640a4 48897108        mov     qword ptr [rcx+8],rsi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff88006513d30 -- (.trap 0xfffff88006513d30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa0002960378
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880041640a4 rsp=fffff88006513ec0 rbp=fffffa800400f5a0
 r8=fffff88006513ee0  r9=0000000000000000 r10=fffff880009eba60
r11=fffff8a00326d7e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30:
fffff880`041640a4 48897108        mov     qword ptr [rcx+8],rsi ds:fffffa00`02960380=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd61e9 to fffff80002cd6c40

STACK_TEXT:  
fffff880`06513be8 fffff800`02cd61e9 : 00000000`0000000a fffffa00`02960380 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`06513bf0 fffff800`02cd4e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0400f7a8 : nt!KiBugCheckDispatch+0x69
fffff880`06513d30 fffff880`041640a4 : fffffa80`0371d950 fffffa80`0400f7a8 fffffa80`0400f798 00000000`00000014 : nt!KiPageFault+0x260
fffff880`06513ec0 fffff880`0418eae1 : fffffa80`0347b000 fffffa80`03461010 00000000`0042ad30 00000000`000001d4 : dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30
fffff880`06513f10 fffff880`04155c93 : fffffa80`0347b000 fffffa80`034bf6b0 fffff8a0`0d7fe240 fffffa80`03461010 : dxgmms1!VidSchiAllocateQueuePacket+0x45
fffff880`06513ff0 fffff880`0409798e : fffff8a0`01409000 fffff8a0`01409000 00000000`00000001 00000000`00000000 : dxgmms1!VidMmTerminateAllocation+0x177
fffff880`065140d0 fffff880`0409b79c : fffff8a0`03140700 fffff880`06514520 00000000`00000000 fffff880`040623af : dxgkrnl!DXGDEVICE::TerminateAllocations+0x166
fffff880`06514120 fffff880`0409de57 : fffff8a0`01409000 fffff880`06514230 fffff8a0`046fc901 fffff880`04063001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`065141b0 fffff960`0024f5e2 : 00000000`0018c6e0 fffffa80`01dceb60 00000000`00000020 00000000`72c76168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`06514470 fffff800`02cd5ed3 : fffffa80`01dceb60 fffff880`06514520 00000000`00000018 00000000`00004000 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`065144a0 00000000`72c9141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0018c818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72c9141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
fffff880`041640a4 48897108        mov     qword ptr [rcx+8],rsi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

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

Loading Dump File [D:\Kingston\BSODDmpFiles\wikke\021612-23774-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e64670
Debug session time: Thu Feb 16 08:14:14.039 2012 (GMT-7)
System Uptime: 0 days 4:45:00.818
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa800435a620, fffffa000435a620, fffffa800435a620}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )

Followup: Pool_corruption
---------

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa800435a620, the pool entry being checked.
Arg3: fffffa000435a620, the read back flink freelist value (should be the same as 2).
Arg4: fffffa800435a620, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002dc970f to fffff80002c9bc40

STACK_TEXT:  
fffff880`03fec998 fffff800`02dc970f : 00000000`00000019 00000000`00000003 fffffa80`0435a620 fffffa00`0435a620 : nt!KeBugCheckEx
fffff880`03fec9a0 fffff800`02dcb1a1 : 00000000`00000000 fffffa80`044112c0 00000000`00000000 00000000`00000228 : nt!ExDeferredFreePool+0xcbb
fffff880`03feca30 fffff800`02ca5afc : fffffa80`04411300 fffffa80`0219b5d0 fffffa80`43504c41 fffff800`02fa929c : nt!ExFreePoolWithTag+0x411
fffff880`03fecae0 fffff800`02f92f44 : fffffa80`0219b5d0 00000000`00000000 fffffa80`0355db60 00000000`00000000 : nt!ObfDereferenceObject+0xdc
fffff880`03fecb40 fffff800`02f934f4 : 00000000`0000071c fffffa80`0219b5d0 fffff8a0`00c1c8b0 00000000`0000071c : nt!ObpCloseHandleTableEntry+0xc4
fffff880`03fecbd0 fffff800`02c9aed3 : fffffa80`0355db60 fffff880`03fecca0 00000000`00000000 00000000`00000000 : nt!ObpCloseHandle+0x94
fffff880`03fecc20 00000000`7781140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00bdf628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7781140a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+cbb
fffff800`02dc970f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+cbb

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb

Followup: Pool_corruption
---------

Appears to be caused by Microsoft Security Essentials. Other possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
Probably caused by your nVidia graphics card driver.
Probably caused by DirectX, your graphics card driver, or your graphics card.
Possible cause is Drivers...

Proceed with the following...

Download MSE, uninstall MSE, and install MSE again. Also, make sure your network adapter drivers are up to date.

Update the following drivers:

AtiPcie.sys
AsUpIO.sys

Code:

AtiPcie	fffff880`01999000	fffff880`019a1000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys
AsUpIO	fffff880`03f7e000	fffff880`03f84000	Sun Jul 05 20:21:38 2009 (4a515fb2)	0000edf8		AsUpIO.sys

I also note you have an SSD. See the Quote: regarding SSDs by usasma in post #2 of BSOD when hibernating.
Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.
1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts
Alternatively:
1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

wikke · 22 Feb 2012

writhziden said:

Proceed with the following...

Download MSE, uninstall MSE, and install MSE again. Also, make sure your network adapter drivers are up to date.

Uninstalled MSE for now - replaced with Avast

writhziden said:

Update the following drivers:

AtiPcie.sys
AsUpIO.sys

Code:

AtiPcie    fffff880`01999000    fffff880`019a1000    Tue May 05 09:00:22 2009 (4a005486)    000134c7        AtiPcie.sys
AsUpIO    fffff880`03f7e000    fffff880`03f84000    Sun Jul 05 20:21:38 2009 (4a515fb2)    0000edf8        AsUpIO.sys

-Downloaded AMD Chipset Drivers (+ AMD AHCI & AMD USB3) v 12.1 of date 1/25/2012. ( AMD Chipset Drivers )

But this contains the same AtiPcie.sys version of May 05 09:00:22 2009... So just did reinstall afaik.

-downloaded the latest Asus Update Utility and immediatly removed it. Manually renamed the file because program uninstall didn't remove the file AsUpIO.sys

writhziden said:

I also note you have an SSD. See the Quote: regarding SSDs by usasma in post #2 of BSOD when hibernating.

-Updated Corsair firmware to latest 2.4 !
-Power settings are on highest performance, with Hibernation disabled.

Did sfc /scannow to verify windows files, was 100% ok.
Now doing a prime torture run. I will keep you posted.

---
EDIT:

Another crash. Points to fltmgr.sys
dump included. Any more ideas?
---
EDIT2 :
Many more crashes today !
1 BSOD while starting a Hitman Pro scan.
It seems to get worse and worse!

writhziden · 14 Mar 2012

Sorry, I missed the .dmp files that were added.

Code:


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


Loading Dump File [D:\Kingston\BSODDmpFiles\wikke\022312-12729-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e92670
Debug session time: Thu Feb 23 11:52:21.166 2012 (UTC - 6:00)
System Uptime: 0 days 0:07:51.929
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80003ddb008, 0, fffff80002c8f6cb, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PsGetProcessSessionId+1b )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff80003ddb008, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002c8f6cb, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efc100
 fffff80003ddb008 

FAULTING_IP: 
nt!PsGetProcessSessionId+1b
fffff800`02c8f6cb 8b4008          mov     eax,dword ptr [rax+8]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  HitmanPro36_x6

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880083e7540 -- (.trap 0xfffff880083e7540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80003ddb000 rbx=0000000000000000 rcx=fffffa8003adeb30
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8f6cb rsp=fffff880083e76d8 rbp=fffff880083e7ca0
 r8=0000000000000000  r9=0000000002d58658 r10=fffffa8003adeb00
r11=fffffa8004565640 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!PsGetProcessSessionId+0x1b:
fffff800`02c8f6cb 8b4008          mov     eax,dword ptr [rax+8] ds:8658:fffff800`03ddb008=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c743f0 to fffff80002cc9c40

STACK_TEXT:  
fffff880`083e73d8 fffff800`02c743f0 : 00000000`00000050 fffff800`03ddb008 00000000`00000000 fffff880`083e7540 : nt!KeBugCheckEx
fffff880`083e73e0 fffff800`02cc7d6e : 00000000`00000000 fffff800`03ddb008 fffff880`083e7600 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`083e7540 fffff800`02c8f6cb : fffff800`02f8587d 00000000`00000000 fffff880`083e7ca0 00000000`0000e6d0 : nt!KiPageFault+0x16e
fffff880`083e76d8 fffff800`02f8587d : 00000000`00000000 fffff880`083e7ca0 00000000`0000e6d0 00000000`02d58558 : nt!PsGetProcessSessionId+0x1b
fffff880`083e76e0 fffff800`02fd39f6 : 00000000`02d4a270 00000000`00008000 fffff880`083e7870 00000000`00000000 : nt!ExpGetProcessInformation+0xce
fffff880`083e7830 fffff800`02fd4449 : 00000000`02d4a270 00000000`00000000 00000000`00008000 00000000`000006d5 : nt!ExpQuerySystemInformation+0xfb4
fffff880`083e7be0 fffff800`02cc8ed3 : 00000000`00000001 00000000`02d5227a 00000000`02ce6501 00000000`00310000 : nt!NtQuerySystemInformation+0x4d
fffff880`083e7c20 00000000`77bf167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0695f778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bf167a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PsGetProcessSessionId+1b
fffff800`02c8f6cb 8b4008          mov     eax,dword ptr [rax+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PsGetProcessSessionId+1b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x50_nt!PsGetProcessSessionId+1b

BUCKET_ID:  X64_0x50_nt!PsGetProcessSessionId+1b

Followup: MachineOwner
---------
Loading Dump File [D:\Kingston\BSODDmpFiles\wikke\022312-12916-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02eaa670
Debug session time: Thu Feb 23 11:43:31.215 2012 (UTC - 6:00)
System Uptime: 0 days 1:46:10.604
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff880112c0ecb}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+2fecb )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880112c0ecb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f14100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+2fecb
fffff880`112c0ecb 41b811000000    mov     r8d,11h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880035b9640 -- (.trap 0xfffff880035b9640)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880112c0e79 rbx=0000000000000000 rcx=fffff88011e7ffa0
rdx=0000000080000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880112c0ecb rsp=fffff880035b97d0 rbp=0000000000000000
 r8=000000000000ff00  r9=0000000000000000 r10=fffffa8004232188
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x2fecb:
fffff880`112c0ecb 41b811000000    mov     r8d,11h
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ce11e9 to fffff80002ce1c40

STACK_TEXT:  
fffff880`035b94f8 fffff800`02ce11e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`035b9500 fffff800`02cdfe60 : 00000000`00000000 fffffa80`0424b530 fffffa80`041e7400 fffff880`035b9940 : nt!KiBugCheckDispatch+0x69
fffff880`035b9640 fffff880`112c0ecb : fffff880`000000d8 fffff880`035b9940 fffffa80`00000000 fffffa80`026f1000 : nt!KiPageFault+0x260
fffff880`035b97d0 fffff880`000000d8 : fffff880`035b9940 fffffa80`00000000 fffffa80`026f1000 fffff880`112c0d1e : nvlddmkm+0x2fecb
fffff880`035b97d8 fffff880`035b9940 : fffffa80`00000000 fffffa80`026f1000 fffff880`112c0d1e fffffa80`026f1000 : 0xfffff880`000000d8
fffff880`035b97e0 fffffa80`00000000 : fffffa80`026f1000 fffff880`112c0d1e fffffa80`026f1000 fffffa80`041e7400 : 0xfffff880`035b9940
fffff880`035b97e8 fffffa80`026f1000 : fffff880`112c0d1e fffffa80`026f1000 fffffa80`041e7400 fffffa80`04231010 : 0xfffffa80`00000000
fffff880`035b97f0 fffff880`112c0d1e : fffffa80`026f1000 fffffa80`041e7400 fffffa80`04231010 fffffa80`04232010 : 0xfffffa80`026f1000
fffff880`035b97f8 fffffa80`026f1000 : fffffa80`041e7400 fffffa80`04231010 fffffa80`04232010 00000000`00000000 : nvlddmkm+0x2fd1e
fffff880`035b9800 fffffa80`041e7400 : fffffa80`04231010 fffffa80`04232010 00000000`00000000 00000000`00000000 : 0xfffffa80`026f1000
fffff880`035b9808 fffffa80`04231010 : fffffa80`04232010 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`041e7400
fffff880`035b9810 fffffa80`04232010 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000000d8 : 0xfffffa80`04231010
fffff880`035b9818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`000000d8 00000000`0000088a : 0xfffffa80`04232010


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+2fecb
fffff880`112c0ecb 41b811000000    mov     r8d,11h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+2fecb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+2fecb

BUCKET_ID:  X64_0xD1_nvlddmkm+2fecb

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

Loading Dump File [D:\Kingston\BSODDmpFiles\wikke\022312-11341-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02ea9670
Debug session time: Thu Feb 23 09:56:21.849 2012 (UTC - 6:00)
System Uptime: 0 days 2:29:03.238
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa0004593508, 0, fffff80002d09690, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiInsertNode+20 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa0004593508, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d09690, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f13100
 fffffa0004593508 

FAULTING_IP: 
nt!MiInsertNode+20
fffff800`02d09690 493b4018        cmp     rax,qword ptr [r8+18h]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800762c730 -- (.trap 0xfffff8800762c730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000019d40 rbx=0000000000000000 rcx=fffffa00045934f0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d09690 rsp=fffff8800762c8c8 rbp=fffffa8002a22b28
 r8=fffffa00045934f0  r9=00000000000004c8 r10=fffffa8001c04330
r11=fffffa8002a22bd8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiInsertNode+0x20:
fffff800`02d09690 493b4018        cmp     rax,qword ptr [r8+18h] ds:8fff:fffffa00`04593508=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8b347 to fffff80002ce0c40

STACK_TEXT:  
fffff880`0762c5c8 fffff800`02c8b347 : 00000000`00000050 fffffa00`04593508 00000000`00000000 fffff880`0762c730 : nt!KeBugCheckEx
fffff880`0762c5d0 fffff800`02cded6e : 00000000`00000000 fffffa00`04593508 fffffa80`03f6ac00 fffffa80`02a22790 : nt! ?? ::FNODOBFM::`string'+0x44711
fffff880`0762c730 fffff800`02d09690 : fffff800`02d15d82 fffffa80`01b60060 00000000`00000000 00000000`19dd8fff : nt!KiPageFault+0x16e
fffff880`0762c8c8 fffff800`02d15d82 : fffffa80`01b60060 00000000`00000000 00000000`19dd8fff 00000000`00000098 : nt!MiInsertNode+0x20
fffff880`0762c8d0 fffff800`02ff9c6b : fffffa80`02a22790 fffffa80`04281010 fffffa80`01c04330 00000000`00000000 : nt!MiGetWsAndInsertVad+0x62
fffff880`0762c910 fffff800`02ffa32b : fffffa80`04281010 fffffa80`02a22790 fffff880`0762cb50 fffffa80`01b60060 : nt!MiMapViewOfDataSection+0x45b
fffff880`0762c9f0 fffff800`02ffa78e : fffffa80`00000001 fffffa80`02a22790 fffff880`0762cb50 00000000`00000020 : nt!MiMapViewOfSection+0x20b
fffff880`0762cae0 fffff800`02cdfed3 : 00000000`00000f60 fffffa80`01b60060 00000000`005be238 fffff800`00000001 : nt!NtMapViewOfSection+0x2bd
fffff880`0762cbb0 00000000`77cd159a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`005be218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cd159a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiInsertNode+20
fffff800`02d09690 493b4018        cmp     rax,qword ptr [r8+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiInsertNode+20

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiInsertNode+20

BUCKET_ID:  X64_0x50_nt!MiInsertNode+20

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

Loading Dump File [D:\Kingston\BSODDmpFiles\wikke\022312-13478-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e8e670
Debug session time: Wed Feb 22 17:31:06.000 2012 (UTC - 6:00)
System Uptime: 0 days 0:41:18.763
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff82003f235d0, 0, fffff88001116626, 5}


Could not read faulting driver name
Probably caused by : fltmgr.sys ( fltmgr!TreeUnlinkNoBalance+6 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff82003f235d0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88001116626, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef8100
 fffff82003f235d0 

FAULTING_IP: 
fltmgr!TreeUnlinkNoBalance+6
fffff880`01116626 488b5118        mov     rdx,qword ptr [rcx+18h]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800314f600 -- (.trap 0xfffff8800314f600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80018cbb60 rbx=0000000000000000 rcx=fffff82003f235b8
rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001116626 rsp=fffff8800314f790 rbp=fffffa8004696ec8
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80002c49000
r11=0000000000000398 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fltmgr!TreeUnlinkNoBalance+0x6:
fffff880`01116626 488b5118        mov     rdx,qword ptr [rcx+18h] ds:0008:fffff820`03f235d0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c703bf to fffff80002cc5c40

STACK_TEXT:  
fffff880`0314f498 fffff800`02c703bf : 00000000`00000050 fffff820`03f235d0 00000000`00000000 fffff880`0314f600 : nt!KeBugCheckEx
fffff880`0314f4a0 fffff800`02cc3d6e : 00000000`00000000 fffff820`03f235d0 00000000`00000000 fffff820`03f235b8 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`0314f600 fffff880`01116626 : 00000000`00000000 fffffa80`0199b150 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0314f790 fffff880`011142c8 : 00000000`00000703 fffff8a0`03f47070 fffff8a0`73634946 fffff8a0`03f470a0 : fltmgr!TreeUnlinkNoBalance+0x6
fffff880`0314f7c0 fffff880`011322af : fffffa80`04696e98 fffff880`01132178 fffff8a0`03f47028 fffff880`0110f000 : fltmgr!TreeUnlinkMulti+0x148
fffff880`0314f810 fffff880`01134341 : fffffa80`04696e50 fffffa80`022b2010 00000000`00000130 fffff8a0`03cde140 : fltmgr!DeleteNameCacheNodes+0x9f
fffff880`0314f850 fffff880`011343fb : fffffa80`022b2010 00000000`00000000 fffffa80`022b2010 00000000`000007ff : fltmgr!CleanupStreamListCtrl+0x51
fffff880`0314f890 fffff800`02f7e90e : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`03f33901 : fltmgr!DeleteStreamListCtrlCallback+0x6b
fffff880`0314f8c0 fffff880`012ddbac : fffff8a0`03cde140 fffffa80`018cbb60 fffff880`0314f998 00000000`00000706 : nt!FsRtlTeardownPerStreamContexts+0xe2
fffff880`0314f910 fffff880`012e2cc1 : 00000000`00000000 00000000`00000000 fffff800`02e66200 00000000`00000001 : Ntfs!NtfsDeleteScb+0x108
fffff880`0314f950 fffff880`0125b85c : fffff8a0`03cde040 fffff8a0`03cde140 fffff800`02e66200 fffff8a0`03f335c0 : Ntfs!NtfsRemoveScb+0x61
fffff880`0314f990 fffff880`0125aa3f : fffff8a0`03cde010 fffff800`02e66260 fffff880`0314fb01 fffffa80`04785010 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`0314f9c0 fffff880`012e063c : fffffa80`04785010 fffffa80`022a8180 fffff8a0`03f33590 fffff8a0`03f33928 : Ntfs!NtfsTeardownFromLcb+0x2af
fffff880`0314fa50 fffff880`012620e2 : fffffa80`04785010 fffffa80`04785010 fffff8a0`03f33590 fffff880`0314fc00 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`0314fad0 fffff880`012f0193 : fffffa80`022a8180 fffff800`02e66260 fffff8a0`6366744e 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`0314fb10 fffff880`012df357 : fffffa80`04785010 fffff8a0`03f336c0 fffff8a0`03f33590 fffffa80`022a8180 : Ntfs!NtfsCommonClose+0x353
fffff880`0314fbe0 fffff800`02cd0001 : 00000000`00000000 fffff800`02fbc900 fffff800`02ec7801 fffffa80`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`0314fcb0 fffff800`02f60fee : 00000000`00000000 fffffa80`018cbb60 00000000`00000080 fffffa80`018be9e0 : nt!ExpWorkerThread+0x111
fffff880`0314fd40 fffff800`02cb75e6 : fffff880`02f63180 fffffa80`018cbb60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0314fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fltmgr!TreeUnlinkNoBalance+6
fffff880`01116626 488b5118        mov     rdx,qword ptr [rcx+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  fltmgr!TreeUnlinkNoBalance+6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME:  fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7929c

FAILURE_BUCKET_ID:  X64_0x50_fltmgr!TreeUnlinkNoBalance+6

BUCKET_ID:  X64_0x50_fltmgr!TreeUnlinkNoBalance+6

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

Possibly caused by Hitman Pro... Other possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
Caused by your graphics card driver.
Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Thanks to Dave76 for help understanding possible causes.

Check your memory with the following tests:

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.

Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.

Download the latest drivers for your display card(s)
Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Expand Display adapters
Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the latest driver for the display cards once Windows starts

Alternatively:

Login as an adminstrative user
Download the latest drivers for your display card(s)
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Expand Display adapters
Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the latest driver for the display cards once Windows starts

Fix any data corruption on your SSD and HDD.

Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

wikke · 14 Mar 2012

Brought it back to where I purchased the components

they already found out was a faulty GFX card and faulty memory..
with probably PSU or Motherboard borked too.

thanks everyone.. this was impossible to pinpoint though

writhziden · 14 Mar 2012

Sounds like some major catastrophe happened to your system.

Glad you got it sorted, though.

Hardware is difficult to pinpoint through online debugging. It takes a lot of steps, and quite frankly, it often takes a fair amount of luck, too.

wikke · 14 Mar 2012

I wasted a bunch of time with this.
But I gained some more knowledge in the process.
Furthermore, all the components were still under warranty, so all is fine I guess :)

cheers