Confused about how I obtained a BSOD

[Foffy]

Hey there. This is my first post here, but I figure I'd come here and potentially ask for help to make sure I avoid whatever the hell I had to deal with for the past four minutes. I'll explain how I got BSODs first: This week I recently got a new graphics card, an NVidia GTX 580, for games. I don't think I have the best power supply to use it just yet, so I've withheld on using it so I didn't blow anything out. But, I wanted to give Sniper Elite V2 a try.

It all worked well until I got to the end of the demo, where my PC locked up and froze. After that, with rebooting, I would constantly get random BSOD messages: some would happen on startup, if I switched audio, if I went to control panel, if I was on Chrome. I tried doing a system restore to the most recent point, which had to do with a DirectX update, and even doing that caused the system to BSOD.

I was lucky and I was able to use an older point to restore to use, but I'm now petrified I'm gonna get it again. Surely I didn't blow the motherboard or any serious components as it all works, but I was wondering how I can check and figure out what were the variables that created it, and how to prevent it? The various BSOD messages all had different error messages popping up, so it wasn't a repeat offender or anything. They don't seem to be back for the time being, so I suppose what I want to ask if there was a way I can simply check my computer to see if everything's up to speed, as I'm assuming something was out of whack and essentially broke the boot process after the system caught wind of it.

 

[JMH]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[Foffy]

Alright, I seem to understand some of the procedures you're asking, but I have no clue what I have to do to get them for you. For example, DMP file; how do I get that?

I have the msinfo file you asked for, for starters.

 

[JMH]

Alright, I seem to understand some of the procedures you're asking, but I have no clue what I have to do to get them for you. For example, DMP file; how do I get that?

I have the msinfo file you asked for, for starters.

Refer to my Post 2.
* To ensure minidumps are enabled:
* The procedure:

 

[Foffy]

Hey...crashed again, so here's a rar that seems to cover the two days I've has crashing issues.

EDIT: I have a question. Could I be getting BSODs due to the power supply? I posted here about getting a new GPU, but apparently to be safe I need a new PSU. Right now, I have the new GPU but an old PSU. Could there be issues with the PSU to the potentially more demanding GPU that cause the random crashes? All that I've changed in the past month was the GPU, and a few days later is when I started getting these messages. I haven't been playing games on this out of safety, but I assume watching videos and streams will risk the PSU doing this, or it just randomly happening.

 

[JMH]

Foffy,
Re your questions above lets see what the analysis says...

Here you are.

* Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

When finished you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files


* These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[Foffy]

Wow, the driver thing sounds really overkill..could it really be another driver? Should I wait to see if it happens again now that I've gotten rid of Daemon Tools? I have very little time to do a lot of these tests this week as I have to finish a paper. This stuff seems to require a lot of time..

Daemon Tools always loaded when I booted up my PC, but the most recent crash happened as I was watching a video. I do occasionally get an error message in Chrome that causes Flash to crash, but only if my internet lags out. I'm hoping I can narrow down what it could be before I start doing tests. It's a bad time for this stuff to start happening now..

 

[JMH]

Foffy you came to seek advice as per your thread title

Confused about how I obtained a BSOD.

Our analysis / advice is based on your DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

Our considered advice has followed the analysis.
It is your choice, of course, to take the advice or not.

 

[Foffy]

I plan to, it's just this week may not be the most likely for it. And I had a few more crashes. These tend to happen when something called WerFault.exe can't open programs like Skype and Chrome. In fact, I wrote down the messages in hopes that would create some clarity, as it seems based on BlueScreenView, it only logged one of them.

This one had no reason listed: STOP:0X0000007E (0XFFFFFFFFC0000005, 0XFFFFF8000418F54E, 0XFFFFF880009A9788, 0XFFFFF880009A8FE0)

APC_INDEX_MISMATCH: 0X00000001 (0XFFFFF80004101D70, 0X0000000000000000, 0X000000000000C3FE, 0X0000000000000001)

Some of these are happening before I even see my desktop...some of the time. It doesn't tend to constantly repeat, so I haven't a clue what's the matter.

 

[zigzag3143]

I plan to, it's just this week may not be the most likely for it. And I had a few more crashes. These tend to happen when something called WerFault.exe can't open programs like Skype and Chrome. In fact, I wrote down the messages in hopes that would create some clarity, as it seems based on BlueScreenView, it only logged one of them.

This one had no reason listed: STOP:0X0000007E (0XFFFFFFFFC0000005, 0XFFFFF8000418F54E, 0XFFFFF880009A9788, 0XFFFFF880009A8FE0)

APC_INDEX_MISMATCH: 0X00000001 (0XFFFFF80004101D70, 0X0000000000000000, 0X000000000000C3FE, 0X0000000000000001)

Some of these are happening before I even see my desktop...some of the time. It doesn't tend to constantly repeat, so I haven't a clue what's the matter.

And the new DMPS are where?

 

[Foffy]

Well, I goofed with that...I ran Tuneup Utilities in hopes of cleaning something that may have been the issue, and I deleted those.

However, I have a question for the time being that may be able to help: when I ram Windows Memory Diagnostic over the weekend and it said I had a hardware issue, though I stupidly assumed it was some driver issue. However, I had a feeling, and not having the time this week to monitor lots of tests, I opened up my PC and noticed one of the RAM cards (the closest to the CPU) had a layer of dust on it. I took out the card, cleaned it, put it back in, and ran Windows Memory Diagnostic again. However, no hardware issue was noted now.

This is where my question lies: could my issue, this whole time, been caused by RAM? As I've mentioned, there's no specific way to continue to repeat the method to get a blue screen, as it quite literally is random. I've noticed it happens when I have programs like Skype and Chrome active and my PC usually is on for a while, and they use a lot of memory...could it be the dusty RAM card and the memory usage that cause the PC to BSOD? Because I don't have a clue what driver, if any, could sporadically start causing issues last Saturday and not earlier, as my PC is only 18 months old. The only component I ever changed in it was the GPU, and it works fine.

 

[zigzag3143]

Well, I goofed with that...I ran Tuneup Utilities in hopes of cleaning something that may have been the issue, and I deleted those. Win 7 doesnt need tune up utilities and in fact does it on its on

However, I have a question for the time being that may be able to help: when I ram Windows Memory Diagnostic over the weekend and it said I had a hardware issue, though I stupidly assumed it was some driver issue. However, I had a feeling, and not having the time this week to monitor lots of tests, I opened up my PC and noticed one of the RAM cards (the closest to the CPU) had a layer of dust on it. I took out the card, cleaned it, put it back in, and ran Windows Memory Diagnostic again. However, no hardware issue was noted now. windows diagnostics doesnt stress the ram enough we prefer memtest.

This is where my question lies: could my issue, this whole time, been caused by RAM? As I've mentioned, there's no specific way to continue to repeat the method to get a blue screen, as it quite literally is random. I've noticed it happens when I have programs like Skype and Chrome active and my PC usually is on for a while, and they use a lot of memory...could it be the dusty RAM card and the memory usage that cause the PC to BSOD? Because I don't have a clue what driver, if any, could sporadically start causing issues last Saturday and not earlier, as my PC is only 18 months old. The only component I ever changed in it was the GPU, and it works fine.

Easily could be ram thats why we suggest you run memtest.

 

[Foffy]

Hey there. Seems I'm still getting some messages, but perhaps I've fallen upon what the driver issue may be! I've noticed that the past few times I played a specific game with my PS3 controller, followed by browsing in Chrome, I got a BSOD. However, feeling like it was a hunch, I decided to tamper a bit further (the program was MotionJoy) and the system had another BSOD as I was tampering with the program. This has never happened before, so perhaps now with tampering with it my system has finally pinpointed the culprit. The driver in fact shows up in the most recent crash logs. Could it honestly be the source of all of my problems? And if so, why did it start acting up this month when I got a new GPU? I've installed MotionJoy way back in 2010. When I installed it back then, the driver was never certified, so I had to enable Test Mode on my PC. Could that too have added to the sudden appearance of BSODs? As I've said before, all that's different with my PC in the last three or so weeks is my GPU, which works fine. I noticed my system performed safer when I disabled AVG, Daemon Tools, and Motion Joy to load up at bootup.

 

[zigzag3143]

Hey there. Seems I'm still getting some messages, but perhaps I've fallen upon what the driver issue may be! I've noticed that the past few times I played a specific game with my PS3 controller, followed by browsing in Chrome, I got a BSOD. However, feeling like it was a hunch, I decided to tamper a bit further (the program was MotionJoy) and the system had another BSOD as I was tampering with the program. This has never happened before, so perhaps now with tampering with it my system has finally pinpointed the culprit. The driver in fact shows up in the most recent crash logs. Could it honestly be the source of all of my problems? And if so, why did it start acting up this month when I got a new GPU? I've installed MotionJoy way back in 2010. When I installed it back then, the driver was never certified, so I had to enable Test Mode on my PC. Could that too have added to the sudden appearance of BSODs? As I've said before, all that's different with my PC in the last three or so weeks is my GPU, which works fine. I noticed my system performed safer when I disabled AVG, Daemon Tools, and Motion Joy to load up at bootup.

In post 2 we asked you to run memtest, and driver verifier. We have seen nothing that says you have run BOTH.

The most recent crashes were still caused by a memory exception.

Your self help is making it more difficult and will result in it taking longer.