BSOD's when using PC in various applications

dmaidmen · 18 Jan 2013

Hi,

I wonder if anyone can help. I have a Shuttle SG33G6 DELUXE barebones PC that has been suffering BSOD's for some while. There doesn't seem to be a particular pattern to them, sometimes there will be several a day and sometimes a few days without one.

I have tried a complete reinstall of Windows 7 but the BSOD's returned straight away. I have updated the drivers from Shuttles website but still had issues. I then tried all Windows recommendations and that didn't help. I also tried Driver Detective and followed its recommendations but to no avail. I'm currently running the latest version of all the drivers that I can find from all sources including the chipset drivers that Intel recommend with their auto updater.

I know the PC's old but due to its size it makes a nice living room PC for everyday use. I have a i5 downstairs for more heavy processing.

I have attached a ton of mini dumps and the rest of the information gathered by the SF tool.

Please let me know if you need any more information and thanks in advance for any help you can provide.

Cheers,

Duncan

Arc · 18 Jan 2013

Hello Duncun.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept the restart.

If possible, plan to update the BIOS.

Code:

BIOS Version/Date    Phoenix Technologies, LTD 6.00 PG, 19/08/2008

Let us know the results.

dmaidmen · 18 Jan 2013

Hi Arc,

Thanks for the quick response. I'll run DV and get back to you.

Cheers,

Duncan

dmaidmen · 26 Jan 2013

Hello,

Does DV stop minidumps being written? We have had several blue screens since turning DV on however no new mini dumps have been created. In the event logs I can't see any WER-SystemErrorReporting events anymore either.

Two of the the BSOD's were caused by an application that was running in the background. I will open a support ticket with them.

Another one was 'Bad Pool Header'. Stop 019.

When I run the SF tool it doesn't appear to dump out the system log entries for 2013. It stops at 2012-10-31.

Cheers,

Duncan

Arc · 26 Jan 2013

Hello Duncun, do you use any program to clean up the disc? If so, stop it for the time being; as they clean the minidump folder too.

No, DV does not prevent creating minidump, still have a check.
Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

dmaidmen · 26 Jan 2013

No I don't use anything to clean up the disk. I had already checked %SystemRoot%\Minidump and it has the older dumps that I uploaded before but nothing since the 2013-01-18. I manually removed the older dump files and archived them.

I think the minidumps are configured correctly. I haven't changed anything since I uploaded the results of the SF tool when I started this thread. See attached for screenshot of my StartupAndRecovery screen.

dmaidmen · 26 Jan 2013

Another BSOD. Attached is a photo of my screen. As you can see it says the crashdump is being written but nothing is present in the %SystemRoot%\Minidump for today.

I checked the folder permissions and I have full control as does Administrators and system. The last crashdump successfully written is owned by Administrators.

My %SystemRoot% installation is on a Crucial 64GB SSD. It currently has 20GB free.

Cheers,

Duncan

Arc · 26 Jan 2013

I have asked for some more help in this thread.

carwiz · 28 Jan 2013

You may have the pagefile set to small or not at all. The pagefile is necessary to create dumps. Could also explain a Bad Pool Header BSOD. This is from the Paged Pool maintained in the pagefile.