BSOD's 0x00000124, 0x0000009f, 0x000000f4 , 0x000001e, 0x000000d1

[Antisladd]

Yea the last couple of weeks i've been getting bsods alot, most of them have created a dumpfile some havn't.

This is the computer info:
OS Windows home premium x64

CPU Intel core 2 quad Q6600

Motherboard Asus P5Q pro turbo

Memory 8gb ddr2 667mhz

Graphics Card(s) 8800gts + 8800 gt

Monitor(s) Displays benq 2410t + benq g2420hd Screen Resolution N/A

Hard Drives 120gb ssd ocz agility 3
4x mechanic drives connected to sata

PSU ace of sweden AC-620RD+ 620w


I've tested som of my hardware and done som changes from solutions i found from my googlesearches,

I ran memory test for about 5 hours no problems,
I have tested to remove 2/4 memorysticks and then the other 2, no difference either way,
I've tried to increas my vcore to 1.3v since ppl saying hal.sys might be caused by that
i also tried increasing volt on memory no difference, it's back on 1.8v again
i have also removed one of the graphiccard the 8800gt, to se if that was the problem or maybe if the psu just couldn't deliver enough power.

I dont rly know how to follow up i've been using BlueScreenView trying to find additonal info, but no luck.

system files listed are
jraid.sys
hal.sys
ndis.sys
crashdump.sys

and also

ntoskrnl.exe


All the dumps are attached hope you could help me with some solution
//Karl

P.S.
If a clean install would help i can do that, either on ssd again or on one on the mechanic disks.
D.S.

 

[zigzag3143]

While a 124 (and thy all are) is hardware related there are a couple of software issues that need addressing


First:

Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

Second

You jraid.sys mentioned in several of the crashes. I would re-install using newest driver available.

 

[Antisladd]

"Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE"

Is that a new bios version? i got a .rom file when downloaded it is that correct?

I've never flashed my bios u se so wanna make sure it's alrightI have found and updated the other 2 though so just this left,
Thanks for the quick respons!

 

[zigzag3143]

"Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE"

Is that a new bios version? i got a .rom file when downloaded it is that correct?

I've never flashed my bios u se so wanna make sure it's alrightI have found and updated the other 2 though so just this left,
Thanks for the quick respons!

Let us know if you need help.

 

[Antisladd]

When i try to flash bios through i get message "the file size does not match existing bios size"

 

[Antisladd]

And are u sure that's the one i should use? my motherboard is a p5q pro turbo isnt this the one?
ASUSTeK Computer Inc. -Support- Drivers and Download P5Q PRO TURBO
and then i download that latest bios and try and flash is that correct? or did i jsut do something wrong with the first one?

 

[writhziden]

You are correct with the link you gave for your board. Do not flash the BIOS until it is recommended. I did not see it recommended. The only thing recommended is the driver update for ASACPI.sys which there is an update via your motherboard site: ASUS - Motherboards- ASUS P5Q PRO Turbo
The update is under Utilities, and is the first one in the list: ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

Also, under Others in the downloads, you will find a driver update for your RAID controller.

 

[Antisladd]

Oh yea i already upgraded those 2 drivers and i flashed the motherboard aswell, didn't se it wasn't recomended yet.
Haven't hade any problems with it though it seems.

In the last like 3 days now i've had one "crash" it wasn't rly a bluescreen though, i just noticed computer getting laggy whyle i was in windows not rly doing anything speciel and over the duration of a few minutes, maybe 5, it keept on getting slower, though memoryusage was low(less then 25%) and so was CPU usage(less then 20%).
And after around 5 minutes it got so slow it stopped and nothing more happend, it was just frozen.
I hade to press start button to shut down the system, when i started up again i just said system didnd't shut down correctly and asked if i wanted a normal boot or boot in safe mode.


So i seems like it might be working now or i haven't gotten any of those bluescreens atleast.
And this "crash" feels like if it might be something else. For example my psu is known to fail, so i'm thinking that maybe it fails to deliver power or something like that.

Any thoughts?
I got vcore on auto again but i still only use the gts 8800 and not the gt8800 aswell.

 

[writhziden]

Did you flash the BIOS with the newest version for your board and not one of the other two boards (I hope)?

The problem you are experiencing could be an application or service conflict. http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html may help.


Additionally: Please provide us with your Event Viewer administrative logs by following these steps:

1. Click Start Menu
2. Type eventvwr into Search programs and files (do not hit enter)
3. Right click eventvwr.exe and click Run as administrator
4. Expand Custom Views
5. Click Administrative Events
6. Right click Administrative Events
7. Save all Events in Custom View As...
8. Save them in a folder where you will remember which folder and save as Errors.evtx
9. When asked, save the display information in English.
10. Go to where you saved Errors.evtx
11. Create a new folder by right clicking in a blank area within the folder Errors.evtx is saved in. You could also click New Folder at the top of the directory under the directory path box.
12. Name the new folder Errors.
13. Place Errors.evtx and the LocaleMetaData folder into the new Errors folder.
14. Right click the Errors folder -> send to -> compressed (zipped) folder
15. Upload the .zip file here.

 

[Antisladd]

Okay here is the files u requested, ty very much for helping!
and i used the bios for my motherboard.

 

[writhziden]

Windows does not appear to be running as it should:

• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

 

[Antisladd]

Got another crash where the computer started to slowly lagg more and more but this time it ended with a bsod after about 5 minutes, got the 0x00000124 code this time again.
will include the new dump as zip, also got the memorydump if that would be helpfull? but it is 120mb compressed

and as i have mentioned, vcore is auto and memory volt is auto aswell

I also now saw ur last post so i will test that and se what happens.
Thanks!

 

[Antisladd]

First i tried binks option and ran it in windows by starting command promt as administrator and typing the sfc /scannow command, found nothing 3 times in a row with restarts inbetween
then i ran one round using the windows disk and going to repair and then the sfc / scannow /....... w/e it was.
non of them found anything wrong

 

[writhziden]

That's good that there were no obvious problems with Windows. Do you use any optimization tools to clean your registry?

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Antisladd\032912-17893-01\032912-17893-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c52650
Debug session time: Wed Mar 28 21:48:53.418 2012 (UTC - 6:00)
System Uptime: 1 days 14:55:51.932
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009776028, f2000040, 800}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware

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

3: 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: fffffa8009776028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  cpuz.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`031dda58 fffff800`03008a3b : 00000000`00000124 00000000`00000000 fffffa80`09776028 00000000`f2000040 : nt!KeBugCheckEx
fffff880`031dda60 fffff800`02b9ac43 : 00000000`00000001 fffffa80`09855660 00000000`00000000 fffffa80`098556b0 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddaa0 fffff800`03008700 : 00000000`00000728 fffffa80`09855660 fffff880`031dde30 fffff880`031dde00 : nt!WheaReportHwError+0x263
fffff880`031ddb00 fffff800`03008052 : fffffa80`09855660 fffff880`031dde30 fffffa80`09855660 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddc50 fffff800`03007f0d : 00000000`00000004 00000000`00000001 fffff880`031ddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddc90 fffff800`02ffbe88 : fffffa80`0aa57000 fffffa80`06990920 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031ddcc0 fffff800`02a8962c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031ddcf0 fffff800`02a89493 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dde30 fffff880`0f426dca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009b0b00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1eadca


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

Something is not happy with your graphics card. Hard to tell if it is software or hardware related. Did you http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html?

Do some hardware checks:

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest