BSOD every few days on wake up. Help translate dmp files.

Arc said:

Pcfreak123 said:

Have a great day :)

You too. :)

Ohh Archie, I am trying. Today is just happened again... take a look at the most recent dump. Gosh how could this be possible.

Arc said:

Pcfreak123 said:

Have a great day :)

You too. :)

Whenever you get a chance please take a look at the latest post. Thank you.

Arc said:

Can you apply the 347.09 WHQL display driver and see how it goes?

Before installing it, uninstalled the installed driver using DDU.

Let us know how it goes.
________________________________

BugCheck 19, {3, fffff8a00e672f60, 0, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )

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

Archie,

Ive had 2 within the last 24 hours check these out i think one is ntfs and the other bad pool header, can you see if you spot anything? ...But I'm not sure if there is something in there pointing us somewhere. We gotta catch this there is no way we are not seeing it. Im anaylizing away.

Arc said:

The same bugcheck, but not very informative.

Code:

BugCheck 19, {20, fffff8a01a9de000, fffff8a01a9dec00, 5c00100}

GetPointerFromAddress: unable to read from fffff800034c3100
GetUlongFromAddress: unable to read from fffff800034c31c0
Probably caused by : ntkrnlmp.exe ( nt!CmpDeleteKeyObject+60a )

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

The carsh dump itself saus that driver verifier may be helpful there.

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.

Let us trust it?

So this has to be a driver issue? Run driver verifier again and hope to catch the right one ?

Arc said:

Apparently stop 0x19's are driver related issues. But a failing RAM can disguise any sort of issue, and that is why we suggested for memtest86+ too, in the earlier time.

Well I ran the test and memory was fine and just to be on the safe side I went and got brand new memory of the same kind and ran test again with no problems. So I would think it is safe to rule memory out.

Can all these errors be hdd related? I ask because my raw read error rate went from 314 to 316 i know its small but was jw.

Arc said:

If you have any doubt, you may take the Data Lifeguard Diagnostic for Windows. Take both the short test and the extended test. Let us know the results.

If the HDD is free from errors, and if you feel that it is a good call, can you plan a clean reinstall? As we are not getting any specific error but the issue continues, let us see how it goes with a vanilla install? Then adding the drivers and programs one by and and observing at which point the issue recreates?

If the issue continues even in th vanilla stage, we have to be sure that it is some sort of hardware related issue.

Arc, the harddrive is 100% clean. Also I can try to a whole new clean install but let me say that I did install from a OEM windows 7 ultimate disc, which I dont think contained any bloatware..If I am correct? Does this matter?