Freeze Crash/Freeze Auto Restart r/t Hal.dll

[C0d3nPix3Ls]

Hey Admin,

Only within the past week & a 1/2 that I have started to experience freeze crashes on the laptop. It usually only happens with online games/ YouTube/ or using MPC-HC for movies. I also use it for work and have to use Citrix.

I updated my Flash player but still the freeze crashes with the latest one being last night but interestingly the BSV pgm didn't capture it that time this again was while playing online. I have about two months ago did a full clean install and had no difficulties till now. Also noted in my log was Ntoskrnl.exe+189baf, PCI.sys9bcf. I looked into my issue and have noted that hal.dll could be anything from driver related to hardware. Since that is so broad, I am hoping to pin it down with your help.

Specs:
Model: ASUS G53JW
Intel i7-740QM Processor @ 1.73 Ghz
Motherboard Chipset - IntelHM55 (IbexPeak M DH)
Intel 5 Series/34x0 Chipset PCH
BIOS - American Megatrends Inc. Bios release date - 10/05/2010 G53JW.209
NIC (Network Interface Device) for Ethernet and Wireless. - Atheros AR9285 (Azurewave) 2.0.0.74 06/08/09
Sound - Nvidia GF106 High Def Audio Controller 1.3.30.1 11/27/13
Graphics Card - Nvidia GeForce GTX 460M - 9.18.13.3221 12/18/13
HD Model: Seagate ST9750420AS

What has been done by me:
1. DL'd update KB2685811
2. Purchased new power charger battery

Not done:
1. Updated any drivers (yet)
2. Installed every MS 7 update because of past bad experiences when doing so.
3. No Overclocking/Power setting changes

To also note, my issue is very similar to user MK000000 at this thread
but I didn't want to hijack as we may or may not have the exact same issue. Attached is my BlueScreenView log and DM Log Collector zip.

Thanks in advance for the support.

 

[ICIT2LOL]

Hello and welcome C0d3nPix3Ls now the dump below is indeed showing a hardware problem which hard ware has to be sorted out though.

WHEA_UNCORRECTABLE_[COLOR="Red"]ERROR (124)[/COLOR]
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: 0000000000000004, [COLOR="red"]PCI Express Error[/COLOR]
Arg2: fffffa80064698d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

This is suggestive (to me at least) an issue with the graphics driver so I think an update of that is in order it is here Drivers | GeForce if the top driver update doesn't work then you may try going back a version.

Now it would be interesting to also see the temps on the machine please use Speccy or anything of your choosing Speccy - Free Download - Piriform

Because there is also this

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff80003203000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

[COLOR="red"]BUGCHECK_STR:  0x124_GenuineIntel[/COLOR]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`031fda78 fffff800`037fba3b : 00000000`00000124 00000000`00000004 fffffa80`064698d8 00000000`00000000 : nt+0x70400
fffff880`031fda80 00000000`00000124 : 00000000`00000004 fffffa80`064698d8 00000000`00000000 00000000`00000000 : hal+0x12a3b
fffff880`031fda88 00000000`00000004 : fffffa80`064698d8 00000000`00000000 00000000`00000000 fffffa80`06468300 : 0x124
fffff880`031fda90 fffffa80`064698d8 : 00000000`00000000 00000000`00000000 fffffa80`06468300 fffffa80`064698b0 : 0x4
fffff880`031fda98 00000000`00000000 : 00000000`00000000 fffffa80`06468300 fffffa80`064698b0 fffff800`0338cbaf : 0xfffffa80`064698d8


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: [COLOR="red"]GenuineIntel[/COLOR]

IMAGE_NAME:  GenuineIntel

IMAGE_VERSION:  

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

 

[C0d3nPix3Ls]

Hi ICIT2LOL, Thanks for your reply. I DL'd the new graphics card driver as advised and tried it on my usual online game. So far so good as far as hang/crashing. My hope is that it will stay that way.

I am including the stats from Speccy though JIC since there were two Bug codes as you mentioned.
View attachment 397302

View attachment 397303

View attachment 397304

View attachment 397305

View attachment 397306

 

[axe0]

I can tell with certainty that the GPU is not the cause, because the device ID does not match with the device ID that caused the crash.

===============================================================================
Common Platform Error Record @ fffffa80064698d8
-------------------------------------------------------------------------------
Record Id     : 01d2996443a70409
Severity      : Fatal (1)
Length        : 672
Creator       : Microsoft
Notify Type   : PCI Express Error
Timestamp     : 3/10/2017 20:49:52 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : PCI Express
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006469958
Section       @ fffffa80064699e8
Offset        : 272
Length        : 208
Flags         : 0x00000001 Primary
Severity      : Fatal

Port Type     : Root Port
Version       : 1.1
Command/Status: 0x0010/0x0407
Device Id     :
  VenId:DevId : 8086:[COLOR="Red"]d138[/COLOR]
  Class code  : 030400
  Function No : 0x00
  Device No   : 0x03
  Segment     : 0x0000
  Primary Bus : 0x00
  Second. Bus : 0x00
  Slot        : 0x0000
Dev. Serial # : 0000000000000000
Express Capability Information @ fffffa8006469a1c
  Device Caps : 00008021 Role-Based Error Reporting: 1
  Device Ctl  : 0107 ur FE NF CE
  Dev Status  : 0005 ur FE nf CE
   Root Ctl   : 0008 fs nfs cs

AER Information @ fffffa8006469a58
  Uncorrectable Error Status    : 00000020 ur ecrc mtlp rof uc ca cto fcp ptlp SD dlp und
  Uncorrectable Error Mask      : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
  Uncorrectable Error Severity  : 00062030 ur ecrc MTLP ROF uc ca cto FCP ptlp SD DLP und
  Correctable Error Status      : 00000000 adv rtto rnro dllp tlp re
  Correctable Error Mask        : 00001100 adv RTTO RNRO dllp tlp re
  Caps & Control                : 00000005 ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP
  Header Log                    : 00000000 00000000 00000000 00000000
  Root Error Command            : 00000000 fen nfen cen
  Root Error Status             : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer
  Correctable Error Source ID   : 00,00,00
  Correctable Error Source ID   : 00,00,00

===============================================================================
Section 1     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80064699a0
Section       @ fffffa8006469ab8
Offset        : 480
Length        : 192
Flags         : 0x00000000
Severity      : Informational

Proc. Type    : x86/x64
Instr. Set    : x64
CPU Version   : 0x00000000000106e5
Processor ID  : 0x0000000000000003

Please search for "msinfo32" (without quotes) and press enter,

• save it as msinfo32.nfo,
• in explorer go to the directory where it is saved,
• right click the msinfo32.nfo file,
• choose 'send to' or 'copy to',
• choose 'compressed (zipped) folder',
• upload the zip file.

 

[ICIT2LOL]

Sorry late reply the temps look ok but I shall leave this one to axe.

 

[C0d3nPix3Ls]

Hi Axe -- So I went into the event log too because it did a sudden restart again this morning and that event didn't show up in Blue Screen Viewer. Looks like lots of issues though it being a clean install I am not quite sure what is going on... My thoughts on possible reasons after reading the logs:

1. Need a new laptop battery - the PSU is new. (Actually, I know I need to replace the battery because it powers down without the PSU plugged in. But I don't feel that is the core issue cause.)
2. More driver updates
3. Chipset update?
4. MS Windows 7 updates
5. The laptop is dying (I really hope this is not it, as I can not afford a new one and as mentioned use it for work)

What can I do next to fix the issues and salvage it? I attached viewer logs and the 'highlights' of the MS System Info



Thanks

 

[axe0]

Why is parts of msinfo32 saved as pdf and why those parts?

 

[ICIT2LOL]

My two cents worth for what it is worth use this to check out that battery se my pic

Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO - Download < download the right bit version and close the right hand window select Sensors and scroll down to the power section where you will see what the volts are doing see my pic. In my pic the section (Nuvoton) with VBATT as a dead give away you are in the section for the rail voltages. There are other section titles and one that pops up often is ITE (sometimes the usual one for Gigabyte boards)
Now the voltage on the different rails have to be within 5% =+/- of what is required or the machine will not work properly if at all.
Limits +/- (minimum - correct - maximum)
12v1 = 11.4 - 12 - 12.6v
12v2 = 11.4 - 12- 12.6v
5v = 4.75 – 5 - 5.25v
3.3v = 3.135 – 3 – 3.465v
-12v = -10.80 - -12 - -13.20v
+5VSB = 4.75 – 5 - 5.25v
The Power good signal voltage at pin 8 on the 24 pin plug (grey cable) should be the same as the 5v rail reading/s
See this for the rail voltage info
PSUs 101: A Detailed Look Into Power Supplies (Section 2.)
The original right hand window shows the machine running and is handy for that but for looking at the components in some detail close it and use the main left hand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in and then click on the individual component/s (it will highlight in blue) - in the right hand side will appear all sorts of details including brands speeds and other essential info that particular device. See pic for example.

Use the Sensor button and scroll down to the battery info.

Edit: I meant to say you only get the volts and wattage the latter is probably a better indicator of the battery status

 

[C0d3nPix3Ls]

Axe - Sorry about the PDF's - it's a default for the save type. I put those parts up because those are some of the usual suspects. But wanted to know your thoughts please on the saved logs as I think that provides some clues...

ICIT2 - I attached what I got from my battery using HWinfo

Thanks to you both for the continued support.

 

[ICIT2LOL]

Hmm can you let us know one more thing from that HW Info readout can you scroll down the listing to the memory timings please see pic/s of mine for comparison and reference.
My laptop here is about a year old.


Now the volts are unusual at 16.785 something so what is the output of the adaptor? Also the wear rate on that battery is quite bad and as you say you need a new one and I would say sooner rather then later.

Just out of interest how old is your machine?? I ask because I see the CPU was first released in March 2009.

 

[axe0]

Save msinfo32 as a .nfo file, a complete package please, and upload the .nfo in a zip file.

 

[C0d3nPix3Ls]

Please see attached zip.

 

[axe0]

Looks like I may be incorrect about the GPU, though it was based on the Speccy information.

The WHEA record shows 'd138' device ID, in msinfo32 it appears to be connected with a shared address between the Intel PCI-E port and the Nvidia GPU.


Just to note, if the GPU ultimately isn't the cause then the motherboard is the cause! D138 is the device ID of the Intel PCI-E port.

 

[C0d3nPix3Ls]

Hi Axe, Is this a definitive thought about the mobo? Because I can't get a replacement right now.

Question: are all of the uploaded error reporting logs also pointing to motherboard issues? Keep in mind though aside from updating the video driver, I have not updated other drivers, nor put on all the MS updates because the last time I did that it messed up the network. Not sure if putting those on will help or not.

 

[ICIT2LOL]

Actually just have close look at the board mate and see if there are nay caps that look like they are bulging or even leaking electrolyte. You might have a look for any signs of scorching on the printed circuit board itself if there is then it might also smell like a hot resinous odour..

 

[axe0]

ICIT2LOL, not sure if that is easily possible for OP (unless OP has experience disassembling the laptop).

 

[ICIT2LOL]

ICIT2LOL, not sure if that is easily possible for OP (unless OP has experience disassembling the laptop).

Oops my bad wasn't thinking straight there

 

[C0d3nPix3Ls]

@ICIT2LOL, not sure if that is easily possible for OP (unless OP has experience disassembling the laptop).

That's correct regarding manipulating the hardware. Not my forte. Software stuff, yes.

I hate to sound like a broken record guys, but does the windows error reports that I uploaded point to updating any drivers and/or Windows updates to resolve the problems? And if so, which drivers/updates?

Please let me know this first before we move forward.

Thanks

 

[C0d3nPix3Ls]

Hmm can you let us know one more thing from that HW Info readout can you scroll down the listing to the memory timings please see pic/s of mine for comparison and reference.
My laptop here is about a year old.


Now the volts are unusual at 16.785 something so what is the output of the adaptor? Also the wear rate on that battery is quite bad and as you say you need a new one and I would say sooner rather then later.

Just out of interest how old is your machine?? I ask because I see the CPU was first released in March 2009.

++++++++++++++++++++++
Posting this in regards to Icit's observation in post #10 for the sake of not missing any steps... but please let me know the answer regarding the drivers and/or updates first.

 

[axe0]

I hate to sound like a broken record guys, but does the windows error reports that I uploaded point to updating any drivers and/or Windows updates to resolve the problems? And if so, which drivers/updates?

No problem
The crash, 0x124, is a hardware crash. Windows has caught a hardware malfunctioning and couldn't correct it, this can happen for various reasons like overclocking, overheating, BIOS issues, driver issues, hardware and even software. Some software, like Gigabyte, ASUS and MSI, are known for causing issues.

When something calls this bugcheck, the system crashes and is being provided with an error record. We use the error record to identify why the crash was called, unfortunately quite rarely is also the cause why the crash occured provided.
This means that we guess our suggestions based on the information you provide us.

I would suggest to reinstall/update the chipset drivers and the GPU drivers from ASUS and check for BIOS updates.

Is this a definitive thought about the mobo? Because I can't get a replacement right now.

It is not a definitive thought, if the mobo would be the cause then you would need to replace the laptop.