Solved BSOD at seemingly random intervals error 0x0000003B

[Maverick2002]

Hi All,

Hopefully you guys can help as i've run out of ideas on a small problem that just wont go away, computer related of course

My computer has always had an issue where occasionally it will BSOD without warning, always quoting a hardware error. Up till now i've lived with it but its finally got to the point where i want it sorted once and for all.

As its always done it, i suspected it may be down to faulty hardware but ruled that out, as it passes stress tests, memory checks, cpu tests with no problems.

I've tried the following so far:

• A nice shiney new graphics card for my birthday which i had hoped that by replacing the old one may magically fix the random BSOD...no avail. Exactly the same thing happens.
• Next up was running the ram stick individually - still the same issue.
• Removed my xonar card - seemed to work as it appeared more stable, but then the same thing happened

Just to give some more info, something that may be totally unrelated but occassionaly, when booting, my system will lock up on the windows logo screen. It will do the fancy spinning thing, complete the logo, then nothing. When the sounds card was in, i used to be able to tell if it had booted correctly as you could hear the sound card itself, tick twice - if it only ticked once i'd know it was stuck.


So what else can i try? Help me windows 7 forums, you're my only hope

 

[Arc]

Hi Maverick2002.

A stop 0x124 is a hardware failure, apparently.

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

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Is the computer running hot? Let us see. Upload a snapshot Using Speccy.

• Download and install Speccy.
• File> Save snapshot.
• Save it on desktop.
• Zip it and upload it following following http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Let us know the results. And, are you having any trouble with any audio device there?
__________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008d7a028, be200000, 5110a}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008d7a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`009fba58 fffff800`03602a3b : 00000000`00000124 00000000`00000000 fffffa80`08d7a028 00000000`be200000 : 0xfffff800`0307fb80
fffff880`009fba60 00000000`00000124 : 00000000`00000000 fffffa80`08d7a028 00000000`be200000 00000000`0005110a : 0xfffff800`03602a3b
fffff880`009fba68 00000000`00000000 : fffffa80`08d7a028 00000000`be200000 00000000`0005110a fffffa80`08bc9930 : 0x124


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

 

[Maverick2002]

Hi, thanks for the reply - I'm on with the tests now.

Quick question, regarding the furmark tests- i've followed the guide, run it but cant find where it saves the logs?

I ran it for 5 minutes and it levelled out at a temp of 84.

I'll run the other tests overnight tonight

Power supply is an antec trupower 650 and i think it should be enough.....i hope anyway

 

[Arc]

If five minutes in furmark did not cause any trouble there, we may consider that the GPU is not failing.

Temps are also good.

Waiting for the results of the other tests

 

[Maverick2002]

15 passes on memtest and no errors, just prime left to go

 

[Maverick2002]

Still not had chance to run prime but i;ve another BSOD log in the meantime

 

[Maverick2002]

Prime ran for 2 hours with no errors. Stopped the test and blue screen straight away -log attached.

Also, interestingly, speedfan registered my cpu temp as -60 and didnt change!? Guessing it bugged out.

Not sure why, but after one of these BSOD windows gets stuck after the windows logo shows, the logo just stays on screen and refuses to enter windows - unrealted maybe?

 

[Arc]

Waiting for the Speccy snapshot.

 

[Maverick2002]

Sorry, thought i'd done that in the 3rd post - was that not what you're after?

Another attached just incase

 

[Arc]

Sorry, thought i'd done that in the 3rd post - was that not what you're after?

Another attached just incase

Sorry, I missed that

At this situation, you should go for deeper and detailer troubleshooting, as the real reason behind a stop 0x124 is sometimes really hard.

Follow http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696 for the ideas about what to do.

 

[Maverick2002]

Sorry to bring this up again after months of trouble shooting - Still having the same issue but i'm 90% sure its to do with the ram. Running on one stick it seems to be more stable but still crashes (doesnt get stuck on the windows logo however) and it doesnt matter which stick i use.

Could it be something to do with the ram timings or am i barking up the wrong tree? Since the intial problems it seems to be happening more, even when i just leave the PC in idle on the desktop...

Am i best to just back everything up and start again or is that too drastic?

 

[Arc]

If you suspect RAM timings, set those (and all other hardware) to default settings.

 

[Maverick2002]

Finally resolved. Not exactly sure wehat it was but i suspect it was the voltages to the RAM - once i set those to default in the ASUS manager all seems well!

Thanks for the support!

 

[Arc]

Good news!