New
#11
Save msinfo32 as a .nfo file, a complete package please, and upload the .nfo in a zip file.
Please see attached zip.
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.
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.
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..
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
No problem :)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?
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.
It is not a definitive thought, if the mobo would be the cause then you would need to replace the laptop.Is this a definitive thought about the mobo? Because I can't get a replacement right now.