Solved Bluescreen WHEA_UNCORRECTABLE_ERROR hal.dll+37203 0x000001

Mattriz · Apr 30, 2014

I have gotten this bluescreen WHEA_UNCORRECTABLE_ERROR (Windows 8.1) 2-3 times now the last 4-5 days.

My cpu temp (40 idle) and gpu temps are fine (gpu may be little high idle, 55 Celsius, but should not be a problem)

The bluescreens happened while surfing the web and watching a youtube clip so my load temps are not any problem.

CPU overclock is stable at 4.0 Ghz have ran this for quite a while without any problem, GPU is running on stock clocks. (running prime95 atm to be 100% sure, but this should not be a problem when i have had it at 4.0ghz for 1 month)

I ran memtest for 11.5 (4+4gb) hours without any errors, then when i sat in one of my old sticks with the new ram (4+4+2gb) i ran memtest for 6.5 hours without any errors.

This problem started after i switched ram sticks, but i now changed them back to my old ram, but i still got the bluescreen. May i have damaged my motherboard while changing the ram sticks?

specs:

Bluescreen file:

usasma · Apr 30, 2014

Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html Please use Option 1 as it provides Event Viewer logs.

Long ago I learned that the first troubleshooting step in an overclocked system is to remove the overclock. This is for 2 reasons:
1) in case the overclock is at fault (and it hasn't damaged any hardware yet) - this will fix the problem.
2) the tests we use for troubleshooting are based on a standard system operating normally - so an overclocked system won't necessarily give correct results because of the stress on the components. This is why I recommend stopping the overclock completely while troubleshooting.

Also, I found that overclocks will degrade over time - the system just won't be able to hold a high overclock forever. The system will get older and it's tolerance for this sort of stress will lessen - resulting in more errors.

Finally, hardware errors aren't necessarily just hardware, they can be:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS problems (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Some systems will "auto" overclock - and I'm seeing more and more of this in Win8 systems.

What were the results of Prime95?
How many passes did you run MemTest for? IMO opinion you need a minimum of 3 passes in order to be sure.

It's possible that you may have damaged the mobo while changing sticks - but that's a lot less likely than the problem just remaining the same (and so, the RAM is probably not directly related to it). But remember, this is all just guesswork until we find a cause.

Please remove the Corsair Link software as it's known to cause BSOD's on some Windows systems. It's driver is CorsairLINK_HardwareMonitor.sys

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install them immediately!

Please remove HotSpotShield as it is known to cause BSOD's on some Windows systems. It's driver is hssdrv6.sys

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
Logitech Gamepanel Virtual HID Device Driver
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys

LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
Logitech Keyboard
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys

Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.

If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Hardware Diagnostics. Let us know the results and we can move on from there.

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Mon Apr 28 20:13:37.444 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\042914-26656-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 11:09:38.064[/B]
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, ffffe0017fe03028, be000000, 800400}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0017fe03028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x124_GenuineIntel__UNKNOWN[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: [B]4000[/B]
 
Processor may be overclocked!
Expected Frequency:   2800
Actual Frequency:     4000
Overclock Ratio:      [color=red]1.42857[/color]
 
  BIOS Version                  0803   
  BIOS Release Date             08/06/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Mon Apr 28 20:13:37.444 2014 (UTC - 4:00)**************************
[COLOR=RED][B]CorsairLINK_HardwareMonitor.sys   Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
[COLOR=RED][B]LGVirHid.sys                      Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]LGBusEnum.sys                     Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
mv91cons.sys                      Wed Jun  6 06:26:38 2012 (4FCF305E)
mvxxmm.sys                        Wed Jun  6 23:09:05 2012 (4FD01B51)
mvs91xx.sys                       Wed Jun  6 23:09:20 2012 (4FD01B60)
[COLOR=RED][B]ASACPI.sys                        Thu Nov  1 21:54:34 2012 (509327DA)[/B][/COLOR]
speedfan.sys                      Sat Dec 29 15:59:35 2012 (50DF59B7)
[COLOR=RED][B]RTCore64.sys                      Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
netr28ux.sys                      Thu Apr 25 22:33:43 2013 (5179E787)
ScpVBus.sys                       Sun May  5 17:31:26 2013 (5186CFAE)
SamsungRapidDiskFltr.sys          Mon Jul 29 14:55:38 2013 (51F6BAAA)
SamsungRapidFSFltr.sys            Mon Jul 29 14:55:39 2013 (51F6BAAB)
intelppm.sys                      Thu Aug 22 04:46:35 2013 (5215CFEB)
RTKVHD64.sys                      Tue Nov  5 06:39:41 2013 (5278D8FD)
AMDACPKSL.SYS                     Tue Mar 11 19:49:44 2014 (531FA118)
AtihdWB6.sys                      Tue Mar 11 19:50:02 2014 (531FA12A)
Wof.sys                           Thu Mar 13 04:27:29 2014 (53216BF1)
[COLOR=RED][B]hssdrv6.sys                       Mon Mar 24 16:09:36 2014 (53309100)[/B][/COLOR]
taphss6.sys                       Mon Mar 24 16:11:58 2014 (5330918E)
atikmpag.sys                      Thu Apr 17 21:07:07 2014 (53507ABB)
amdacpksd.sys                     Thu Apr 17 21:54:17 2014 (535085C9)
atikmdag.sys                      Thu Apr 17 22:13:16 2014 (53508A3C)
[/font]

Mattriz · Apr 30, 2014

Thank you very much usasma for a such long and helpful post

Here is the SF Diagnostic Tool zip folder

i removed the overclock and its back to stock 2.8Ghz

i installed driver scanner 2014 and updated all my drivers and i uninstalled Corsair Link and HotSpotShield, but i use msi afterburner for the gpu fan speed controller, do you recommend any other gpu fan speed controller that i can use instead?

Prime95 ran for 2 hours then a GPU related bluescreen happened (not the same as this problem but in the same area). I started a thread in the windows 7 forum (last post page 1) before i knew about this forum so its some info there.

i ran memtest for 11.5 (4+4gb) hours without any errors, then when i sat in one of my old sticks with the new ram (4+4+2gb) i ran memtest for 6.5 hours without any errors. I dont know how many passes this is. I ran a windwos based program, not memtest86. http://hcidesign.com/memtest/

Im not sure if i updated LGVirHid.sys, LGBusEnum.sys and ASACPI.sys when installing Logitech Gaming Software and asus usb-n66 software. Please tell if there is any more logs i need to post

usasma · May 1, 2014

I haven't overclocked in many, many years so I'm not familiar with current programs like this.
I have, in the past, used SpeedFan to modify fan speeds.
Otherwise, I'd check with other overclockers.

Don't worry about the ASACPI.sys driver at this point - it's usually OK in that version (it's earlier versions that I worry about).
The Logitech software isn't very critical either - we'll just see what shows up if you get further BSOD's

From the uploaded reports:

You have a ASUS USB-N66 Dual Band N Network Adapter:

I do not recommend using wireless USB network devices. Especially in Win8/8.1 systems.
These wireless USB devices have many issues with Win7 and later - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win8/8.1 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

You have 3 hard drives. What is the make/model/wattage and age of your Power Supply?

There are problems with this device:

TSSTcorp CDDVDW SH-S223C SCSI CdRom Device SCSI\CDROM&VEN_TSSTCORP&PROD_CDDVDW_SH-S223C\5&22BEDE4E&0&000100 Failure using the VxD loader.

Please uninstall this device, then reboot and see if the error comes back. If so, it may be an issue with the drive itself. Please let us know as the next step would be removing the drive to see if it helps.

There are very few entries in the WER section of MSINFO32.
All the Event Viewer/WER reports only show entries from 30 April 2014
Did you have error reporting turned off since you installed the OS?

What we do now is wait and see if there's further BSOD's...........

Mattriz · May 1, 2014

Not sure if i have the win 8.1 drivers installed on ASUS USB-N66. At the moment i have to use ASUS USB-N66 since the router is to floors up and i cant stretch a 20-30m internet cable around the house.

Im not using the TSSTcorp CDDVDW (CD-ROM) so i plugged it out, but i havnt had any issuse with this before. Is there any driver i shall uninstall here?

I have 3 hard drives: Samsung 840 pro 128GB, Western Digital Caviar GreenPower 1TB and WD Elements 2 TB USB 2.0 Desktop External Hard Drive

i have this PSU: Corsair TX 750w. It was bought july 2010

I dont think i have disabled error reporting?
View attachment 42554
View attachment 42555

usasma · May 2, 2014

It appears that your N66 drivers are more current than the drivers available on the Asus website.
Asus doesn't offer Win8.1 drivers for this device.
Where did you get your current drivers from?

There's no further issues with the CD/DVD drive that you've unplugged. Please leave it unplugged until the system has stabilized.

As for the absence of error reports, I'm a bit confused as I expect to see some errors. My concern is that there weren't any errors prior to 30 April - but now there are. I wonder what caused the error reporting to start again? This isn't something that we need to fix (as it's fixed itself), but I'm generally suspicious of any unexplained/unknown changes to a system.

Regardless, there seems to have been no further BSOD's - so that's a good thing!

Mattriz · May 2, 2014

I used driver scanner 2014 to install the N66 drivers.

Can i overclock my cpu back now? or should i wait a couple of more days to see if there is any mores bluescreens?

usasma · May 3, 2014

I'd wait a couple of days just to be sure.
Good luck!

Mattriz · May 3, 2014

Will do

Thank you for all your help usasma!

Solved Bluescreen WHEA_UNCORRECTABLE_ERROR hal.dll+37203 0x000001

Mattriz

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

Mattriz

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

Mattriz

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

Mattriz

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

Mattriz

New Member

My Computer

System One