Continuing saga of BSOD

patfield · 15 Nov 2010

I posted last week with regard to my BSOD problems. I have an HP Pavilion a6242n desktop with a 320 g hardrive, 3 g ram, AMD Athlon 64 x 2 processor and a Nvidia Geforce 6150 SE graphics. The system cam preloaded with Vista 32 bit. I did a clean install of Windows 7 Ultimate and it kept blue screening. I sent in my reports and was advised to go back to Vista, which I did, but still got blue screens. Finally my system wouldn't even turn on, it would not recognize my hard drive. I replaced the hard drive with a 500 g brand new drive. I installed Windows 7 on it and everything was running OK, until I tried to play Bejewelled on Facebook. My whole system froze up (but didn't blue screen at this point) and the monitor hummed really loudly. I rebooted and soon thereafter it blue screened. I tried to run in safe mode, but it still blue screened. I let it rest overnight and it actually turned on this morning. So far it hasn't blue screened today, but I haven't tried to do anything graphic intensive. I suspected and was advised on this forum that my video card had caused my other crashes. I am including the latest BSOD dump report and the perfmon report. Can you tell me if it is still my video that is causing the BSOD. I updated my drivers when I installed Windows 7 for the second time on the new drive. Any help would be appreciated.

CarlTR6 · 16 Nov 2010

I looked at your five latest dumps. Only one of them indicated a video driver and that driver is up to date. However, you do have some outdated drivers loading on your system. The 2008 drivers are quite obsolete. Outdated drivers can and do cause memory corruption and BSOD's. I suggest that you take care of updating these drivers before moving on to testing hardware.

nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers

nvstor.sys Wed May 20 02:45:37 2009 - Drivers - Download NVIDIA Drivers

VSTBS26.SYS Wed Oct 15 20:54:06 2008 - Conexant HSF_HWB2 WDM driverConexant: Support

VSTCNXT6.SYS Wed Oct 15 20:52:22 2008 - Conexant SoftK56 Modem Driver Conexant: Support

VSTDPV6.SYS Wed Oct 15 20:57:45 2008 - Conexant SoftK56 Modem Driver Conexant: Support

Several of these drivers can cause the symptoms you described.

How to Update drivers -

- I have listed links to most of the drivers in the code box above. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

If you need with the drivers, please post.

After you update the above drivers, you can test your video card using Furmark following the instructions in the tutorial below. Be sure to monitor your temps while testing.

Video Card - Stress Test with Furmark

Post back with your results and let us know how your systems is doing.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01c12000 PsLoadedModuleList = 0xfffff800`01e4fe50
Debug session time: Sun Nov 14 19:43:30.979 2010 (GMT-5)
System Uptime: 0 days 0:03:47.604
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff80001e119e0, fffffa8004e1f9e0, fffff80001e119e0}

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

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

0: 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: fffff80001e119e0, the pool entry being checked.
Arg3: fffffa8004e1f9e0, the read back flink freelist value (should be the same as 2).
Arg4: fffff80001e119e0, 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:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80001db5d6f to fffff80001c82740

STACK_TEXT:  
fffff880`0408ab08 fffff800`01db5d6f : 00000000`00000019 00000000`00000003 fffff800`01e119e0 fffffa80`04e1f9e0 : nt!KeBugCheckEx
fffff880`0408ab10 fffff880`018ebcc8 : 00000000`00000000 00000000`000002b0 00000000`00000103 00000000`00000000 : nt!ExDeferredFreePool+0xa56
fffff880`0408ac00 fffff880`018f345b : fffffa80`032fb810 fffffa80`000002b0 00000000`00000001 00000000`0000002b : rdyboost!SmdRBDispatchReadWrite+0x3ac
fffff880`0408acd0 fffff880`01898db4 : fffffa80`034ed190 fffff880`01f98520 fffffa80`0244c1a0 00000000`00000000 : rdyboost!SmdDispatchReadWrite+0xb7
fffff880`0408ad00 fffff880`0121554a : fffff880`01f98498 00000000`00000000 00000000`00000000 00000000`00000000 : volsnap! ?? ::FNODOBFM::`string'+0x57b
fffff880`0408ad30 fffff800`01c7a5c7 : 00000000`01fbfd3c 00000000`7efd7000 00000000`7efd5000 00000000`01fbfde8 : Ntfs!NtfsStorageDriverCallout+0x16
fffff880`0408ad60 fffff800`01c7a581 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`01f98360 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a56
fffff800`01db5d6f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a56

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+a56

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56

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

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0284c000 PsLoadedModuleList = 0xfffff800`02a89e50
Debug session time: Sun Nov 14 16:55:57.144 2010 (GMT-5)
System Uptime: 0 days 0:42:36.220
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {c1d000c2, 6, 0, fffff800028a6cd3}

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+211a4 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000c1d000c2, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800028a6cd3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af40e0
 00000000c1d000c2 

CURRENT_IRQL:  6

FAULTING_IP: 
nt!KeInsertQueueDpc+13
fffff800`028a6cd3 440fb74902      movzx   r9d,word ptr [rcx+2]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1b4e0 -- (.trap 0xfffff88002f1b4e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88004837150 rbx=0000000000000000 rcx=00000000c1d000c0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028a6cd3 rsp=fffff88002f1b670 rbp=0000000000000000
 r8=0000000000000000  r9=fffff88004837150 r10=0000000000000001
r11=fffff88002f1b7b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeInsertQueueDpc+0x13:
fffff800`028a6cd3 440fb74902      movzx   r9d,word ptr [rcx+2] ds:4000:00000000`c1d000c2=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028bbca9 to fffff800028bc740

STACK_TEXT:  
fffff880`02f1b398 fffff800`028bbca9 : 00000000`0000000a 00000000`c1d000c2 00000000`00000006 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b3a0 fffff800`028ba920 : 00000000`00000000 fffffa80`04494000 fffffa80`04494000 fffffa80`046aa000 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b4e0 fffff800`028a6cd3 : fffffa80`04494000 00000000`00000000 fffffa80`03cc7000 fffffa80`04494000 : nt!KiPageFault+0x260
fffff880`02f1b670 fffff880`048371a4 : fffffa80`04494000 00000000`00000000 00000000`00000000 fffff880`049af14c : nt!KeInsertQueueDpc+0x13
fffff880`02f1b700 fffffa80`04494000 : 00000000`00000000 00000000`00000000 fffff880`049af14c 00000000`c1d00000 : nvlddmkm+0x211a4
fffff880`02f1b708 00000000`00000000 : 00000000`00000000 fffff880`049af14c 00000000`c1d00000 00000000`00000000 : 0xfffffa80`04494000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+211a4
fffff880`048371a4 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+211a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c8b048a

FAILURE_BUCKET_ID:  X64_0xA_nvlddmkm+211a4

BUCKET_ID:  X64_0xA_nvlddmkm+211a4

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

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02807000 PsLoadedModuleList = 0xfffff800`02a44e50
Debug session time: Sun Nov 14 19:15:38.428 2010 (GMT-5)
System Uptime: 0 days 0:03:45.379
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff80003c37130, 0, 0, fffff80002873b3b}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )

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

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

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff80003c37130
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff80002873b3b

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff80003c378c8 -- (.exr 0xfffff80003c378c8)
ExceptionAddress: fffff80002873b3b (nt!KiInterruptDispatchNoLock+0x000000000000006b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

TRAP_FRAME:  fffff80003c37970 -- (.trap 0xfffff80003c37970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000001312d0 rbx=0000000000000000 rcx=fffffa8003ab9410
rdx=fffffa8003f70388 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002873b3b rsp=fffff80003c37b08 rbp=fffff80003c37b88
 r8=0000000000000000  r9=00000000eb62fc01 r10=000000000008a562
r11=fffff800029f1e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiInterruptDispatchNoLock+0x6b:
fffff800`02873b3b 0f2945f0        movaps  xmmword ptr [rbp-10h],xmm0 ss:fffff800`03c37b78=00000000000000000000000000000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002876ca9 to fffff80002877740

STACK_TEXT:  
fffff800`03c36878 fffff800`02876ca9 : 00000000`0000003d fffff800`03c37130 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff800`03c36880 fffff800`02872fe9 : fffffa80`03bd9806 fffffa80`056a6e50 fffff800`03c37130 fffff800`028a4668 : nt!KiBugCheckDispatch+0x69
fffff800`03c369c0 fffff800`0289d40d : 00000000`0010001f fffff800`03c37130 fffff800`03c37970 fffff800`03c378c8 : nt!KiInterruptHandler+0x29
fffff800`03c369f0 fffff800`028a4a90 : fffff800`029c6954 fffff800`03c36a68 fffff800`03c378c8 fffff800`02807000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`03c36a20 fffff800`028b19ef : fffff800`03c378c8 fffff800`03c37130 fffff800`00000000 00000000`00000001 : nt!RtlDispatchException+0x410
fffff800`03c37100 fffff800`02876d82 : fffff800`03c378c8 00000000`00000000 fffff800`03c37970 fffff800`02e12460 : nt!KiDispatchException+0x16f
fffff800`03c37790 fffff800`0287568a : fffffa80`03be8050 fffff880`02d7316f fffff800`03c379c0 fffffa80`03be8050 : nt!KiExceptionDispatch+0xc2
fffff800`03c37970 fffff800`02873b3b : 00000000`b9d4cd01 fffffa80`023e9780 fffff800`03c37b01 fffffa80`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff800`03c37b08 00000000`00000010 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x6b
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x10


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInterruptHandler+29
fffff800`02872fe9 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiInterruptHandler+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

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

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02851000 PsLoadedModuleList = 0xfffff800`02a8ee50
Debug session time: Sun Nov 14 19:16:40.954 2010 (GMT-5)
System Uptime: 0 days 0:00:26.029
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 80, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000080
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880023e6830 -- (.trap 0xfffff880023e6830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000ebd0007 rbx=0000000000000000 rcx=fffffa800233cc90
rdx=0000000000000081 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028c4905 rsp=fffff880023e69c0 rbp=fffff880023e6a40
 r8=0000000000000080  r9=fffff68000018d70 r10=fffffa800233cc90
r11=fffff880023e6c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ExpInterlockedPopEntrySListFault16:
fffff800`028c4905 498b08          mov     rcx,qword ptr [r8] ds:f480:00000000`00000080=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000286db7a to fffff800028c1740

STACK_TEXT:  
fffff880`023e66c8 fffff800`0286db7a : 00000000`0000001a 00000000`00041287 00000000`00000080 00000000`00000000 : nt!KeBugCheckEx
fffff880`023e66d0 fffff800`028bf82e : 00000000`00000000 00000000`00000002 00000000`0001b100 fffff8a0`00eb6050 : nt! ?? ::FNODOBFM::`string'+0x42ba5
fffff880`023e6830 fffff800`028c4905 : 00000000`00000002 fffff800`028dee9d 80000000`1a500867 fffff880`023e6a40 : nt!KiPageFault+0x16e
fffff880`023e69c0 fffff800`028dee9d : 80000000`1a500867 fffff880`023e6a40 fffffa80`03c6ec28 fffffa80`03c6ec28 : nt!ExpInterlockedPopEntrySListFault16
fffff880`023e69d0 fffff800`028db9c6 : 00000000`00000001 00000000`031ae000 fffff880`023e6c20 fffff680`00018d70 : nt!MiResolveDemandZeroFault+0x14d
fffff880`023e6ac0 fffff800`028bf82e : 00000000`00000001 00000000`072ef2f0 00000000`00000101 00000000`00000000 : nt!MmAccessFault+0x5c6
fffff880`023e6c20 00000000`749ef6ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`004df088 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x749ef6ac


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42ba5
fffff800`0286db7a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42ba5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

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

patfield · 16 Nov 2010

My BSOD's are so frequent I cannot even use safe mode to try to update the drivers. Even when I boot into safe mode, it crashes. What can I do now?

CarlTR6 · 22 Nov 2010

I suggest that you run Memtest to test your RAM following this tutorial. Memtest runs outside of windows. You can follow the structions for downloading and burning a CD on another computer.

RAM - Test with Memtest86+

Continuing saga of BSOD

Continuing saga of BSOD

can't even use safe mode