Computer crashed - BC Code 124

[Arc]

Reoprt the test results, not problems only.

Because without the test results we can do nothing more.

 

[Rawkt]

Reoprt the test results, not problems only.

Because without the test results we can do nothing more.

Yup, I'll do that.

I'm out right now, I'll be home in a few hours and I'll run Prime 95 followed by memtest.

Quick question about memtest, how many passes would be recommended?

 

[Arc]

It is said there. At least eight.

 

[Rawkt]

It is said there. At least eight.

Sorry to bother with all these questions, if an error did pop up while I was asleep/away from the computer during the test, would it be harmful at all to have the test continue with the error?

 

[Rawkt]

Reoprt the test results, not problems only.

Because without the test results we can do nothing more.

I did the Small FFTs test and monitored the temperatures, no errors or warnings on the 4 workers. Temperatures for the cores did not exceed around 72 degrees with the temperature next to 'Package' peaking at 76 degrees and remaining stable between 72-76 degrees.

I'll run memtest next, probably tomorrow so I can monitor it and stop it just in case an error pops up.

 

[Thedoctor44]

How long did you run Prime95 for? I recommend around 2 hours.

===============================================================================
Common Platform Error Record @ fffffa800768a8f8
-------------------------------------------------------------------------------
Record Id     : 01cf5560d6c96d22
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : [COLOR="SeaGreen"]Machine Check Exception[/COLOR]
Timestamp     : 4/11/2014 8:34:25
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800768a978
Section       @ fffffa800768aa50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : [COLOR="red"]Micro-Architectural Error[/COLOR]
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800768a9c0
Section       @ fffffa800768ab10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : c3 06 03 00 00 08 10 00 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800768ab10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800768aa08
Section       @ fffffa800768ab90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR="Red"]Internal timer[/COLOR] (Proc 0 Bank 3)
  Status      : 0xf200000000800400

This is a strong indication of a failing CPU so please run it for around 2 hours.

 

[Rawkt]

Does that always mean that it is a CPU problem? It would just be a pain if it was a CPU problem since I have very little experience when it comes to this.

Oh... I only ran it for 1 hour thinking that it would be enough, my bad.


EDIT: Just to add, these errors only occurred when I was browsing/listening to music, no problems come up when I'm gaming... I don't think that makes a difference, but I just thought I'd let you know.

 

[Thedoctor44]

A lot of the time it means a CPU fault has occurred but not always.
Just post back the results.

One thing at a time.

 

[Rawkt]

A lot of the time it means a CPU fault has occurred but not always.
Just post back the results.

One thing at a time.

Thank you for taking your time to reply.
I'll get back to you tomorrow once I run memtest for the recommended length of time, I don't really want to run it overnight just in case an error comes up.

It's a relatively new computer so I'm just hoping that it isn't serious...

 

[Thedoctor44]

I would recommend running it overnight, memtest86 will never stop running unless your computer shuts down or you stop it.
An error will show up red at the bottom, you can't miss it.

 

[Rawkt]

I would recommend running it overnight, memtest86 will never stop running unless your computer shuts down or you stop it.
An error will show up red at the bottom, you can't miss it.

I thought you had to stop it once an error occurred... So it's okay to have it continue running even though an error has occurred?

 

[Thedoctor44]

No not at all, I've never known that anyway.
It's fine to run it overnight.

 

[Rawkt]

No not at all, I've never known that anyway.
It's fine to run it overnight.

Sweet, I'll run it tonight just before I go to bed!

 

[Rawkt]

Also, did the files that I uploaded the second time round have anything about the CPU like the first zip did? I just wanted to know if the two errors were caused by the same thing...

Thanks for the replies.

 

[Thedoctor44]

There were no new dump files unfortunately.

 

[Rawkt]

There were no new dump files unfortunately.

Ohh so it was found in the dump file. Alright, thanks!

 

[Rawkt]

I would recommend running it overnight, memtest86 will never stop running unless your computer shuts down or you stop it.
An error will show up red at the bottom, you can't miss it.

Ran it overnight and no errors came up, everything seemed fine! Ended up with 6 passes and nearly up to the 7th.

 

[Thedoctor44]

Did you run Prime95 again for around 2 hours?
If not please run it, if so and no errors came up then I recommend running Driver Verifier by following these instructions

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Reason being, I have had encounters where 0x124 bugchecks can actually be caused by software.

Please create a system restore point before enabling Driver Verifier as it can make your system unbootable, even in safe mode

http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

 

[Rawkt]

Did you run Prime95 again for around 2 hours?
If not please run it, if so and no errors came up then I recommend running Driver Verifier by following these instructions

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Reason being, I have had encounters where 0x124 bugchecks can actually be caused by software.

Please create a system restore point before enabling Driver Verifier as it can make your system unbootable, even in safe mode

http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Alright!

What do you mean by unbootable...

 

[Thedoctor44]

As in windows will not start without getting a blue screen.
If that happens you can revert to the restore point you created earlier.