Solved BSOD randomly trying to narrow down

[Rick76]

I"ve been having BSOD's randomly for years now. I went through a period recently of not having any for 5 months or so until they started reoccurring. I've always had an overclock although I am not an expert at it. For the purposes of trying to finally figure out what is causing the BSOD's I've gone to default BIOS settings. I can add that I have had the BSOD's even when not overclocked.

Noticeable behavior and hunches:
1. Power Options. I have a hunch something about the pc power options is causing the BSOD's because at times the monitor will stay asleep despite the computer being awake. The hunch also comes from crashes being caused soon after being awakened from sleep.

2. Memory. On my motherboard there is a red light comes on (Memok!) when it does not recognize memory. It is usually on when restarting the computer or when the BSOD happens. The light will be on and the monitor will turn itself off. When clicking the "Memok" button it's supposed to detect and apply safe settings for the memory. I've done this before and currently using the settings it has applied to my BIOS.

Also when overclocking running a BLEND test in Prime95 would almost instantaneously crash my PC although when running MEMTEST via USB BOOT it detected no errors.

I have nothing else to add except that I hope I can get some help with these BSOD's once and for all. Thank you.

 

[Rick76]

Just ran a test for 1 hour on prime95 with memory at factory suggested settings where before I would BSOD instantly or a very short time afterwards. I notice if I leave the memory alone the MOBO will set the DRAM to 1333mhz @1.55v when the Memory is rated for 1600mhz @1.5v (which I set to and have gotten the best performance on Prime95 blend test).


Just current update with memory testing. This RAM has been a mystery to me because I've been letting the mobo put all kinds of different voltages to it automatically. By default the mobo has the ram at 1333mhz and when changing it to 1600mhz BIOS asks if you would like to let it automatically change the voltage and usually I would say yes. When allowing the mobo to automatically change the DRAM voltage it puts it up to 1.65v. When put on factory settings it sets the DRAM to 1.55v. Both of these are out of the specified 1.5v but now @1.5v and everything else at default I've gotten pretty far in prime95 blend.

 

[koolkat77]

If you are overclocking any hardware please stop. You can enable overclock after your system after we have completed diagnosis.

Please remove Magic ISO software. It seems to be contributing to your BSOD's.

Remove AMD Overdrive; also in EasyTune6 for Gigabyte motherboard They are known BSOD issues in Win 7.

Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)

Uninstall them using the free version of Revo Uninstaller. While uninstalling a software, opt for advance uninstall. This allows you to remove and delete registry left over of a stubborn program. Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Avast! antivirus is often a cause of BSOD's. I would remove it with the Avast! uninstall tool and replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make a full scan separately:
avast! Uninstall Utility | Download aswClear for avast! Removal
Microsoft Security Essentials - Microsoft Windows
Malwarebytes Free

Run a system file check and disk check on your Hard drives:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
http://www.sevenforums.com/tutorials/433-disk-check.html

Test RAM with memtest86+:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
:info: Pay close attention to part 3 of the tutorial "If you have errors"

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

Bugcheck

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Jul 11 06:22:37.212 2013 (UTC + 6:00)
System Uptime: 0 days 0:24:52.742
BugCheck D1, {0, 2, 0, fffff880074b8a13}
Probably caused by : HIDPARSE.SYS ( HIDPARSE!HidP_GetUsages+2f )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Jul 11 05:56:16.002 2013 (UTC + 6:00)
System Uptime: 0 days 0:25:09.048
BugCheck 124, {0, fffffa8007b78028, b202a000, 175}
Probably caused by : AuthenticAMD
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  prime95.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Jul 11 05:06:25.817 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:43.941
BugCheck 1000007E, {ffffffffc0000005, fffff800030c9b05, fffff88003332628, fffff88003331e80}
Probably caused by : rdyboost.sys ( rdyboost+4fd3 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Jul 11 03:16:45.082 2013 (UTC + 6:00)
System Uptime: 0 days 0:15:57.503
BugCheck 50, {fffff8a012518dec, 0, fffff80003395f7e, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Wow-64.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jul 10 12:43:53.535 2013 (UTC + 6:00)
System Uptime: 0 days 8:50:40.956
BugCheck 1A, {41289, c3d3001, 87bd, c2d3045}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a99 )
BUGCHECK_STR:  0x1a_41289
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[Rick76]

solution

Just wanted to close this thread out with a solution guys.

It was the ram.
F3-12800CL9D-4GBRL (ram)
m4a89gtd pro/usb3
Phenom x4 955 Black Edition


After nearly 3 years of random BSOD's the answer was this... changing the timing of the ram from 9-9-9-24 2T to 8-8-8-24 1T fixed it.

 

[Rick76]

Just wanted to post back as a thanks for those who tried to help. Thank you it was indeed hardware related.