Solved Seemingly Random BSOD. STOP ERROR: 0xA, 0x7E, 0x124 mostly.

[diamondwolf]

**The following will be a pretty long post of what I've tried over the past couple days from reading this forum as well as a few others to get an idea of where to start.**

**In case someone only glances at this and ask me to post the memory.dmp file as I have explained below at this point in time the computer will not boot into Windows.**

Basic System Info:

- x86 (32-bit) or x64 ? Windows 7 Ultimate x64
- the original installed OS on the system? None
- an OEM or full retail version? Full Retail
- What is the age of system (hardware)? 2½ Years
- What is the age of OS installation (have you re-installed the OS?) No more than 24 hours.

=More Detailed Specs=
Model: Sager NP8120
CPU: Intel® Core™ i7-840QM
GPU: ATI Mobility Radeon HD 5870 x2 in CrossFire
RAM: 8BG (Two 4GB sticks)
HDD1: The one that wouldnt install Windows was a SeaGate 500GB, currently a Hitachi 320GB)
HDD1: Came with a WD Scorpio Blue 640GB, currently have the SeaGate 500GB in this slot as I wanted to try it one more time with the Windows 7 install, ofcourse it failed.(See below).
Other less detailed things: Had my Razer Naga/Laptop fan plugged into 2/3 USB ports (removed this when trying to boot into safe mode), nothing in USB 3.0 ports. Built-in Webcam/Fingerprint Reader. RealTek 8168D and Intel Centrino Ultimate 6300-N.

I dont know if all of the above information is relevant but might as well post it as well.

Last week I decided to reformat my Sager laptop and do a fresh install. Everything was fine for a while until about this weekend.
I started getting random blue screens or the computer would just restart. Sunday night I continued reading up on the issues and doing some of the troubleshooting steps listed on this site. At first I figured it was a driver issue, and tried to reinstall the OS again, and its been a couple days so I dont remember the exact error now. I ran a HDD check with SeaTools, it found a few errors. I told SeaTools to repair it, once it was complete I ran the check again, and it came back clean. I tried to reinstall Windows however it would come back with a 0x124 STOP ERROR. It would expand the system fils, install, and I think about the time it went to boot into the new system is when the BSOD would occur. Still getting BSOD on a new install I understand this would not be a driver issue. I burned a copy of memtest86+ to a USB with the executable from the site, and let it run as I slept. Wake up 5 hours later, no issues. Pulled a Hitachi 320GB HDD out of the Gateway laptop I'm typing on now, put it into my Sager and proceeded to install Windows.

SUCCESS! Or so I thought. After finishing to install drivers on my new OS (downloaded them from the www2.sagernotebook.com website), checked device manager, all seemed find. Installed windows update, 113 updates on a fresh install, and it blue screened again (as per the title, I have gotten 3 different stop codes, I believe this one was another 0x124). I ran the Windows Update again and checked it for BSOD in the meantime. First thing I did upon reinstalling Windows 7 was uncheck auto restart upon failure so if it did BSOD I wouldnt miss it. Last I saw it was on around update #87 or so, almost finished but it however BSOD'ed again.

Forgot to mention the next thing I did after disabling auto restart was download RealTemp/Furmark. Earlier last week when all I had was an occasional BSOD and a random restart, I always had MSI Afterburner running in the background while playing SWTOR and the GPU's never hit above 60°C. Running FurMark for a while the GPU's would reach around 70/74°C for GPU1/GPU2 respectively. Idle the GPU's were around 38~40°C. Idle the CPU would sit around 38~40°C and I think the most it got while I was running Windows Update/the test on the CPU with RealTemp was around 50°C, but never for long. Also before I forget I also ran the Windows Memory Diag on Basic (2 passes) and again on Standard with 5 passes after more blue screens, no errors reported. Though I have read that it could report no errors and the RAM actually is bad, so who knows.

I had set Windows to run a chkdsk upon the next reboot, and this is wear I'm currently at. Upon booting into Safe Mode it loads all of the devices/core drivers, and hangs. At the very top of the screen is a small row of artifacting. This happened when I first tried to boot into Safe Mode with Networking as I just received a BSOD and wanted to boot into safe mode, load BlueScreenView, note the driver and look at it with WinDbg for further explanation. I held the power button, booted back up, and chose just Safe Made, no networking, same issue. Safe Mode with Command Prompt? Same issue. Boot using last known good configuration and it starts the chkdsk I told it to run just to make sure the Hitachi wasnt already bad as well. When it tells me to press any key within 10 seconds it reaches 1 second remaining to skip it and then seems to hang.

I have received the STOP ERROR codes 0x124 the most or equal to the amount of 0xA's, and a couple odd 0x7E's as well. One I know pointed to Netwsw00.sys which I have read is from Intel's Wireless driver, which was before I tried to reinstall, failed, replaced the HDD with the Hitachi and installed successfully. The 2nd most recent said something to the effect of Netws64.sys or along that which makes me believe it could be the wireless driver, but with the 0x124 it's my understanding this is usually hardware itself. From what I can tell however BlueScreenView mostly list only ntoskrnl.exe as the cause, or every once in a while it will also list hal.dll, very few times does it actually list the driver.

That given the old HDD that would not install as mentioned above is in the 2nd slot, and disabled. The RealTek 8168D showed a yellow ! caution and was previously disabled, with the driver software removed. All drivers were downloaded directly from www2.sagernotebook.com, and driver installs/updates downloaded by Windows 7 was disabled upon install.

I would love to post the MEMORY.DMP log for further advice, however I cant even boot into Windows and read it myself. ^^; I've read through some of the post on this forum, and even skimmed over the STOP ERROR 0x124 what it means and what to try, however this is a laptop which is a PITA to try to take apart unlike a desktop. I'm more curious on what the horizontal row of artifacting at the top means and what some of you think of this/what it points to as this seems to be the newest symptom. I'm assuming maybe RAM/GPU/CPU? but I'd like to have an idea of where to start before I go around taking parts out of the computer again. I'd rather not send it off to have it repaired if I can get a reasonable diagnosis myself as I'm sure it would cost me a kidney in the process. Any ideas/tips/theories would be much appreciated. Thanks in advance.

 

[Vir Gnarus]

It's really hard to tell because there's very little raw data we can go on with this. It does sound that the memory is ok given your diagnostic runs on that, and it's evidently not the drive because you swapped drives and tested them and they came up ok. So we can rule those two out.

I feel we're dealing with the dreaded Trio of Trouble, which is CPU/Mobo/PSU. The WHEA errors (0x124 bugchecks) support this suspicion. Aside from some hardware tools like a PSU tester n stuff, there's unfortunately no definitive means of testing these items outside of placing them in perfectly reliable PCs. Not only that but we're dealing with a laptop here which makes things much worse in regards to swapping hardware, though it is a Sager which helps a bit. I still recommend you call them up and issue it for servicing, because it may be out of your service contract to try and replace these components yourself.

If you want, you can write down the numbers for the next 0x124 bugcheck you experience. There should be some parentheses with 4 numbers separated by commas. I need at least the last two. These will help me determine exactly what the error is for that particular bugcheck.

 

[diamondwolf]

Update:

Thanks for the reply! Thats actually what I was scared of was one of those but I do have an update.

Windows Start Up repair seems to have fixed the booting issue. The dump files have been cleaned, along with NET 4 Framework and WinDbg gone. BlueScreenView only shows one and that is a STOP ERROR code 0xA. It also list NETwNs64.sys as the culprit. Does this explain the hanging when trying to boot into Safe Mode with Networking? What about the small horizontal row of artifacting at the top of the screen? This combined with a 0x127 error code does it mean the driver is causing the wireless chip to crash or is the hardware causing the driver to crash?

While typing that on my Sager it BSOD'ed to another 0x124, I did not get the parameters but assuming I can boot back into it I will get you any information I can. Please refresh every once in a while as I'll edit not to double post.

Update: I tried booting into Windows normally, and was met with another 0xA. Reboot, and boot into Safe Mode. Artifacting in the top left of the screen but only a small line and not entirely across it. Seemed to hang at CLASSPNP or whatever its called but continued anyways. Mentioned Windows Update failed, reverted changes, and I was able to log in. Generated a report from BlueScreenView and sent it to a flash drive to paste containing a 0xA and a 0x124. I had generated the info using the Windows_NT6_BSOD_jcgriff2.exe but was met with another 0xA the moment I thought about sending it to the flash drive. Here is the 0xA and 0x124 report BSV generated before that though.

0x124
Code: 0x00000124
Parameter 1: 00000000`00000000
Parameter 2: fffffa80`0871a028
Parameter 3: 00000000`b2000000
Parameter 4: 00000000`00070150
Caused by: hal.dll
Crash Address: ntoskrnl.exe+71f00

0xA
Code: 0x0000000a
Parameter 1: 00000000`00000008
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000001
Parameter 4: fffff800`022df9bf
Caused by: NETwNs64.sys
Crash Address: ntoskrnl.exe+71f00

 

[Vir Gnarus]

Actually, while the numbers are nice, now that you have access to your files, can you provide the minidumps? They are located in /Windows/Minidump directory. That will greatly increase the amount of info on this.

This is really sounding more and more like your motherboard. Still, I'll run through these to see if I can get more info. In the meantime, you will want to install the lastest driver updates for everything, and that includes BIOS and firmware. I however am certain we're dealing with failed hardware, but it doesn't hurt.

 

[diamondwolf]

Just tried.

I thought about that after my last post, however I was met with a 0xA twice in the process. I uninstalled my wireless and the software as it seemed to be the usual culprit, but before I could atleast copy the minidumps to a flashdrive (I downloaded WinRar but it seems to have disappeared like WinDbg and .NET 4 after the start up repair) so I could zip it and attach it. Unfortunately I would love to troubleshoot some more but the Army made me make a vision appt and that happens to be today, lol. I'll try to get a copy of the minidump off the laptop after my appointment. I really hope its not a motherboard issue as I've replaced that an in old gateway before, was not fun. Laptops have too many screws, lol. Anyways, thanks for your help and check back in a couple hours, hopefully I'll have some luck in getting the minidump when I get back.

 

[diamondwolf]

Minidump and Windows_NT6_BSOD_jcgriff2 rar

Files requested and as stated from the BSOD - Posting Instructions topic.

Minidumps: View attachment 220848
Windows_NT6_BSOD_jcgriff2: View attachment 220849

I'll try to update the drivers if my laptop will last that long. The Intel Wireless driver in the Windows_NT6_BSOD_jcgriff2 was the one I got from the Intel site, however since it seemed to be the cause of most of the 0xA bluescreens I have removed it from device manager along with uninstalling the drivers.

 

[Vir Gnarus]

The one 0x124 bugcheck I see is caused by a failure to read (and therefore execute) an instruction stored in your instruction cache for your CPU (L0 cache). I also see what appears to be your CPU registers 'magically' losing their contents, which is the cause of your 0xA bugchecks. All of this points to CPU failure as most likely cause, followed by PSU and then motherboard. Any of these components aren't really interchangeable in a laptop, so your best bet is to have Sager service or replace the item. If you are feeling adventurous you can try replacing the CPU yourself, but replacing any parts in there aside from the memory and drive will prove very risky.

Unfortunately, as I've stated before, there's no way to definitively test any of these three.

Analysts:

0: kd> !errrec fffffa800871a028
===============================================================================
Common Platform Error Record @ fffffa800871a028
-------------------------------------------------------------------------------
Record Id     : 01cd5ec4183f7fa5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/10/2012 18:26:35 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800871a0a8
Section       @ fffffa800871a180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    :[COLOR=Red] Cache error[/COLOR]
Operation     : [COLOR=Red]Instruction Execute[/COLOR]
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000106e5
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800871a0f0
Section       @ fffffa800871a240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : e5 06 01 00 00 08 10 00 - fd e3 98 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800871a240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800871a138
Section       @ fffffa800871a2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Red]ICACHEL0_IRD_ERR[/COLOR] (Proc 0 Bank 2)
  Status      : 0xb200000000070150

 

[diamondwolf]

I hope not.

I'm kind of curious. The other day when I reformatted the computer I had went to sleep and when I woke up all was fine. No random errors or anything so could it be something I had installed driver wise from the sagernotebook site or is it more than likely hardware related given the analysis?

I have taken out the CPU and heatsink before a few months ago, I think I've actually had it for only a little over a year, but in that time the heatsinks for the GPU/CPU were clogged with dust build up and it was getting pretty hot so I removed them and blew them out, also reapplied Arctic Silver 5. So I feel pretty comfortable in doing that.

Just wondering if anything like bad chipset drivers from the sager website could also be to blame before I spend like $600+ on a CPU.

 

[Vir Gnarus]

These issues are commonly caused by hardware failure, especially if we're dealing with your L0 cache for your CPU. However, there are rare occasions where bugs in BIOS or chipset drivers can mess things up and give false positives of stuff like this. That's why I recommended they be updated in my previous post since it's always good to get that out of the way first before dealing with the hardware involved.

 

[diamondwolf]

Will do. Though also with a couple questions, before I forget though I do want to express my gratitude for your help. So, thank you, Vir.

1) I have looked into that and also looking at the chipset drivers downloaded from Sager, it had it listed under the read me as Intel(R) 5 Series/3400 Series Chipset. Looking at the laptop it also has the same thing listed under the device manager. Intel has 3 listings under:

Desktop: Intel(R) 5 Series Chipset
Laptop: Mobile Intel(R) 5 Series Chipset
Server: Intel(R) 3400 Chipset

I understand its laptop, so I would think the Mobile of course, however it doesnt specifically state Mobile like my Gateway (the one I'm currently typing this from), where it specifically has Mobile Intel(R) 4 Series Chipset Processor to DRAM Controller - 2A40 under the device manager. I'm gonna guess since its not a server but a gaming laptop I can rule out the server. But just for clarification would I download the Desktop or the Laptop(Mobile) 5 Series chipset? Probably a dumb question, but I dont normally touch chipset drivers myself.

2) Im going to guess from the format of your previous post you used WinDbg to read through the minidumps. But I was wondering how you interpreted all of that and what command you ran it with. Not that I'm seconding guessing that, I believe you as you pointed out somethings and gave some pretty good detail. Not many sites have said anything about how to do that, was just wondering if you could explain or if you do know of a site I would like to read it too.

Again thanks for your help. Very much appreciated.

Short update so I dont double post: So far since this morning I have reformatted, instead of going through all of the drivers one by one over again. I realized after googling the WiFi drivers the other day I searched Intel's site manually today. I found they have 2 entries for the "Ultimate-N 6300" and "Ultimate-N 6300 and 6200". So I downloaded the one specifically for the 6300 and have had no issues with blue screens supposedly caused by those drivers since. Actually I've had no blue screens over the past 5 hours at all. Here's hoping that it continues!

 

[Vir Gnarus]

The custom laptop Sager makes probably uses a motherboard that makes use of a desktop-grade chipset. There's also the possibility that the chipset driver suite you found pertains to all related chipsets, be it mobile or otherwise. It's hard to determine without actually figuring the exact model. I guess it's a Clevo x8100. Can't really tell from what's given (Hwinfo may figure it out). I'm sure the specs for your laptop will tell you.

As for using Windbg, I took the second argument of the bugcheck and fed it to the !errrec command (that's 3 'r's). The second arg for the bugcheck is the address of the WHEA_ERROR_RECORD data structure that contains all the relevant info. The !errrec command just displays it all in a readable format. One can also decipher the gist of it just by looking at Arg3/Arg4 of the bugcheck and whipping out the Intel developer manual (free download) and looking up the MCi_STATUS bit flags they're associated with, but it's a legacy way of doing things and obviously more difficult. Good for when system fails to generate crashdumps, though.

I learned all this just from pretty much scouring the internet for information on kernel debugging for over a year. I got a lot of resources I saved up in the link in my signature, plus my own personal noteworthy experiences. Understand I'm still an amateur; I cannot guarantee the info I provide is accurate.

 

[diamondwolf]

Yes its a Clevo X8100. Might check out HWInfo and see what it reports and update the chipset drivers based off of that, as I thought the same about maybe it uses a desktop grade chipset, so I was kind of hesitant to just pick one and install. Matter of fact right now I have just installed drivers from the CD, albeit they are older I do know they work for one. Last time everything went into a catastrophe after trying to install Windows updates, and went to a blue screen towards the end of them. So far however, I have installed most of them and only have a few minor ones left, plus the SP1 update. But most importantly, no BSOD's at all!

Thanks for the info on this. I love looking into new things and learning more about computers. I guess since you learned by scouring the internet you're the same way. Will definitely try to find some examples online and check out the developer manual plus the link in your sig.

Thanks again for the help man, I'll post back if I get any BSODs or even if I dont in case someone else has/is having this issue and they find this post.

 

[diamondwolf]

Today all seemed fine however while I was playing SWTOR the computer completely locked up. It did the same thing yesterday when installing Windows Updates and went through a phase where every reboot and option lead to a 0xA blue screen. Then finally it decided to let me into start up repair once, and worked ever since.

I went to bed woke up this morning, turned it on and it booted up fine. Except for the lock up while playing a game. Since then it went back into its phase of STOP ERROR on every boot up option, once again mostly 0xA and it threw in the old 0x124 I havent seen in a while. Along with a couple 0x3D's. Would the random reboots earlier in the week + system lock ups = CPU? Or could it be any of the Trio of Trouble as you put it?

I've read up on Ultimate Boot CD and it seems it has some bootable CPU test on it as well. I also found that Intel has a bootable Intel(R) Processor Diagnostic tool somewhere around. They only list the .exe on their site and say to contact your local Intel tech support for a bootable copy... which... seems really dumb, lol.

Just wondering if this supports your conclusion and if those tools would help pinpoint the problem to the CPU or if you think it could still be the other 2 of the trio.

 

[diamondwolf]

Disregard. This post was related to Prime 95 testing through Ultimate Boot CD but I forgot to check and see how to run/what is reported after the other 2/3 test.

 

[diamondwolf]

I will add this in incase anyone else comes across the issue. As I hate topics like this that dont have what fixed the issue at the end, and the OP never follows up.

So after taking Vir's advice, I booted my computer a few times and let it blue screen. I always got the PROCESSOR CACHE error towards the bottom, and it was always bank 0 proc 2, whatever that means. I ordered the same CPU model off of eBay, and got it later than I had hoped last week.

Wednesday, I swapped the new CPU I had gotten, with the one in the laptop. Replaced the thermal compound. Ever since then it has not BSOD'ed for at all. Reinstalled Windows just to make sure there would be no drivers in the background messing it up. Nice clean install, got through all the updates, still without a STOP ERROR code. Since then from early that evening Wednesday, all the way till now (Monday), no STOP ERRORs.

So it turns out it was a bad CPU. It sucks, but the issue is resolved, and I'm happy. Thanks for all of your help Vir, along with answering my questions in PM's. Take care man.

 

[Vir Gnarus]

Thanks a mil on the update man. Once I laid eyes on some of your crashdumps, especially with the odd register behavior and the WHEA errors reporting L0 cache failures, I had to venture to guess your CPU was prime suspect here. Of course, motherboard - and especially PSU - issues can manifest these as well, but it was very consistently CPU-related, so I had a feeling yer CPU bugged out.

Glad to hear you went ahead and swapped the CPU and that was all you needed done. Have fun with yer laptop, mate!