Solved Frequent BSOD on new ASUS Notebook, poss. ntoskrnl.exe?

[omega1227]

My notebook is an ASUS X53U running Windows 7 Home Premium 64-bit edition. The computer is a little over two months old (received it as a Christmas gift) and it had worked perfectly fine up until a few weeks ago when I began experiencing seemingly random BSODs. So far I have not been able to find out how to force it to happen, all I can say is the first two times it BSOD'ed the .dmp file showed that it was "hal.dll" causing the problem, now every single time since the problem seems to be caused by "ntoskrnl.exe." Like I said, the crashes are completely random, sometimes happening once a day and other times happening three or four times in an hour. I tried to figure out what was going on by looking at the .dmp files in WhoCrashed, and it seems to be indicating a hardware error. The only external hardware I have hooked up to my PC is a mouse, which does randomly stop working on occasion. Could there be an issue with it? Also, this may not be true "hardware" persay, but I do have a virtual CD-ROM drive installed through Virtual CloneDrive.

System Specs:

ASUS X53U Notebook
Windows 7 Home Premium 64-bit
AMD E350 Processor 1.60 GHz
4.00 GB Ram

 

[zigzag3143]

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

Some generic advice.

If you are overclocking STOP. Return to the default settings at least for now.
If you are running a RAID update its driver.


You can read more on this error and what to try here... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[omega1227]

Thanks for the prompt reply zigzag3143. I have not set my computer to be overclocked and I to my knowledge I am not using a RAID.

 

[scrooge]

if it's still under warranty i'd take/send it back and get them to fix it. you should not be getting hardware trouble on a new notebook.

scrooge

 

[omega1227]

That's what I was trying to avoid doing... I'm sure it's probably something I installed, because it was fine until I installed all my software on it. The only problem is determining what. Can hardware stop errors be caused by a bug in software?

 

[zigzag3143]

That's what I was trying to avoid doing... I'm sure it's probably something I installed, because it was fine until I installed all my software on it. The only problem is determining what. Can hardware stop errors be caused by a bug in software?

One thing I have seen cause 124's is if in msconfig max cpu, and max ram are checked. They both (along with legacy floppy support) should be unchecked

 

[omega1227]

I've been updating my drivers since yesterday in hopes that a corrupt driver is the problem. However, I also discovered while digging through my error files that there seems to be some problems with the Tages Protection service. It seems to be crashing shortly before I get a BSOD, mainly with atkgfnex.exe, asmmap.exe, lirsgt.sys, and other files controlled by ntoskrnl.exe. I'm going to keep at this until I figure it out.

 

[omega1227]

Figured I'd follow up for future readers. My final determination is that either a driver or something else became corrupted, possibly during an update. I spent several hours running in safe mode yesterday without a single BSOD, so I decided to simply pop in my AI Recovery discs and revert to my factory state. Since then I've been running smoother than ever and haven't had a single BSOD. I think it's safe to say I'm good to go.