27/11/2012
6:37 - Stop 0x101 - unknown image
6:32 - stop 0x101 - unknown image
6:28 - stop 0x101 - unknown image
5:56 - stop 0x3B - luafv.sys; a windows driver, cannot be the real cause. A deeper search in the dump showed
Code:
fffff880`0ce85440 fffff880`058ccfacUnable to load image \??\C:\Program Files\Folder Guard\FGUARD64.SYS, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for FGUARD64.SYS
*** ERROR: Module load completed but symbols could not be loaded for FGUARD64.SYS
FGUARD64+0xbfac[/COLOR]
WinAbility Folder Guard Device Driver. You need to uninstall it.
It also shows a historic nForce, nvstor64.sys.
Code:
lmvm nvstor64
start end module name
fffff880`018ab000 fffff880`018ea000 nvstor64 (deferred)
Image path: \SystemRoot\system32\DRIVERS\nvstor64.sys
[COLOR=Red] Image name: nvstor64.sys
Timestamp: Wed Jul 01 05:51:51 2009[/COLOR] (4A4AAC1F)
CheckSum: 0003C24D
ImageSize: 0003F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
As nforce controls a big part of the chipset drivers, you must to update it. But you may temporarily get rid of nForce and see what happens.
Get rid of nvstor.
- Right click on "my computer" icon and click "manage" on the context menu.
- It will open the "computer management" window.
- Select "Device Manager" in the left pane, It will list all the existing devices up.
- Expand "Disc Drives" by clicking on the triangle in front of it.
- Select one item under it, right click, uninstall.
- Continue the process for all items under "Disc Drives"
- Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.
It also says, you need to check the storage discs.
- Update your SSD's Firmware (skip it, if it is not a SSD)
- Re-seat the sata and power.
- Run chkdsk /f/r, following the option two of the tutorial Disk Check
- Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
And, you
Scan the system for possible virus infection.
4:41 - stop 0xF7, ultimately
Code:
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=Red]BugCheck F7[/COLOR], {b992ddfa232, 2b992ddfa232, ffffd466d2205dcd, 0}
[COLOR=Red]Probably caused by : nvlddmkm.sys [/COLOR]( nvlddmkm+18eea6 )
Followup: MachineOwner
---------
The version of the display driver is a bit problematic, IMO.
Code:
lmvm nvlddmkm
start end module name
fffff880`0f899000 fffff880`1058d000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
[COLOR=Red]Image name: nvlddmkm.sys
Timestamp: Tue Oct 02 23:51:13 2012[/COLOR] (506B3099)
CheckSum: 00CD4613
ImageSize: 00CF4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Seeing the overall situation, I would suggest you to take three hardware tests, too.
► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.
► Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
► Stress test the CPU.
Hardware - Stress Test With Prime95
Checked the other dumps earlier ... so
Let us know the results, when you are done. If it is problematic to do these stuff in the normal situation, boot into
http://www.sevenforums.com/tutorials/666-advanced-boot-options.html, safe mode with networking, and do these.
