Solved Multiple BSODs, no common activity

QPhysics · Jan 26, 2013

After months of perfectly stable operation, I've suddenly started getting lots of BSODs, six in one day! I haven't installed any new hardware or software; I've run tests on the RAM and hard drive and found no errors; sfc \scannnow says all the system files are fine.
WinDbg lists several different files as being the causes of the BSODs, and there's no common program or activity I'm running/doing that causes the crashes. This morning I turned the computer on to a BSOD.

Help me, SevenForums, you're my only hope.

Arc · Jan 26, 2013

Your actual problem is a very old nForce driver.

Code:

fffff880`033cadf0  fffff880`02f1dd90Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
 nvmf6264+0x3dd90

[/COLOR]---------------------------------------------------------------------------------------------
start             end                 module name
fffff880`02ee0000 fffff880`02f31500   nvmf6264 T (no symbols)           
    Loaded symbol image file: nvmf6264.sys
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
[COLOR=Red]    Image name: nvmf6264.sys
    Timestamp:        Fri Jul 31 05:18:18 2009[/COLOR] (4A723142)
    CheckSum:         0005B9A8
    ImageSize:        00051500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

A search revealed that you are using nForce as the chipset driver, and that includes nvmf6264.sys as the network controller driver. You need to try to update nForce, as it contains not only the network controller, but also storage controller and a lot of other vital drivers.

Go to Drivers - Download NVIDIA Drivers, search for nForce, as per your motherboard's chipset specifications.

Also, Comodo firewall adding to it.

Code:

fffff880`033ca498  fffff880`0175e29bUnable to load image \SystemRoot\System32\DRIVERS\cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
 cmdguard+0xd29b[/COLOR]

Better you uninstall Comodo, and use windows inbuilt firewall.

Let us know the results.

QPhysics · Jan 27, 2013

Two more BSODs after updating the nForce drivers. I was surprised that they were reported as being an issue because I just updated those a month or so ago.
The first BSOD happened when I shut down my music player (MusicBee) last night, so I checked my audio drivers but they all say they're up to date. The second was waiting for me when I turned on the computer, so I don't know what might have been going on in the background when it occurred.

Thanks

Arc · Jan 27, 2013

Both the crash dumps are apparently very silent.

Code:

[COLOR=Red]BugCheck 3B[/COLOR], {c0000005, fffff96000153354, fffff8800874cfa0, 0}

[COLOR=Red]Probably caused by : win32k.sys[/COLOR] ( win32k!HmgSetLock+28 )

Followup: MachineOwner
==================================================================================
[COLOR=Red]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff80003860068, fffff880033b5fc8, fffff880033b5820}

[COLOR=Red]Probably caused by : cng.sys[/COLOR] ( cng!GatherRandomKey+294 )

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

And both of them came with different bugcheck codes.

Though, a deeper search identifies nForce again as failing.

Code:

fffff880`033b63a0  fffff880`01035964*** WARNING: Unable to verify timestamp for nvstor64.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
 nvstor64+0x15964[/COLOR]

Though you have updated it.

Code:

fffff880`01020000 fffff880`0105f000   nvstor64 T (no symbols)           
    Loaded symbol image file: nvstor64.sys
    Image path: \SystemRoot\system32\DRIVERS\nvstor64.sys
 [COLOR=Red]   Image name: nvstor64.sys
    Timestamp:        Fri Apr 09 14:52:41 2010[/COLOR] (4BBEF1E1)
    CheckSum:         0003FFC4
    ImageSize:        0003F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

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.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Also 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.

QPhysics · Jan 27, 2013

I've already run Memtest86+. I put in one stick at a time and ran it, then put all four in together and ran it. No errors.

I'll enable verifier and let you know when I have any results to share.

QPhysics · Jan 29, 2013

I think this is an official candidate for weirdest computer issue ever.
I ran verifier.exe for over 34 hours and, other than being a tiny bit laggy, there were no issues. No crashes, no freezes, no BSODs.
So I turned off verifier and rebooted...and before Windows got me fully logged in...BSOD!
Reboot...start the SF_Diagnostic_Tool to gather the information...and BSOD!

I've never heard of a system that was stable with verifier on and crashed twice in less than 20 minutes when it was shut off. Have you?

Anyway, diagnostic tool output attached...hopefully you'll spot something I missed, because I don't see a thing here that I would point to as the cause.
I was thinking about running verifier on the Microsoft drivers too...but that's just as likely to cause a completely unrelated crash as to actually pinpoint the driver that's actually bad, right?

Arc · Jan 29, 2013

The supplied data says that Comodo is still there, it is starting up with windows, and its safe delete filter causing problems on logon.

Anyway, you have 24 items stored in startup, and among them, Super Antispyware and PC Doctor is not needed in not only startup, but also for the system. Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept the restart.

Auslogics. Nice for XP. Harmful for windows 7.

Which antivirus do you use? I am failing to find any.

QPhysics · Jan 29, 2013

Arc said:
Which antivirus do you use? I am failing to find any.

Comodo Internet Security has an antivirus, firewall, and program control all-in-one.

QPhysics · Jan 29, 2013

The only thing I can find is that when verifier.exe is running, FreshIO doesn't appear in the drivers list. Is it possible that freshIO is the problem (it does have a lot of hardware interaction) and verifier is keeping it from loading instead of crashing when it tries to load? That would be odd behavior for verifier (or maybe I just don't understand verifier as well as I thought I did), but if that fixes it, I'd be happy.

Arc · Jan 29, 2013

As I can say, comodo is the main issue here remaining. Uninstall it using Revo Uninstaller, advanced mode. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download, install and update those, and then run full system scans with both of them, one by one.

QPhysics · Jan 29, 2013

Well, thanks for the attempt, but Comodo is not a problem, has never been a problem, and I'm not going to downgrade to an inferior firewall.
Maybe someone else will pick up the thread or I'll figure something out on my own, but I 'm not going to remove one of the best firewalls around and install that sieve known as Windows Firewall that doesn't even bother checking outgoing programs.

Arc · Jan 29, 2013

It's ok. If you find the issue, let us know.

I have asked the other people to have a look and post their opinions on your issue. Hopefully they will come soon.

Pauly · Jan 29, 2013

Check out Arc`s post count, he knows what he`s talking about, but then you obviously know better, good luck to you !

Dsprague · Jan 29, 2013

clearly he doesn't have a clue I guess these awards and badges are just dumb luck

Arc · Jan 29, 2013

My beloved and respected friends, Quantum Physics is here to have some help with a serious issue. Please help him, if you can suggest him some alternatives. I failed to satisfy him, that's my bad luck; but that does not necessarily mean that what I am saying is the final word.

I posted a lot, achieved almost all the awards of this board, all is true. But, if it is something I overlooked, or I sticked at a particular point like a stubborn, it is an injustice to him, like all of us, he is also a member of our board, may be a new one compared with us. So it is our responsibility to help him the best possible.

Please dont ask him to take my suggestions, suggest something that will work for him.

As my brain is captured at the Comodo point, I may have overlooked something. If you see it from a fresh perspective, something new must come out.

All the best to you all, and cheers!

gregrocker · Jan 29, 2013

I cannot count the number of times since Win7 release that removing Comod:shock: has resolved performance issues. It along with MucAfee are chronic offenders around here.

If an expert BSOD analysis isn't enough for you then work through the Troubleshooting Steps for Windows 7 to see if anything has been missed.

Dave76 · Jan 30, 2013

I agree with Arc's analyses.
The only way you are going to know for sure if Comodo is causing problems for you is to un-install it for testing purposes.
We have seen it cause issues before.
It's your system and your choice.

QPhysics · Jan 30, 2013

Pauly, Dsprague, gregrocker, and Dave76
So I guess it means nothing to you that verifier.exe ran on those drivers and reported them as being fine?
I guess your anecdotal evidence is the only thing that matters while CNET, TechRepublic, Windows Secrets, Gizmodo, etc., etc., etc., having rated Comodo CIS the highest for features AND stability means nothing? Oh, and my own anecdotal evidence of having 8 computers in my home that use it plus another 20 or so that I've installed it on for family and friends?

So does this mean anything to you? I compared the early output from the SF diagnostic tool when I was crashing every few minutes to the output when I have verifier running...and there was one difference in the drivers.txt file. I removed that driver, rebooted without verifier, and no crashes in over 24 hours. Oh, and COMODO CIS is running, in case you want to know.

So, instead of foolishly running a program down with absolutely no evidence that it's causing any problems, maybe you guys should go back to some of those other cases and try to figure out what the real cause of the problem was...you know, the problem that was taking Comodo down in the first place that caused the eventual total crash.

Arc, thank you for the help. You got me poking around in those output files and that's what led me to finding that driver.

Dsprague · Jan 30, 2013

QPhysics said:
Pauly, Dsprague, gregrocker, and Dave76
So I guess it means nothing to you that verifier.exe ran on those drivers and reported them as being fine?
I guess your anecdotal evidence is the only thing that matters while CNET, TechRepublic, Windows Secrets, Gizmodo, etc., etc., etc., having rated Comodo CIS the highest for features AND stability means nothing? Oh, and my own anecdotal evidence of having 8 computers in my home that use it plus another 20 or so that I've installed it on for family and friends?

So does this mean anything to you? I compared the early output from the SF diagnostic tool when I was crashing every few minutes to the output when I have verifier running...and there was one difference in the drivers.txt file. I removed that driver, rebooted without verifier, and no crashes in over 24 hours. Oh, and COMODO CIS is running, in case you want to know.

So, instead of foolishly running a program down with absolutely no evidence that it's causing any problems, maybe you guys should go back to some of those other cases and try to figure out what the real cause of the problem was...you know, the problem that was taking Comodo down in the first place that caused the eventual total crash.

Arc, thank you for the help. You got me poking around in those output files and that's what led me to finding that driver.

Please cite the driver for our purposes so that we may check the other cases as you so stated to insure that this driver was not the cause of these crashes.

QPhysics · Jan 30, 2013

It was
FreshIO.sys
part of the FreshDiagnose program from Fresh Devices (a system diagnostic tool that I'd used for years but won't anymore both because of the crashes and the SF diagnostic tool beats it in every way imaginable).

Solved Multiple BSODs, no common activity

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

An error has occured

My Computer My Computer

At a glance

Whisperer in Darkness

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

Endeavor to Persevere

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Whisperer in Darkness

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer