Random BSODs, New Computer Build, minidumps included

[SevenChurches]

This is my first computer build, completed in September. Desktop has been used infrequently but will need to be used daily here soon. This computer is primarily going to be used for flash animation and video editing.

There has been no pattern when receiving a BSOD. From what I can recall, I've gotten them:

1) Right after log in.
2) While running CeltX screenwriting software.
3) While running Anime Studio Pro 9.

Minidumps are attached. If you need any more information about my build, I'll try to answer.

Thanks for any of the help you can give me!

 

[koolkat77]

Welcome to Sevenforums

Perform a Clean boot:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Take memtest in the following manner.

Test your RAM with Memtest86+. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

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

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

:info: Errors are sometimes found after 8 passes.
:tip: Do this test overnight, before going to bed.

*How does the computer perform in Safe Mode?​

 

[SevenChurches]

Small update.

Ran Memtest for 10 passes and got no errors, so I think I can rule out memory problems.

Going to now try a clean boot and see if I get any more BSODs.

 

[koolkat77]

Performance in safe mode as well.

 

[SevenChurches]

I've run my computer in Safe Mode a bit and there were no problems so far, but probably not enough to make a determination.

 

[koolkat77]

For how many hours were you in safe mode?
Did the clean boot help?

 

[SevenChurches]

I performed the clean boot. All non Microsoft services were disabled. After about two days, I got another blue screen.

Like all of my others, bug check code 0x00000109 caused by ntoskrnl.exe+7f1c0

However, when I went back to msconfig and checked to make sure my services were still disabled, avast! Antivirus was running once again. Could that be my problem?

As for safe mode, I probably haven't spent more than an hour running in that.

 

[koolkat77]

Upload the newer files.

Yes avast! can sometimes be a reason for BSOD-s. Please uninstall and replace with MSE.

• avast! Uninstall Utility | Download aswClear for avast! Removal

MSE is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software:-

1. Microsoft Security Essentials - Free Antivirus for Windows
2. Malwarebytes - Free
3. http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html
​

:warn: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Run the System File Checker. It allows the user to scan for and restore corruptions in Windows system files.

• 
  1. Click on the rb:
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

 

[SevenChurches]

Uninstalled avast! and installed Microsoft Security Essentials and Malwarebytes. Those scans found nothing.

Will now proceed with the file checker and the disk check.

Here are my latest dump files too.

 

[SevenChurches]

File check and disk check also complete. No errors.

I'll post back if I get any more BSODs.

 

[SevenChurches]

Got another blue screen today. I turned on my computer, logged in, and it was basically just sitting there idling for about 20 minutes when the blue screen came up.

 

[koolkat77]

My computer is at the repair shop. I will take a look at the files as soon as I can.

Upload a screenshot of your hard disk using crystal disk info and summary tab using speccy:

• CrystalDiskInfo - Software - Crystal Dew World
• Speccy - System Information - Free Download
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website.

• Hard Drive Diagnostic Procedure

Driver Verifier

Use verifier for 36 hours. Then send us the BSOD reports

Driver Verifier
I'd suggest that you first backup your data 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/Windows 7 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"
- 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.

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 [/B]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).

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.
Driver Verifier - Enable and Disable

 

[SevenChurches]

Alright, I have a screen grab of CrystalDiskInfo and Speccy.

Ran the hard drive test and the results said that my hard drive passed.

Got another BSOD, so will be including my newest minidumps.

Will start running the Driver Verifier next. I do have a question about that though. Does the verifier need to be run for the full 36 hours or just until the next blue screen?

 

[koolkat77]

Till the next blue screen.

The dumps of 11th & 13th come with BCC 109.

STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION  
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

BugCheck 109, {a3a039d89e8a6558, b3b7465ef10734ae, fffff80003000e40, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
............
BugCheck 109, {a3a039d89ee8564f, b3b7465ef166254d, fffff80002fd4510, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!_imp_NtOpenSymbolicLinkObject+8 )
............
BugCheck 109, {a3a039d89edf272a, b3b7465ef15cf628, fffff80002fda510, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!_imp_NtOpenSymbolicLinkObject+8 )

After verifier I would suggest that you test ram sticks individually.

 

[SevenChurches]

Alright, I finally got a blue screen while running the driver verifier. However, these blue screens gave me different error codes than before. Bug codes 3b and e3. They happened right as my computer was booting up and applying updates.

So now, I can go back and change the driver verifier and change the settings back to normal?

I'll check the RAM sticks individually as well.

 

[SevenChurches]

And another blue screen just a minute ago, RESOURCE_NOT_OWNED.

 

[koolkat77]

Weird thing is it's crashing on MSE itself

There's nothing specific in the dumps

Will wait for the results on memtest.

 

[SevenChurches]

Well, ran Memtest on each stick in every slot for at least 7 passes and still got no errors.

 

[SevenChurches]

Got another blue screen right after I sent that last message.

SYSTEM_SERVICE_EXCEPTION

 

[koolkat77]

Sometimes memtest doesn't find errors.
How many sticks do you have?

Test them manually, without memtest.

Insert one stick and see how the computer performs.
Do the same with others.

Edit: It's crashing on MSE. Have you overclocked any of your hardware?