ANalyse minidump help

[raedbenz]

Attached is the my minidump as a result of the verifier when BSOD appeared.
Sorry the SF Diagnostic Tool crashed while running.
Please advise..
Thanks

 

[tlarseth]

I can't read the dumps while at work, have you verified Drivers are up to date, computer is Virus free, and please tell us if you are getting the BsoD while doing a specific task, and what that task is.

 

[raedbenz]

Thanks for the reply.
the BSOD is random.
i have Microsoft security essential, and nothing has been reported.
here is a link of the minidump log i analyzed using kd tool.
i guess drivers are up to date.
any hints ?

Thanks

 

[x BlueRobot]

[COLOR="red"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/COLOR]

BugCheck 1000007E, {ffffffff80000003, fffff80002adcdd0, fffff88003b4bc28, fffff88003b4b480}

Probably caused by : [COLOR="Red"]Wdf01000.sys[/COLOR] ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Image path: [COLOR="red"]\SystemRoot\system32\drivers\Wdf01000.sys[/COLOR]
    Image name: Wdf01000.sys
    Timestamp:       [COLOR="red"] Thu Jul 26 03:25:13 2012[/COLOR] (5010AA89)

Driver Reference Table - Wdf01000.sys

No real faulty drivers are pointed to:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Test for memory issues:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Check for any hardware compatibility issues with Windows 7:

• Windows 7 | Upgrade Advisor

Could you please upload a .NFO file:

Start rb: > Type: msinfo32 > File, Save

Please back post your results

 

[raedbenz]

I run memtest86+ up to 9 passes with no errors.
NFO file is here .

Thanks

 

[x BlueRobot]

I run memtest86+ up to 9 passes with no errors.
NFO file is here .

Thanks

Attach the file itself (place in a compressed folder) and then upload in your next post.

 

[raedbenz]

oops sorry..
here is the .nfo compressed.
i run the Windows 7 | Upgrade Advisor and all is OK apart from SpeedFan program.
Thanks

 

[x BlueRobot]

oops sorry..
here is the .nfo compressed.

Thanks, having a look at it now

 

[x BlueRobot]

Run these programs:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Uninstall SuperAntiSpyware:

Start Menu\Programs\SUPERAntiSpyware

Both MSE and SuperAntiSpyware provide real-time protection and therefore are clashing together, install:

• Malwarebytes : Free anti-malware download

Keep MSE installed and use in conjuction with Malwarebytes; download the free version not the free trail (untick the free trail box during installation)

Download:

• CPUID HWMonitor

To monitor the temperature of your hardware during idle and when running the stress test.

Post back your results

 

[raedbenz]

hello,

cpu temperature are around 30 C.
I got again BSOD while shutting down.
this is the View attachment 242214.
it is the same process: System, and driver Wdf01000.sys.
any hints thanks?

 

[x BlueRobot]

[COLOR="red"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/COLOR]

Probably caused by : [COLOR="Red"]Wdf01000.sys[/COLOR] ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )

[B]Usual causes:[/B]  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Have you uninstalled SpeedFan (compatiblity issues reported by the Windows 7 Upgrade Advisor) and removed Super AntiSpyware?

Have you ran Driver Verifer for least 24 hours (following the steps within the link) and ran a stress test for the graphics card?

 

[raedbenz]

[COLOR=red]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/COLOR]

Probably caused by : [COLOR=Red]Wdf01000.sys[/COLOR] ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )

[B]Usual causes:[/B]  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Have you uninstalled SpeedFan (compatiblity issues reported by the Windows 7 Upgrade Advisor) and removed Super AntiSpyware?

Have you ran Driver Verifer for least 24 hours (following the steps within the link) and ran a stress test for the graphics card?

I just uninstalled speedfan. Super AntiSpyware was uninstalled 2 days ago.
i alse enabled driver verifier following the link above. I dont have a graphic card.
so lets wait see what happens.
if a BSOD occurs i will upload the minidump. if you need further info/log files please let me know.
Thanks for your reply.

 

[x BlueRobot]

Okay good, and run Driver Verifier for at least 24 hours, if any BSOD occurs before the given time period then you can stop the test.

 

[raedbenz]

Okay good, and run Driver Verifier for at least 24 hours, if any BSOD occurs before the given time period then you can stop the test.

i got BSOD again when shutting down. Here is the View attachment 242358.

 

[x BlueRobot]

Driver Verifier pointed to the same Wdf01000.sys driver.

• Wdf01000.sys - Driver Reference Table

I recommend running some hard-drive diagnostics with:

• http://www.sevenforums.com/tutorials/433-disk-check.html
• SeaTools | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Make sure that both the tick boxes are selected with Disk Check, and run tests with Seagate for Windows.

Please post a screenshot from with the information in which Crystal Disk provides:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Please use the System File Checker to scan for and attempt to repair corrupted Windows files:

• http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

 

[raedbenz]

i run the SeaTools the long tests and all Passed.
attached is the CrystalDiskInfo View attachment 242428.
i have not yet done the rest.
i ll try to do them today.
Thanks

 

[x BlueRobot]

That's good to see, seems like your hard-drive is in good condition and not contributing to the crashes.

 

[raedbenz]

i run SFC /SCANNOW and did not find any corrupt files..
also I ran disk check and it is ok
Thanks

 

[x BlueRobot]

Any more crashes?

Uninstall Real VNC:

Start Menu\Programs\RealVNC

3rd party remote control programs can contribute to the Stop 0x7E bug check, please uninstall this program at least for testing and the duration of trying to make your system more stable.

[B]Usual causes:[/B]  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, [COLOR="Red"]3rd party remote control[/COLOR]

Have you installed Malwarebytes yet?

Please scan for the latest Windows Updates, and install all the Important and Optional Updates available:

Start rb: > Type: Windows Updates > Select and Install Updates/Scan for Updates

Windows has it's own built-in remote control service if needed:

• http://www.sevenforums.com/tutorials/3922-remote-desktop-connection-rdc-network.html

 

[raedbenz]

RealVNC was installed but it was not running..
I did uninstall it anyway..and remember verifier is not running.
Since then i have restarted my PC 3 times and no BSOD.
My notice is that the shutdown is slow. it takes in total around 90 - 120 sec.
as soon as i click shutdown the hdd light keeps busy for about a minute while win7 shutdown screen is displayed. after that hdd light stopps blinking, and still displays the shutdown screen for another minute.
any ideas ?
i have modified the waittiketokill to to 2000msec.
Do you think if verifier was running during shutdown it will throw and exception bcoz of the hdd long activity ?

Thanks