Can 0X124,x3B Be Caused by Overclocking?

[Johnathan Lyman]

Hey guys and gals.

I support a lot of people on these forums but now it's my turn.

I recently (as in 10 minutes ago) was plagued with the infamous and hard to track down 0x124 BSOD while folding (Folding@Home) and watching Dexter via Netflix. I frequently leave my machine on all night to fold and this is the first time I've seen this present itself as 0x124. Prior, the only issues I've had are the occasional SYSTEM_SERVICE_EXCPTION (3b) and something else I can't remember. I read through the 0x124 reference thread posted here and So far every check is passing. I'll test the ram tonight with MemTest86 and run chkdsk /r in the morning. In the meantime, enjoy the package I've included along with all pertinent information. (specs down below)

I do know that in the past, I've only either BSOD'd when folding over night OR (only happened once) was watching Hancock via MPC on my big screen.

I am overclocked. My sig says 3.35, but I'm at 3.43ghz now and this is the first issue that's come up since I bumped up a couple days ago. I'll drop the clock back to stock as well. RAM is not overclocked (9-9-9-24, 1.5V, per manufacturer specs).

Age of hardware: 1 month
Age of OS: 1 month

 

[zigzag3143]

Hey guys and gals.

I support a lot of people on these forums but now it's my turn.

I recently (as in 10 minutes ago) was plagued with the infamous and hard to track down 0x124 BSOD while folding (Folding@Home) and watching Dexter via Netflix. I frequently leave my machine on all night to fold and this is the first time I've seen this present itself as 0x124. Prior, the only issues I've had are the occasional SYSTEM_SERVICE_EXCPTION (3b) and something else I can't remember. I read through the 0x124 reference thread posted here and So far every check is passing. I'll test the ram tonight with MemTest86 and run chkdsk /r in the morning. In the meantime, enjoy the package I've included along with all pertinent information. (specs down below)

I do know that in the past, I've only either BSOD'd when folding over night OR (only happened once) was watching Hancock via MPC on my big screen.

I am overclocked. My sig says 3.35, but I'm at 3.43ghz now and this is the first issue that's come up since I bumped up a couple days ago. I'll drop the clock back to stock as well. RAM is not overclocked (9-9-9-24, 1.5V, per manufacturer specs).

Age of hardware: 1 month
Age of OS: 1 month

124 can be caused by overclocking, under volting, hardware mismatch failing power supply, bad ram, etc

Use these

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. 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 http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html


Two of the three are blamed on your video driver with the third being blamed on your Norton

I would remove norton and replace with Microsoft security essentials
ftp://ftp.symantec.com/public/english_us_canada/removal_tools/Norton_Removal_Tool.exe
http://www.microsoft.com/security_essentials/

remove and re-instal your video driver using these

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using http://www.guru3d.com/category/driversweeper/

When it is removed then download and install the fresh copy.


Thanks


Ken

be care distributed computing clients like folding can melt laptops. I have over 1 million seti unit and have fried 2 laptops.

 

[Johnathan Lyman]

Thanks Zigzag.

Memtest: ok
Chkdsk: ok
Overclock: removed
Norton 360: Removed - Replaced with MSE
ATI Drivers: Cleaned out - reinstalled 10.12

We'll see what happens. It might happen tonight, it might happen 2 weeks from now...

Oh and it's a desktop, not a laptop.

 

[Johnathan Lyman]

Update: I got an 0x3B BSOD while upgrading to Windows 7 SP1.

Dump attached.

 

[zigzag3143]

Still a memory exception caused by your video driver. Are you overclocking/undervolting? What AV are you using? Are you running a RAID?

Can you look in event viewer for critical errors relatating to this problem

There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

Let us know if you need help with any of this.

Ken

 

[Johnathan Lyman]

No raid. OC from 2.8 to 3.4, no volt changes. Microsoft Security Essentials.

Only criticals that are mentioned is the machine restarted from a bugcheck.

I attached all of them as a text file. You'll see a couple from the 10th or so. I ran CCleaner and deleted those before I realized it.

 

[zigzag3143]

No raid. OC from 2.8 to 3.4, no volt changes. Microsoft Security Essentials.

Only criticals that are mentioned is the machine restarted from a bugcheck.

I attached all of them as a text file. You'll see a couple from the 10th or so. I ran CCleaner and deleted those before I realized it.

Might want to go back to defaults to test. OC is a substantial cause

 

[Johnathan Lyman]

No raid. OC from 2.8 to 3.4, no volt changes. Microsoft Security Essentials.

Only criticals that are mentioned is the machine restarted from a bugcheck.

I attached all of them as a text file. You'll see a couple from the 10th or so. I ran CCleaner and deleted those before I realized it.

Might want to go back to defaults to test. OC is a substantial cause

K. I'll give that a whirl and let you know.

 

[logpace]

Hey what worked for my 0x124 error was I just "upgraded" my windows installation. Put in your windows 7 disk and hit upgrade, and it leaves all your files etc untouched except it copies all new windows files and resets your drivers. Worked for me.

 

[Johnathan Lyman]

Hey what worked for my 0x124 error was I just "upgraded" my windows installation. Put in your windows 7 disk and hit upgrade, and it leaves all your files etc untouched except it copies all new windows files and resets your drivers. Worked for me.

Even though I'm already at the highest upgrade level for Windows 7?

I haven't had an 0x124s since the first incident, just 0x3B.

 

[logpace]

Ya, for example I have windows 64-bit pro and I "upgraded" to it. thats why I have the quotes around upgrade, because it isnt really an upgrade, it just rewrites over all the windows system files

 

[Johnathan Lyman]

Just as a heads up, I hadn't had any problems until a few minutes ago. I left my PC running World of Warcraft as I went to make lunch and came back to a black screen that i had to hard restart. Restarted and was told I crashed with 0x3b.

I attached the most recent dump.