Solved Help my computer I just built keeps having BSOD!

[mrbc]

BSOD while watching movies/gaming just built computer

Around 3 days ago I just finished putting together my computer and since then I have had BSOD 3 times, twice while gaming and once while watching a movie. I have no idea why they are happening, here is the report windows gave me after it happened.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 000000000006168C
BCP3: 0000000000000000
BCP4: 0000000000190BFC
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\052212-15927-01.dmp
C:\Users\Matt\AppData\Local\Temp\WER-26551-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Anyone wondering here are my computer specs;
Processor:AMD A8 3870K with integrated radeon 6550D graphics
Memory: [FONT=Verdana, Arial, Helvetica, sans-serif] Mushkin Enhanced Silverline Stiletto 8GB 2X4GB PC3-10666 DDR3-1333 9-9-9-24 Dual Channel Memory Kit [/FONT]
Motherboard:[FONT=Verdana, Arial, Helvetica, sans-serif] Gigabyte A75-UD4H ATX FM1 Motherboard
HDD: [/FONT]Western Digital Caviar Blue 500GB 16MB Cache 7200RPM 3.5IN SATA Internal Hard Drive OEM

Powersupply: 550 Watt antec

 

[zigzag3143]

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.

 

[mrbc]

Here is the minidump files

 

[zigzag3143]

These crashes were caused by memory corruption 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"IRP Logging and Force Pending I/O Requests. 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)

 

[mrbc]

Alright ive done the driver verifier and confirmed its a driver issue

 

[mrbc]

What should I do now? and what is a raid update? thx for all the help btw

 

[zigzag3143]

Alright ive done the driver verifier and confirmed its a driver issue

If your computer has crashed with verifier running upload the DMP, if not keep running it. May take as much as 36 hours.

 

[mrbc]

here they are

 

[zigzag3143]

here they are

Finally. Driver verified x2 and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd.

Remove and replace

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 you're done you can use this Freeware:

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

Using MagicISO to create ISO image files

 

[mrbc]

THANK YOU SO MUCH for all the help, I just +repped you and if I could rep you more I would

 

[zigzag3143]

THANK YOU SO MUCH for all the help, I just +repped you and if I could rep you more I would

Thank you and its our pleasure. Good luck.

 

[mrbc]

So i just had another BSOD >< just when I thought it was over lol; heres the dmp file

 

[mrbc]

Dmp file

 

[zigzag3143]

Dmp file

Verified but blamed on an OS file which isnt likely. While we are waiting I would remove the following.

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 you're done you can use this Freeware:

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

Using MagicISO to create ISO image files

 

[mrbc]

For some reason that SPTD program would'nt work for me, instead ive manually change the reg edit value on "start" to 4 to force sptd.sys to not start when windows boots. Seems to be working so far computers been on for a few hours and still no BSOD

 

[zigzag3143]

For some reason that SPTD program would'nt work for me, instead ive manually change the reg edit value on "start" to 4 to force sptd.sys to not start when windows boots. Seems to be working so far computers been on for a few hours and still no BSOD

Or just rename sptd.sys>>sptd.bak so it cant load. Either way Daemon tools in this iteration and one other seems to cause BSOD's on some systems

 

[mrbc]

First thing I did was remove daemon tools and installed magic iso; never would have guessed that was the cause, been using daemon for years. By the way, how do you read those minidump files?

 

[zigzag3143]

First thing I did was remove daemon tools and installed magic iso; never would have guessed that was the cause, been using daemon for years. By the way, how do you read those minidump files?

We use a tool called WinDeBugger.

If you feel this is solved please use the red triangle and ask that this be marked solved.

K