BSOD 2x this week

[enigm@tic]

Had my 2nd BSOD this week just now, system is clean of any spyware or viruses but under big cpu load is when it crashed - once playing bc2 and just now I was running spybot, malwarebytes and MSE scans at same time.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 19
BCP1: 0000000000000003
BCP2: FFFFFA8006C7DB90
BCP3: FFFFFA8006C7DB90
BCP4: FFFFFA80062A5278
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Here is the minidump file RapidShare: 1-CLICK Web hosting - Easy Filehosting

 

[Lexluethar]

Have you used windows minidump reading program to see what it says?

 

[KSoD]

Bug Check 0x19: BAD_POOL_HEADER

0x3
The pool entry being checked
The read-back flink freelist value
The read-back blink freelist value
The pool freelist is corrupt.
(In a healthy list, the values of Parameters 2, 3, and 4 should be identical.)

Cause

The pool is already corrupted at the time of the current request.
This may or may not be due to the caller.
Resolution

The internal pool links must be walked to figure out a possible cause of the problem.
Then you can use special pool for the suspect pool tags, or use Driver Verifier on the suspect driver. The !analyze extension may be of help in pinpointing the suspect driver, but this is frequently not the case with pool corrupters.

 

[enigm@tic]

Have you used windows minidump reading program to see what it says?

Nah don't know how to use it.


Thanks Mak but what is a pool header? Driver problem?

 

[KSoD]

Well from this sentence:

Then you can use special pool for the suspect pool tags, or use Driver Verifier on the suspect driver.

I would say, yes. It is a driver issue.

Use the link in my signature entitled windbg tutorial and learn how to read the Dump files for yourself. That should tell you the file in question.

Here is what the Dump File says:

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


Loading Dump File [G:\051710-16224-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5ae50
Debug session time: Mon May 17 02:36:23.898 2010 (GMT-4)
System Uptime: 3 days 4:20:36.948
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa8006c7db90, fffffa8006c7db90, fffffa80062a5278}

Probably caused by : ntoskrnl.exe ( nt!_output+a17 )

Followup: MachineOwner

 

[enigm@tic]

Cheers. 99% sure its just ati drivers.