Solved BSOD need assistance please

[warbirds]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800750D8F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Steps taken so far:

1. updated graphic card sriver
2. ran system in safe mode for over an hour resulting in NO BSOD
3. ran virus, malware, reg clansers resulting in no issues found.
4. new system with clean Windows 7 install (all updates to date completed)


see attached file:

 

[richc46]

We need the informatiion below to confirm
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

If you are indeed code 124 you will be given this Thread
Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

 

[warbirds]

BSOD

We need the informatiion below to confirm
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

If you are indeed code 124 you will be given this Thread
Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

* Not a cooling issue. Verified w/Speedfan. Today issue occured less than 2 mins from cold boot. System was running @ 27C
* Ran Memory Check no issues found
* Problem does not occur in "safe mode"

Going to try BIOS update next.

Thank-you

 

[warbirds]

We need the informatiion below to confirm
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

If you are indeed code 124 you will be given this Thread
Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800750D8F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Steps taken so far:

1. updated graphic card sriver
2. ran system in safe mode for over an hour resulting in NO BSOD
3. ran virus, malware, reg clansers resulting in no issues found.
4. new system with clean Windows 7 install (all updates to date completed)


see attached file:

Dedails of error


==================================================
Dump File : 111610-21372-01.dmp
Crash Time : 11/16/2010 9:13:17 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`06de88f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a587c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\111610-21372-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================


Caused By Driver : ntoskrnl.exe

ok what is this and how to fix?

 

[richc46]

Thats a Microsoft Kernal Driver, not the cause
Per the 124 report. Hardware caused it to fail
Ntoskrnl.exe file description

Productname: Microsoft® Windows® Operating System
Description: NT Kernel & System
Company: Microsoft Corporation

You could try an SFC command, but it will not help
In an elevated cmd prompt type sfc /scannow

 

[zigzag3143]

Just a drive by.....

One thing to add to Rich's excellent posts. There is a two year old driver that should be updated PxHlpa64.sys. This has a copywrite from Sonic Solutions, and seems to be part of movie maker,

 

[richc46]

When errors are found, run SFC up to 3 times. If there are still significant problems that cannot be repaired a repair install is suggested.
http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[warbirds]

next step

When errors are found, run SFC up to 3 times. If there are still significant problems that cannot be repaired a repair install is suggested.
http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

ok I'll try running sfc /sccannow 3x.

Question: Why does the problem does not occur in "Safe Mode" and the error code that you stated is Hardware related? Is the the same as a hardware driver issue?

 

[CarlTR6]

Hardware related does include driver issues.

 

[richc46]

Carl is correct of course
You can try a clean boot, if it does not work, it is almost definately a driver
http://support.microsoft.com/kb/929135

 

[CarlTR6]

You can help us help you better by uploading your dumps and the system files generated by the tool is this tutorial. Rich mentioned this in an earlier post. We need to see the actual dump files and the system files.

Blue Screen of Death (BSOD) Posting Instructions

 

[warbirds]

dump file

You can help us help you better by uploading your dumps and the system files generated by the tool is this tutorial. Rich mentioned this in an earlier post. We need to see the actual dump files and the system files.

Blue Screen of Death (BSOD) Posting Instructions

The file is there in my 1st posting. File name is minidump.zip.
As I see more information is required per the instructions above. I'll upload this later tonight. TY.

I would like to thank everyone who has assist in trying to resovle this issue.
They dont make this cut and dry......

 

[CarlTR6]

No, I'm afraid it is not cut and dry. We will be waiting for your upload.

 

[warbirds]

update: bsod report

Attached is bsod report. Ran sfc /scannnow and so far no BSOD but the end report still states issues still exist.

 

[CarlTR6]

How many times did you run sfc? When it is reporting errors, you should run it at least three times. All of these dumps are error code 124, a fatal hardware issue. You still have a very outdated driver on your system; it is an XP driver. Navigate to C:\Windows\System32\Drivers and rename this driver from .sys to .bak. Reboot and the driver will not load. This will break the software this driver is associated with. If you know what software it belongs to, uninstall the software. It is obsolete.

PxHlpa64.sys Fri Feb 02 16:24:22 2007

I also found an almost guaranteed BSOD maker:

ASACPI.sys 3/27/2005 - ATK0110 ACPI UTILITY
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 8th 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 2005).

Take care of these two drivers and see how your system does.

 

[CarlTR6]

I kept looking through your system and found one more outdated driver. Please update this driver along with those above.

yk62x64.sys 5/20/2009 - NDIS6.2 Miniport Drive, Marvell Yukon Ethernet Controller.Marvell: Support

 

[warbirds]

How many times did you run sfc? When it is reporting errors, you should run it at least three times. All of these dumps are error code 124, a fatal hardware issue. You still have a very outdated driver on your system; it is an XP driver. Navigate to C:\Windows\System32\Drivers and rename this driver from .sys to .bak. Reboot and the driver will not load. This will break the software this driver is associated with. If you know what software it belongs to, uninstall the software. It is obsolete.

PxHlpa64.sys Fri Feb 02 16:24:22 2007

I also found an almost guaranteed BSOD maker:

ASACPI.sys 3/27/2005 - ATK0110 ACPI UTILITY
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 8th 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 2005).

Take care of these two drivers and see how your system does.

This link above went to another MB. Mine is ink above went to a different MB. Mine is this:

http://support.asus.com/download/download.aspx?modelname=P6X58D

And yes ran sfc /scannnow 3x's

 

[warbirds]

ok all has been done as requested with one problem.
PxHlpa64.sys Fri Feb 02 16:24:22 2007 made changes as instructed bt caused driver issue with DVD/CD Drive.

 

[CarlTR6]

Good job. You can rename the driver back to .sys. after you know your system is running smoothly. This is an attmpt to eliminate all potential problems. It may be that you can run with that driver. How is your system doing?

 

[warbirds]

update

Good job. You can rename the driver back to .sys. after you know your system is running smoothly. This is an attmpt to eliminate all potential problems. It may be that you can run with that driver. How is your system doing?

So far so good. Well I'm going to be optimistic that this did the trick.