Brand New asus and multiple BSODs on win.8.1/64b - a hardware problem?

[Teeto]

Hello there,

I have bought a brand new asus ux32la 14 days ago. Over time I have been experiencing random BSODs pointing to different problems, including irql not less or equal, kernel exception not handled or memory management error - to mention a few. I have restored the OS to factory settings, but the problems still persist.. Meanwhile I have ran a memory diagnostic tool (the one offered by windows os) and it has pointed to hardware problems with RAM. I also wanted to run a memtest 86+ test, but I to stumble upon problems with booting from a USB key - in the loading menu, when changing the boot device to USB nothing happens..

Attached are the dump and system readouts. I was wondering if you could help me with definately analysing whether the BSODs are caused by hardware, in which case I would have to avail myself of my guarantee with the vendor..

Many thanks and have a great day!

Teeto

View attachment perfmon.zip

 

[Patrick]

Hi Teeto,

Hold on, I don't think this is a memory problem, and Windows' diagnostic tool is by no means a good test for that (even though one might think it would be).

DPC_WATCHDOG_VIOLATION (133)

This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.

Since we don't have a kernel-dump, there's no way we can see what driver(s) causing the DPC hang. We can see if it was driver or driver(s) by checking the 1st argument:

3: kd> .bugcheck
Bugcheck code 00000133
Arguments [COLOR=#ff0000]00000000`00000001[/COLOR] 00000000`00001e00 00000000`00000000 00000000`00000000

1st argument = 1, this tells us multiple drivers caused it and not just one. This is also why we don't have an informative stack, as this happened some time before the crash, and not just with one driver (for example holding a lock).

---

1. AiCharger.sys is listed and loaded in the modules list which is the Asus Charger driver. It's included in many Asus bloatware, which you appear to have installed. Please go ahead and uninstall any and all Asus software as it's unnecessary bloatware.

2. Remove and replace McAfee with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's very likely causing conflicts:

McAfee removal - How to uninstall or reinstall supported McAfee products using the Consumer Products Removal tool (MCPR)

Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

-- FWIW, I would never have McAfee on any of my systems.

Regards,

Patrick

 

[Teeto]

Hi Patrick,

thanks for the informative response.

As for the drivers causing BSODs, I have a second zip folder of minidumps that happened before the OS factory restore (some 2 days ago), and from what I gather (although I m a layman here) igdkmd64.sys was the culprit then. Maybe I ll upload this file as well, so that we get a bigger picture on the problem.

View attachment minidump.zip

Meanwhile, I ll try to take the steps as advised in your post.

Regards,
Teeto

 

[Patrick]

I'll take a look at that if I need to.

I may ask for a different approach if we crash again.

Regards,

Patrick

 

[jcgriff2]

Hi -

I would definitely return the system and demand a new one given it is only 2 weeks old.

There is a great likelihood that this may be only the beginning of never-ending problems with the system.

Regards. . .

jcgriff2

 

[Jared]

I agree, my computer had issues from day one, I should have returned it but I knew nothing about computers and I was stupid. If it's within the 30 day time period then you should be able to get a refund if you are unhappy.