Forum Home
Press F1
 
Thread ID: 134692 2013-07-29 02:01:00 Ocasional lockup Driftwood (5551) Press F1
Post ID Timestamp Content User
1350083 2013-07-29 02:01:00 Occasionally system will lockup & eventually restart.
Below is the info displayed after restart.



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 5129

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004EC4038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\072913-14773-01.dmp
C:\Users\bert\AppData\Local\Temp\WER-42401-0.sysdata.xml



System is:
Asus P5Q Pro
Intel E8600
G-Skill 2x 2GB DDR2 1066
Seagate ST500DM002
EVGA GTX 560 ti
Win7 x64 HP 		Driftwood (5551)
1350084 2013-07-29 02:47:00 Disable the automatic system restarts upon BSOD, and have a look for the "STOP" code which comes up at the top of your screen when it *does* blue-screen on you. It'll be something like "STOP 0x0000008E" which is a whole lot more useful and easy to diagnose :) Chilling_Silence (9)
1350085 2013-07-29 02:56:00 Thanks.
Will do. 		Driftwood (5551)
1350086 2013-07-29 03:33:00 The error code is BCCode: 124 = 0x00000124

Theres more info, 124 is a general error code that can be almost anything, the mini dumps which usually have more info often don't lead to much help either.

What you are looking for is the wording after the 124 An example would be IRQL_LESS_THAN_OR_EQUAL

Have a look in the system Logs under eventvwr, look for any errors there and see if they report anything more. Could be hardware failing or corrupted drivers someplace. 		wainuitech (129)
1350087 2013-07-29 05:51:00 That can be hardware or CPU related. In some cases it maybe a faulty CPU, or some option in the BIOS that windows doesnt like. It can also happen if you're overclocking, or it maybe overheating Speedy Gonzales (78)
1350088 2013-07-29 06:44:00 From the Event Viewer/Windows Logs/System
Three Errors were logged at the time of the last freeze.

Source: WHEA-Logger, Event ID: 18

Details of one of them:

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor ID: 0 		Driftwood (5551)
1350089 2013-07-29 11:14:00 I would check the temps of the cpu. And check that its on properly in the case. There's 2 possible reasons why youre getting this stop error on the MS answers site.

1. Intel Matrix Storage Intel® Matrix Storage Manager version 8.9 was buggy, or something. Customers usually fixed it by updating it

2. The cooling in the case isnt good enough

3. Might pay to check the ram with memtest and to check the mobo for leaking capacitors 		Speedy Gonzales (78)
1350090 2013-07-29 22:02:00 Thanks Speedy I'll check those out. Driftwood (5551)
1350091 2013-08-03 03:52:00 Just a follow up on this problem.

Intel Matrix Storage Manager is the latest version which is 8.9

No problem with the cooling, in fact the problem only happens when the system is idling.

Memtest was ok & no sign of bulging capacitors.

Interesting that the first time this occurred was just after a windows update. 		Driftwood (5551)
1350092 2013-08-03 04:53:00 I'm pretty sure 8.9 is the version that can crash. Update it. I think its called Rapid storage tech now. The drivers maybe here (downloadcenter.intel.com)

Download the floppy x64 file. Extract it. Then go to device manager / IDE ATA / Atapi controllers / double click on the SATA entry / driver tab / update driver button / browse my computer / let me pick. Point it to the folder you extracted the floppy x64 file to. Then OK. Make sure Intel (R) ICH10R Sata AHCI controller appears in the window, before you load it. Reboot when it finishes/ says to. Then see how things go

Your mobo is similar to this except mines the P5Q SE/R. But they've got the same chipset, and this is the version of the SATA drivers I'm using at the mo, in Win8 x64 		Speedy Gonzales (78)
1 2