Windows 7: BSOD at random intervals, no specific pattern even after clean install

CliveK · 07 Oct 2012

For the past year I've been having BSODs at completely random intervals. I haven't had any new hardware, I've checked all the drivers and I've even reinstalled Windows 7 Ultimate to no avail. It got so bad and annoying that I even bought a new heatsink and fans, thinking it was the rather high temperature in my tower - but no.

I've got no idea what is causing it. Looking in BlueScreenViewer shows all sorts of strings such as System Service Exception, Memory Management, Bad Pool Header, etc. The gap inbetween August and September's .dmp files was because I did not turn on my computer.

If anyone can help it'd be greatly appreciated! I've attached the grab.

Kindest regards,

Clive.

Arc · 08 Oct 2012

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

CliveK · 08 Oct 2012

Many thanks, Arc. Here are the files as requested.

MSINFO32.zip

SF_09-10-2012.zip

Arc · 08 Oct 2012

It is caused by the Logitech Camera Driver.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck F7, {158, f88005bbabfe, ffff077ffa445401, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : lvrs64.sys ( lvrs64+1932e )

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

Get the updates from Logitech - Support & Software Downloads.

CliveK · 12 Oct 2012

Quote: Originally Posted by Arc

It is caused by the Logitech Camera Driver.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck F7, {158, f88005bbabfe, ffff077ffa445401, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : lvrs64.sys ( lvrs64+1932e )

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

Get the updates from Logitech - Support & Software Downloads.

Unfortunately, after this, BSODs are still occurring.

Arc · 12 Oct 2012

Possible, most possible.
Upload the latest dumps, too.

CliveK · 13 Oct 2012

Quote: Originally Posted by Arc

Upload the latest dumps, too.

Thank you.

Arc · 13 Oct 2012

First of all, your BIOS is somehow old.

Code:

Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=1911]
BiosVendor = Phoenix Technologies, LTD
BiosVersion = ASUS P5N-D ACPI BIOS Revision 0601
BiosReleaseDate = 06/05/2008
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily =  
SystemVersion = System Version
SystemSKU =  
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5N-D
BaseBoardVersion = 1.XX

Try yo update it.

Your network driver, nvidia nforce networking controller, is similarly old.

Code:

 lmvm nvm62x64
start             end                 module name
fffff880`04888000 fffff880`048ebd80   nvm62x64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvm62x64.sys
    Image name: nvm62x64.sys
    Timestamp:        Sat Oct 18 02:31:06 2008 (48F8FD12)
    CheckSum:         0006F977
    ImageSize:        00063D80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You need to update it.

Finally, how many days ago you have updated nvidia display driver? Very recently I think? Unfortunately it is the cause of the crash here.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff9801fa56fe0, fffff9801fa56c57, 434028, 32}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+ca04b )

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

Install an earlier version back, which worked stably.

Let us know the results.

CliveK · 19 Oct 2012

Thank you so much for this. I did all bar the BIOS and didn't have a BSOD for a while, until today... I wanted to make sure it's not something else before I update my BIOS.

SF_19-10-2012.zip

Arc · 20 Oct 2012

It says it is saused by Ndis.sys.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff880009f23d0, 2, 0, fffff80002a59393}

Unable to load image \SystemRoot\system32\drivers\ndis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
Probably caused by : ndis.sys ( ndis+5e47 )

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

And there are some other network related issues in the stack. So better you update your network drivers.

nVidia nForec etheret:

Code:

Name    [00000007] NVIDIA nForce 10/100/1000 Mbps Ethernet
Driver    c:\windows\system32\drivers\nvmf6264.sys (7.3.1.7330, 341.23 KB (349,416 bytes), 04/03/2010 17:26)

Get it from Drivers - Download NVIDIA Drivers, search for nForce.

Let us know the results.

Windows 7: BSOD at random intervals, no specific pattern even after clean install

BSOD at random intervals, no specific pattern even after clean install problems?