Tech Support Forum banner
Status
Not open for further replies.
1 - 20 of 20 Posts

·
Registered
Joined
·
11 Posts
Discussion Starter · #1 ·
Hi, I've been getting BSODs randomly, mostly when I set my computer to shutdown at a certain time using a widget (Autoshutdown Restyled). It doesn't happen all the time, only sometimes. Just then, I tried shutting down by going through the start menu and I got a bluescreen. It said "Memory_Management".

· OS?
Windows 7 Ultimate x64

· What was original installed OS on system?
Windows 7 Ultimate x64

· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
It is an OEM software which I bought seperatly

· Age of system (hardware):
2 or 3 years ago

· Age of OS installation - have you re-installed the OS?
I haven't re-installed the OS

· CPU
i7 920

· Video Card
ATI 5770

· MotherBoard
ASUS P6T

· Power Supply - brand & wattage
Corsair TX-750

I hope someone can solve my problem :smile: Thanks in advance
 

Attachments

·
Registered
Joined
·
2,210 Posts
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.
 

·
Registered
Joined
·
11 Posts
Discussion Starter · #3 ·
Re: Shutdown BSOD

Thanks for the super fast reply! :flowers: I turned on Driver Verifier and it kept bluescreening before loading Windows so I'm guessing I have a driver issue.

About the Microsoft Firewire Driver, I have no clue as to why it crashed since I usually safety eject my devices but that's fine.
 

·
Registered
Joined
·
2,210 Posts
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).
 

·
Registered
Joined
·
2,210 Posts
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.
 

·
Registered
Joined
·
11 Posts
Discussion Starter · #7 ·
Re: Shutdown BSOD

I just did as you suggested for using the legacy 1394OCHI driver and I uninstalled Acronis awhile back. I guess it didn't full uninstall since you see it in a crash I had. I'll give Driver Verifier a go and will keep you posted :wink:
 

·
Registered
Joined
·
11 Posts
Discussion Starter · #8 · (Edited)
Re: Shutdown BSOD

Just ran the Driver Verifier again and it seems like the Firewire Driver wasn't the issue (But it feels as if my computer is faster but it could be my imagination) because it had another bluescreen. It happens half way when the "Windows Starting" gui is loading up. Thank you so far for all the support :thumb:
 

·
Registered
Joined
·
2,210 Posts
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.
 

·
Registered
Joined
·
11 Posts
Discussion Starter · #11 ·
Re: Shutdown BSOD

I just attached an image of the bluescreen that I had taken with my phone camera. It doesn't look that informative about the cause of the problem but I could be wrong. I'll have to do the JCGriff report tomorrow because it's pretty late here and I have work :facepalm:
 

Attachments

·
Registered
Joined
·
2,210 Posts
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.
 

·
Registered
Joined
·
11 Posts
Discussion Starter · #14 ·
I'm currently doing the tests now so I'm replying via my phone. That bluescreen was the only blue screen I got when turning on Driver Verifier so I turned it back off. I'll let you know asap about the test results.
 

·
Registered
Joined
·
2,210 Posts
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.
 

·
Registered
Joined
·
11 Posts
Discussion Starter · #16 ·
Yes, I setup Driver Verifier then it says to restart in order for it to take effect which I had no problem doing. Its only when it starts up from the restart that it crashes. Well I guess we'll just have to wait and see what the outcome of the tests are.
 

·
Registered
Joined
·
11 Posts
Discussion Starter · #17 ·
Re: Shutdown BSOD

So far, all the tests have passed (Memtest86+, MemtestG80/CL, & Seatools) but I haven't done the Prime95. After the tests, I decided to do some trial and error with Driver Verifier and I found out that the blank BSOD on Windows start-up was caused by "sptd.sys" (I found out by picking only that driver in Driver Verifier). Also, when I enabled only "asio.sys", it bluescreened when I was logged into Windows. I attached the DMP file in this reply.
 

Attachments

·
Registered
Joined
·
2,210 Posts
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.
 

·
Registered
Joined
·
11 Posts
Discussion Starter · #19 ·
Re: Shutdown BSOD

Thanks for the advice. I uninstalled Daemon Tools and all the ASUS software that came with my motherboard. I had to manually delete the Asio.sys driver because it wasn't on Driver Sweep. Driver Verifier hasn't picked up any other buggy drivers so it seems like everything is working :smile: Thank you for all the help, it was much appreciated :thumb:
 

·
Registered
Joined
·
2,210 Posts
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).
 
1 - 20 of 20 Posts
Status
Not open for further replies.
Top