[VirGnarus]

Re: Shutdown BSOD

You'll want to turn on Driver Verifier for future crashes.

Initial inspection shows that the latest crashdumps occurred while the Indexing Service was running. They involved drive-related I/O (which is what indexing is about). Aside from that, there's no definitive answer that can be derived from these minidumps.

I found a crashdump dated Nov 16 that was a 0x9F bugcheck. I'm not sure if this is related to your current incidents, but this one revealed the Microsoft Firewire driver was trying to remove a device during a power down and got stuck on it. Most likely this is because the device did not respond. This sounds relevant to your shutdown dilemmas, but you yourself will probably be better to discern if this is the case.

 

[VirGnarus]

Re: Shutdown BSOD

So you don't have any Firewire devices hooked up?

Anyways, for the new crashes you received from DV, provide us the minidumps for em (should find them in /Windows/Minidump).

 

[VirGnarus]

Re: Shutdown BSOD

The 1394OCHI driver is one of three that come with Windows for Firewire. You can follow the answer provided in this thread to change it to a legacy version of the driver should you so choose. Also, before you do that, check to ensure that your motherboard has any firmware or chipset driver updates. If you have a separate card that is for Firewire, check for updates on that as well.

As for the latest dump file, it's the same minidump that's present as the last one in your previous JCGriff Report you gave us. If DV has been causing your system to BSOD early at startup, this means that the system was currently at a state that did not permit it to produce a crashdump. This could be caused by a driver related to disk I/O actually being the culprit, or all the drivers necessary to perform disk I/O were not fully loaded yet.

Looking a bit at previous crashdumps, I think the former is what's causing this. I see the Acronis Try&Decide Volume filter driver in the callstack in a previous crash. Plus, most of the crashes occurring lately that I can see were related to file I/O. Given that this driver is pretty old (Aug 2010) you'll want to check for updates to the software, or forgo using it and uninstall it at this time.

There is the potential that while this may be what Driver Verifier is catching as being bad, it may not be related to your previous crashes. However, this would mean this driver still has the potential to cause problems.

 

[VirGnarus]

Re: Shutdown BSOD

The one that specifically stated the driver was back in September, but the filesystem crashes continued to exist into January.

This becomes very difficult for us. We know that Driver Verifier found something, but we cannot receive the information necessary to ascertain what it caught. The closest thing we can do, is to have you read the bluescreen and hopefully there's a "probably caused by:" with the name of a driver.

If you only see the bluescreen for a split second, you'll need to turn off automatic restart at crash. In start menu type "advanced system settings" and access the first option it gives. Then go to "Startup and Recovery" and you should see a checkbox to automatically restart. Uncheck it. Also make sure "Write an event to the system log" is checked and set it to write a small memory dump file.

 

[VirGnarus]

Re: Shutdown BSOD

Also, you may wanna upload to us another JCGriff report. Perhaps the system log will give more details.

 

[VirGnarus]

Re: Shutdown BSOD

That screenshot doesn't show a crash that Driver Verifier would be responsible for. It's a typical scenario where a critical process for Windows got shut down because the memory it attempted to access was erroneous (bad memory, or bad address). Though I reckon you turned Driver Verifier off before this occurred? If you can get a screenshot of a bugcheck that occurred at Windows startup after you restarted from turning on Driver Verifier, we should have a better idea. Otherwise, if this is it, then there's no go.

Anyways, I think it's wise that we go through some hardware testing now:

RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
GPU: MemtestG80/CL - Run twice (if any of the tests work on your GPU)
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

All of these (excluding MemtestG80/CL) are included in the UBCD if you prefer a Live CD environment (which is a good environment to test hardware on). Also, if you want, provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load.

 

[VirGnarus]

Re: Shutdown BSOD

Do remember that in order to actually save settings for Driver Verifier (as in to actually have it take affect) you'll need to do a clean restart of the PC after you finish setting it up. Having the machine crash afterwards without a prior restart will not save the changes you made with Driver Verifier. Keep that in mind. If you are sure you did just that, then again we can start figuring this as being hardware-related.

 

[VirGnarus]

Re: Shutdown BSOD

SPTD.sys is the advanced virtual drive emulation driver that's responsible for emulating SecuROM and stuff for Daemon Tools. It's been known to cause BSODs a lot. Make sure that it's updated to the latest, but even so there's a tendency it'll bug out, in which case you'll have to remove it. Daemon Tools can still emulate drives without it, but will not support security emulation.

Btw, the one that Driver Verifier caught was none other than that pesky Asio.sys driver. It's for one of those nasty, gimmicky, downright buggy motherboard utilities that come with your motherboard. They have an ugly history of causing these problems, and worse yet, they're difficult to remove without having Windows cave in with em. Run the uninstaller for em and see if that does the trick. You may need to do some manually cleaning or with something like Driver Sweeper to take care of em.

 

[VirGnarus]

Re: Shutdown BSOD

No prob. If so far you haven't had any crashes you can go ahead and mark this thread as solved whenever you please. Have a good one! Oh, and remember to turn off Driver Verifier once you're sure everything's cool. Lastly, make sure you uninstalled only the motherboard software, the chipset drivers you'll want to keep (and update if available).