Random BSOD's on few week old build.

Hi Watson, Just had a quick look at your system details and noticed that your processor is an i5 4570 at 3.2Ghz, however, your motherboard is reporting it as an i5 4670 at 3.4Ghz, I can't tell you much about the BSOD's as I'm not a BSOD guy but it's definitely worth a note that your Processor appears to think it's something else.

MrNeeds said:

Hi Watson, Just had a quick look at your system details and noticed that your processor is an i5 4570 at 3.2Ghz, however, your motherboard is reporting it as an i5 4670 at 3.4Ghz, I can't tell you much about the BSOD's as I'm not a BSOD guy but it's definitely worth a note that your Processor appears to think it's something else.

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Uninstall GIGABYTE OC_GURU. But before uninstalling it, run it and set everything to system defaults.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

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

Next, the BSODs are generally blaming the memory. It may be the physical RAM or may be any driver passing any bad information to the memory.

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

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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.
_____________________________________

Code:

BugCheck 50, {ffffea800fdda4f0, 0, fffff80002efafe5, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+215 )

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

Code:

BugCheck 1A, {41790, fffffa8004cada50, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

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

Good news.

Let us know for any further BSOD.

Expected. :)

Follow the rest of post #3. From memtest86+.