Getting Random BSOD with different stop codes

JulietSix · 10 Jul 2013

For the past couple weeks my machine has been getting Random BSOD with different stop codes. I hadn't done much to rectify the problem other than google the stop codes to see what may the problem. I've learned it could be anything from failing hardware to driver conflicts. Pretty vague. So I just decided to format and reinstall Win 7 and see if that helped. Of course it didn't, so I've come here for the expertise of you gentleman...

I went through the BSOD posting instructions and I hope I've done everything properly. It's a lot of information.

See attached.

koolkat77 · 11 Jul 2013

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):
DuplexSecure - FAQ

Log Me In/Remote anywhere software seems to be contributing to the crashes.

Uninstall it 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

Check for a BIOS update:
BIOS Version/Date American Megatrends Inc. P2.60, 10/1/2010

Eset antivirus is contributing cause of your BSOD's. I would remove it with the uninstall tool and replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make a full scan separately:
Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
Microsoft Security Essentials - Microsoft Windows
Malwarebytes Free

Run a system file check and disk check on your Hard drives:
SFC /SCANNOW Command - System File Checker
Disk Check

Test RAM with memtest86+:
RAM - Test with Memtest86+

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

Code:

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Jul 11 08:30:34.911 2013 (UTC + 6:00)
System Uptime: 0 days 6:12:00.942
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Jul 11 02:17:21.510 2013 (UTC + 6:00)
System Uptime: 0 days 0:22:31.682
BugCheck 124, {4, fffffa8005ff68d8, 0, 0}
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jul 10 09:32:54.036 2013 (UTC + 6:00)
System Uptime: 0 days 0:06:53.083
BugCheck 124, {4, fffffa8005fed038, 0, 0}
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  lsm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jul 10 09:24:38.287 2013 (UTC + 6:00)
System Uptime: 0 days 8:51:19.318
BugCheck 101, {18, 0, fffff880032a4180, 5}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  LogMeIn.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

JulietSix · 11 Jul 2013

Since I was just coming from another reinstall anyway I opted to go the step 7 route on the "Stop 0x124 trouble shooting strategy" (vanilla install w/ some slight modification).

I downloaded Prime95 and ran a small ffl stress test for a little over an hour earlier without a hiccup. I used Realtemp to monitor the temps to make sure they didn't go into dangerous levels. They leveled off at about 70-71 degrees. Last night Prime95 would crash the machine in a matter of minutes. Tonight I will run memtest86 on the machine overnight and see what comes up.

Since the reinstall I've yet to have any problems, but I haven't installed any updates or hardware drivers yet. I'll run like this for another day or so and slowly begin to install drivers and software. Thanks for the advice koolkat.

koolkat77 · 26 Aug 2013

Were your bsod problems solved?

JulietSix · 27 Aug 2013

They were Thank-you.

After going through what I mentioned above, I decided to start testing the PC with new hardware pieces. I selected the graphics card first (because why not?), stress tested the computer and could not reenact the problem when I put an older card I had laying around. Turns out the GPU was bad. I Sent it to EVGA for replacement and now I'm good to go.

Thanks!!

koolkat77 · 27 Aug 2013

Thanks for letting us know! It will help users with the same issue :)
Please mark your thread as solved.

Tip

If your problem is solved please use the Mark this thread as solved link at the top of your thread or down on the left corner