Random BSODs

[mrviper9307]

I have been getting random BSODs for the past few months. There is nothing consistent about what I've been doing when they happen. I've run MemTest before, but would be willing to do so again. I've attached the files compiled by the DM Log Collector. Any help would be greatly appreciated.

 

[koolkat77]

Welcome to the forum mrviper9307,

Your last dump is dated 18/9/2014.

Make sure your dump logging is enabled.

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. Check Write an even to the system log, and Automatically restart.
5. In the Write debugging information list, click Small memory dump (256k).

Location of Dumps:
C:\Windows\minidump

Please remove the software below, they could be a reason for BSOD's.

Start Menu\Programs\Advanced SystemCare 7	Public:Start Menu\Programs\Advanced SystemCare 7	Public
Start Menu\Programs\Driver Booster	Public:Start Menu\Programs\Driver Booster	Public

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

That's a whole lot of start-up mess.

Perform a Clean boot:

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

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

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

Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

• Speccy - System Information - Free Download
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Post back with results.

 

[mrviper9307]

Thanks for the reply. My dump logging is enabled, I just haven't been using the computer for the past couple of weeks. That's why the logs stopped on 9/18. I have uninstalled all IOBit software and ran SFC without error. I'm currently on a clean boot, but since I don't have a way of reliably forcing the BSOD, I'll just have to wait and see if it happens. I have also attached a screenshot of the Summary screen of Speccy.

 

[mrviper9307]

I just had another BSOD while running from a Clean Boot. Unfortunately, as Minidump wasn't successfully saved, even though the dump logging was on. I've been wondering if it's possibly a power issue because sometimes it takes a little while for my USB keyboard and mouse to start working when I boot, sometimes I have to unplug and replug my USB microphone several times to get it detected, and sometimes my second monitor won't receive signal unless and unplug and replug the HDMI cable. Any thoughts?

 

[koolkat77]

Please post a snap of your next BSOD.

 

[mrviper9307]

I had another BSOD today again with no log, but managed to get a pic of the screen. It's attached.

 

[mrviper9307]

I have had another BSOD. Upon running my log dumps through "WhoCrashed", it is citing ntoskrnl.exe (nt+0x75BC0) as the problem. Any ideas as to what this means? I've also just updated my BIOS, in case that might have been the problem. Attached is the picture of today's BSOD. Any help would be awesome.

 

[koolkat77]

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

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.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.