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

**axe0** · 22 Mar 2017

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

C0d3nPix3Ls · 23 Mar 2017

Please see attached zip.

**axe0** · 24 Mar 2017

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 · 24 Mar 2017

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 · 24 Mar 2017

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** · 25 Mar 2017

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

ICIT2LOL · 25 Mar 2017

axe0 said:

@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 · 26 Mar 2017

axe0 said:

@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 · 26 Mar 2017

ICIT2LOL said:

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** · 26 Mar 2017

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.