Two BSOD 4 days apart (zip file attached)

[smilingbounder]

So, I have no clue how to decipher these things. Please help me out people

 

[nommy the first]

Hello Smilingbounder,

The following software is contributing to your problems and a known BSoD cause, please uninstall it;

Start Menu\Programs\[COLOR=Red][B]DAEMON Tools Pro[/B][/COLOR]    Public:Start Menu\Programs\DAEMON Tools Pro    Public

• Download and install Revo Uninstaller.
• Right click the program that needs to be removed, and click on Uninstall.
• Select "Advanced" as uninstall mode.
• Let Revo remove the program, and afterwards please follow the displayed steps to remove all entries of the program as well.
• When all programs have been uninstalled, please restart your machine.

----------

Please reduce the items that run at start up. You basically only need your anti virus to run at start up, all other programs are not necessary and can be removed from the start up list.
Check this tutorial to see how to add or remove start up items.

----------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 124[/B][/COLOR], {0, fffffa8007aae028, be000000, 100110a}

[COLOR=Red][B]*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys[/B][/COLOR]
Probably caused by : GenuineIntel

Followup: MachineOwner
---------

Usual cause: Fatal hardware error.
More info :ar: Bug check 0x124_0.
Driver reference table: intelppm.sys.

----------

Please go to the Intel download center and use the driver update utility to update the driver to the latest version.

----------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 116[/B][/COLOR], {fffffa800a6170f0, fffff8800778a6b4, ffffffffc00000b5, a}

[COLOR=Red][B]***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B][/COLOR]

Followup: MachineOwner
---------

Although that the dump file might be corrupted, we do know that this is a stop 0x116, which is usually caused by a failing GPU driver.
More info :ar: Bug check 0x116.

----------

I see that you are using a Nvidia GeForce GTX 560 Ti, are you using the latest driver? It is recommended to use the 314.22 WHQL, as it's the most stable one.
Please follow this;

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Good luck and keep us posted,
Nommy

 

[smilingbounder]

So, I just had another BSOD. Attaching the SF zip.

Might be relevant info: I was using the 314.22 WHQL drivers for a while, no problems. Installed the newest beta driver yesterday, and tonight I got this BSOD. I was also testing different settings in BIOS. Disabling speedstep, etc.

 

[smilingbounder]

Can anyone please take a look. I haven't had one since my previous post, but I still would like to know, if possible, what caused it.

 

[nommy the first]

Hello smilingbounder,

Sorry for my late reply, but I was away from my computer for the past one and a half day.

----------

Using BETA drivers is never a good idea BSoD wise. Have you tried installing the 327.23 WHQL driver?

----------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 124[/B][/COLOR], {[B][COLOR=Red]0[/COLOR][/B], fffffa8005728028, bf800000, 124}

[COLOR=Red][B]Probably caused by : GenuineIntel[/B][/COLOR]

Followup: MachineOwner
---------

Usual cause: Fatal hardware error.
More info :ar: Bug check 0x124_0.

----------

It does seem that you were using Steam when you encountered both this and the previous BSoD. Please try not using Steam for a few days. If you don't encounter a BSoD, try reinstalling it. If you do encounter a BSoD, please try everything below here.

----------

Your dump files do not show any finite cause of the problem, so please preform the following hardware tests;
Stress test the graphics card using Furmark GPU Stress Test.

   Information

During the test please check the screen for artifacts.
The purpose of this test is to make your machine crash and create dump files so that we can pinpoint the cause of your problem.

   Tip

Please run Furmark once when your machine has just started, and once again when your machine has been active for several hours.

----------

Please download Speccy.

1. Download and install Speccy.
2. Open Speccy. Click on the Summary tab.
3. Click on File and then on Save Snapshot.
4. Set the save location as your desktop and upload the file by following this tutorial.
   :ar: Please upload a snapshot of your machine in the following situations;
   • Idle, after startup.
   • After being used for a few hours.
   • After straining the GPU by, for example, playing some High Res games.

----------

Please run Memtest86+ to test your RAM for issues.

   Tip

Let Memtest run for at least 10 passes and preferably overnight as it may take very long to complete.
:ar: Especially read part three of the tutorial, which explains you to test each RAM stick in all DIMM slots to filter out failing slots.

Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

----------

Please follow this to test your hard drive for errors;

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check - Use the /r switch, Follow OPTION TWO - command prompt at startup.
2. Then Post the results following | THIS METHOD
3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fxkey.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

Good luck and keep us posted,
Nommy