BSOD without reasons, error 0x00000124 and multiple freezes

AmmoniumFR · 15 Jun 2014

Good evening,

I post a thread on this forum because I need help. I have built a new computer last week, and I have many problems since.

I had a few BSOD and a lots of freezes. Also after few hours of use, my computer freezes and I need to shut it down manually/by force with the button.

I don't understand why this is happening and I don't know how to solve these problems, so I please request your help.

I attached the zip file generated by SF tools.

My Spec :

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
Windows 7 pro 64b.
CPU
Intel i7 4790 (haswell refresh)
Motherboard
MSI Z97-G45 Gaming
Memory
8 Go DDR3 G.Skill
Graphics Card
MSI GTX 780 3Go OC
Hard Drives
SSD SanDisk 256 Go
HDD Samsung 1To (x2)

Regards,

Ammonium

Boozad · 15 Jun 2014

Normally a 0x124 is a hardware related STOP, and it may well be in this case but it will need a far, far better analyst than myself to debug it. One thing I did pick up on in your logs though is that your Intel Processor driver flagged up as a problem.

Code:

fffff880`0337cb58 fffff800`033fea3b : 00000000`00000124 00000000`00000000 fffffa80`07586028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`0337cb60 fffff800`02f93463 : 00000000`00000001 fffffa80`0758fa00 00000000`00000000 fffffa80`0758fa50 : hal!HalBugCheckSystem+0x1e3
fffff880`0337cba0 fffff800`033fe700 : 00000000`00000728 fffffa80`0758fa00 fffff880`0337cf30 fffff880`0337cf00 : nt!WheaReportHwError+0x263
fffff880`0337cc00 fffff800`033fe052 : fffffa80`0758fa00 fffff880`0337cf30 fffffa80`0758fa00 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0337cd50 fffff800`033fdf0d : 00000000`00000008 00000000`00000001 fffff880`0337cfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0337cd90 fffff800`033f1e88 : 00000000`00000001 fffff880`03374180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0337cdc0 fffff800`02e7b4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0337cdf0 fffff800`02e7b313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0337cf30 fffff880`0ffe8c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 (TrapFrame @ fffff880`0337cf30)
fffff880`0339cb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19

Looking at the timestamp it's very old and could do with updating.

Code:

7: kd> lmvm intelppm
start             end                 module name
fffff880`0ffe6000 fffff880`0fffc000   intelppm   (pdb symbols)          c:\symbols\intelppm.pdb\08BB31C0378D48EC8CB513240E096A171\intelppm.pdb
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: c:\symbols\intelppm.sys\4A5BC0FD16000\intelppm.sys
    Image path: \SystemRoot\system32\DRIVERS\intelppm.sys
    Image name: intelppm.sys
    Timestamp:        Tue Jul 14 00:19:25 2009 (4A5BC0FD)
    CheckSum:         0000F4EC
    ImageSize:        00016000

Go here to find an updated driver.

I'll ask one of our analysts to take a look at your logs to see if there are any hardware faults that stand out.

Thedoctor44 · 15 Jun 2014

Code:

7: kd> !errrec fffffa8007586028
===============================================================================
Common Platform Error Record @ fffffa8007586028
-------------------------------------------------------------------------------
Record Id     : 01cf8899771e25c5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/15/2014 17:48:45 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000007

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

Local APIC Id : 0x0000000000000007
CPU Id        : c3 06 03 00 00 08 10 07 - ff 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  @ fffffa8007586240

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

Error         : Internal unclassified (Proc 7 Bank 4)
  Status      : 0xba00000052000402

I cannot comment on what the cause could be as this particular error is undocumented.

I suggest stress testing all your components.

Stress test your CPU with Prime95

I recommend running Prime95 for around 2 hours

Warning

As with most stress tests your component's temperature will rapidly increase.
It is advised that you download a temperature monitoring program like HWmonitor
Keep an eye on your temperatures and stop the tests if it starts to overheat

Stress test your graphics card with Furmark

I recommend running it for around 30 minutes

Warning

Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures

Memtest86 will test your RAM

Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Try taking out the CMOS battery on the motherboard then placing it back in to ensure no improper settings have been made.

Post back the results.

essenbe · 15 Jun 2014

Did you install drivers for your Motherboard. If so did you install them from the driver disk sent with your Motherboard or did you download them from the manufacturer's web site? The drivers on the manufacturer's web site are much more current that the driver disk. However, your Motherboard and CPU did not exist in 2009, so would you please let us know if you did a clean install or simply transfer the OS drive from another computer to this one? That is what it appears to me. If you did not do a clean install, I would strongly suggest that you do one now. Back up your personal files to an external source and do a clean install. The operating system will never run right with the wrong drivers or with 2 sets of drivers installed. Either one would cause you considerable problems.

AmmoniumFR · 15 Jun 2014

Thank's boozad for your help.
The intelppm driver has no update on the intel's website.
I used the Intel Driver Update Utility and search download.

TheDoctor, I will execute all the stress test and post the result. See you soon and I hope that we shall find a solution.

essenbe, I have did a clean install with an official windows seven pro dvd.
I used the msi driver on this page MSI Global - Computer, Laptop, Notebook, Desktop, Motherboard, Graphics and more

I don't have transfert any system files, just personnal files.

essenbe · 15 Jun 2014

AmmoniumFR, All the drivers I found on the MSI site you linled to were dated 2014. Haswell refresh, Haswell, Ivy Bridge or Sandy bridge didn't exist in 2009. I don't know where that driver came from, but I would get rid of it. It's most likely a Core2Duo driver.

AmmoniumFR · 15 Jun 2014

Me to, I don't know where that driver came from.

And what is his utility ? I don't know if I can remove it or disable it.

essenbe · 15 Jun 2014

It is the Intel processor driver. I believe it should be in C;/Windows/ system32/drivers but you should be able to disable it in services.msc

AmmoniumFR · 15 Jun 2014

This is not dangerous to disable it ? I don't want to break my computer and must be install windows again. After somes research, intelppm.sys is still normal and is present, what do you think ?

Thedoctor44 · 15 Jun 2014

intelppm.sys?

You shouldn't alter that driver, it's the Intel Processor Power Management driver that communicates with hardware, that is not the cause at all, it communicates with the hardware via a standard messaging interface it's only getting the blame because the hardware called a machine check exception that transfers information via intelppm.sys to windows to initiate the bugcheck.