Intermittent BSODs - Please Help!

[MagusMagnus]

Alright, finally had another BSOD and have the dump file on it. I am hoping someone can make more sense out of it and pinpoint the issue once and for all so I can get this problem solved (praying it is NOT a hardware problem - been there and done that, don't need to shell out anymore $$$ on it there).

Basically, out of nowhere a few months back I started having my system randomly crash from a error 1001 Bug Check. When it happens, my speakers emit a very odd buzzing noise and the screen kind of goes funny with it too before it BSODs on me.

I had Firefox open, running Silverlight for Netflix as well as Youtube and Flash - that seems to be the congruent factor for these BSODs, but I'm not 100% on that. This only happens once every couple of months but need it to stop to prevent corruption or other damage, I don't wish to perform the third clean install of the OS this year either, but will if absolutely necessary.

No overclocking or anything going on here either.

 

[MagusMagnus]

Also important to note, the OS install is from November 2011 after replacing and installing a brand new hard drive. No malicious code, system is running perfectly other than for these BSODs although I am now also getting a host of Event ID 4107 errors (CAPI2) [never happened before a few weeks ago, other identical BSODs unrelated] and also Event 4 k57nd60a if that helps any further.

 

[zigzag3143]

Zip file is empty try this method.


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.
Please attach the DMP files to your next post not to post one.

If you are overclocking STOP

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. If empty (or non existent) please look in the following folders. C:\windows (the dmp should be called memory.dmp), and C:\windows\LiveKernelReports\Watchdog.

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.

 

[MagusMagnus]

Ah dang, sorry about that. Here's another try at it...

 

[MagusMagnus]

Anyone have any ideas? Having a very difficult time nailing this down on my own.

 

[zigzag3143]

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 Verifier

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.
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 JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[MagusMagnus]

Just wanted to report back (sorry, a lot going on lately haven't had much time to myself). I did not get around to running memory diagnostics. I just decided on a clean install and so far, it would APPEAR that these problems are gone. If not, I'll simply have to make a new thread. These BSOD's were happening very occasionally (1-2 a month, seldom 1-2 in the same day) so I just do not know for sure yet, only did the clean install a little while ago.

But I AM using the latest CCC driver for my GPU so perhaps that was in fact the problem. The system manufacturer had offered absolutely no updated versions tailored to this system and I'd been too timid to try using the generic one until recently (bad experience in the past with doing that). So again, so far... so good. *knock on wood*

 

[writhziden]

If the problems return, you may continue in this thread. I will now be subscribed and receive a message if any new posts appear.

Let us know once you are confident the problem is solved, as well.