BSOD WDF01000.sys

I have attached a zip of my minidump folder. Getting random BSOD's. Appears to happen when PC is sitting idle for the most part. Started shortly after Win 7 Pro 64-bit install. This is from an HP 6560b laptop.

It seemed that windbg only shows wdf01000.sys as the problem, but I'm not sure if my symbols are correct or if debugging correctly. I can't seem to find what might actually be causing the wdf01000.sys or what I should reinstall to fix the problem.

I've ran several hardware diagnostics and it doesn't seem to find anything wrong with either the hard drive or RAM chips. There are 2 4GB chips.

Please let me know if more info is needed and thanks for the help!!!!!!

Hi there,

Your intel gigabit network driver is being flagged,

Code:

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

Driver Reference Table - e1c62x64.sys

Code:

start             end                 module name
fffff880`03000000 fffff880`03056000   e1c62x64 T (no symbols)           
    Loaded symbol image file: e1c62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Timestamp:       Wed May 04 17:19:01 2011 (4DC1ECF5)
    CheckSum:         00056BAB
    ImageSize:        00056000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It's from 2011, try updating that driver.

This is the preferred method for uploading info about crashes,

Blue Screen of Death (BSOD) Posting Instructions

If you keep having problems after updating that driver, use the tool provided to upload all the info.

Thanks a ton!! I will try to update that. Can I ask how you found that from the minidump? I am using winDbg and all it would show me is wdf01000.sys. How did you find the e1c62x64.sys? Do you think it might just be my symbols or something, or do you debug these a different way?

You're welcome, try using this method to find that driver,

!thread > enter

Then find the "base" & "limit" numbers,

dps limit base > enter

(Ctrl+C to copy & Ctrl+V to paste)

Then just scroll till you see that output I showed you.

koolkat77 said:

I had mentioned that ---

koolkat77 said:

Sometimes analyzing the BSOD deeper gives you idea where its driver's failing

The common commands for checking drivers are lmtsm and lm, I use both of these often :)

How to check which driver is failing between crashes?:

It's the !thread command that you need to run.

1. Hit enter and you will then see a few numbers like this:

2. Copy and paste the numbers from “Limit and Base” but before that type “dps”

And hit enter.

3. It will be busy but expand after a while. Then scroll down slowly and see which driver is failing there..

For instance, in the image above you can see nvlddmkm.sys failing.