Solved Troubleshoot ntoskrnl.exe, hal.dll, win32k!EngUpdateDevice

DarthKane · Dec 22, 2014

I have a custom built PC. AMD FX 8350, GTX 760, 8GB RAM, 2 SSD's.

I just switched my rig back from Linux, I wiped and reinstalled everything so its basically a new machine.

My first installed last year was Windows 8, then upgraded to 8.1. I wanted to avoid the BS MS license game so I started at 8 and then Windows Updated to 8.1. OS is activated.

My machine was really unstable and would reboot if I tired to play a game, and would reboot randomly over night or when the machine was not used.

I updated my BIOS, GPU, and used Slimdrivers to update the rest of my system.

My PC was good for about two days, but had another BSOD last night, while I was sleeping.

I don't think I have any hardware problems...

View attachment 55556

DarthKane · Dec 22, 2014

BSODed a few more times today. WhoCrashed says the crash occurs at a future date and time. My time zone setting is set to eastern and the 22nd not the 23rd.

On Tue 12/23/2014 3:11:16 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\122214-4562-01.dmp

This was probably caused by the following module: hal.dll (hal+0x37213)

Bugcheck code: 0x124 (0x0, 0xFFFFE000A2F3A028, 0xB0800000, 0x40151) Error: WHEA_UNCORRECTABLE_ERROR file path: C:\WINDOWS\system32\hal.dll

usasma · Dec 24, 2014

Sorry for the delay in responding. There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

There are 3 memory dumps, each with a different BSOD error code. The differing error codes are sometimes symptomatic of a lower level problem within the system (although I usually wait for 5 or more BSOD's before making this statement).
They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case. Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Please get a head start on the hardware diagnostics - they are located here: Hardware Diagnostics

Other than that, please be sure that you have all updates from Windows Update and from the Asus website for your motherboard.
Should you pass all the hardware diagnostics, let us know - and while waiting for a reply, please run Driver Verifier according to these instructions: Driver Verifier Settings

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Mon Dec 22 04:30:12.078 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\122214-4796-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]0 days 7:00:52.758[/B]
Probably caused by :[B]win32k.sys ( win32k!EngUpdateDeviceSurface+3977f )[/B]
BugCheck [B]3B, {c0000005, fffff801382f95e4, ffffd0019369eef0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801382f95e4, Address of the instruction which caused the bugcheck
Arg3: ffffd0019369eef0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  FlashPlayerPlu
FAILURE_BUCKET_ID: [B]0x3B_win32k!EngUpdateDeviceSurface[/B]
  BIOS Version                  2501
  BIOS Release Date             04/07/2014
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 20 17:28:07.398 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\122014-4765-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]0 days 1:13:10.083[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, ffffe000f2cbf028, f0800000, 40151}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000f2cbf028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  Loadout.exe
FAILURE_BUCKET_ID: [B]0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  1903
  BIOS Release Date             07/11/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 20 07:56:19.880 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\122014-4562-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17328.amd64fre.winblue_r3.140827-1500
System Uptime:[B]0 days 8:52:43.567[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]dxgkrnl.sys ( dxgkrnl!DpiFdoDpcForIsr+31 )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff8028e3167e2, 0, ffffffffffffffff}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8028e3167e2, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1E_c0000005_R_dxgkrnl!DpiFdoDpcForIsr[/B]
  BIOS Version                  1903
  BIOS Release Date             07/11/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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 Dec 22 04:30:12.078 2014 (UTC - 5:00)**************************
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
xusb22.sys                  Tue Mar 18 04:18:41 2014 (53280161)
RTKVHD64.sys                Tue May  6 09:14:37 2014 (5368E03D)
Rt630x64.sys                Tue Jul 15 22:56:14 2014 (53C5E9CE)
nvhda64v.sys                Mon Jul 21 10:17:53 2014 (53CD2111)
nvlddmkm.sys                Wed Nov 12 15:51:31 2014 (5463C853)
nvvad64v.sys                Thu Nov 20 10:33:54 2014 (546E09E2)
NvStreamKms.sys             Sat Nov 22 02:46:45 2014 (54703F65)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 20 17:28:07.398 2014 (UTC - 5:00)**************************
au630x64.sys                Thu Mar 14 05:44:07 2013 (51419BE7)
RTKVHD64.sys                Thu Sep 26 07:56:08 2013 (524420D8)
nvhda64v.sys                Thu Nov 28 08:38:09 2013 (52974741)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 20 07:56:19.880 2014 (UTC - 5:00)**************************
nvlddmkm.sys                Wed Jul  2 13:42:02 2014 (53B4446A)
[/font]

DarthKane · Dec 24, 2014

THANKS for getting back to me usasma. I had a couple more BSOD's that I think were caused by this: hal.dll+37213 ntoskrnl.exe+150aa0

You said, "symptomatic of a lower level problem within the system" lower level meaning kernel level aka hosed/failed OS aka Windows ME/Vista?

I have since wiped my C drive and installed WINDEX 7. Hoping for some dumb reason that this will fix my problem, but IDK...

While rebuilding my OS I noticed NVidia released an update on Dec 23rd. The old drivers I was using was from November.

They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
Maybe, but I doubt it. I have been inside my case removing hard drives, but I was careful, and know what I am doing I am A+ certified.
- BIOS issues (check for updates at the motherboard manufacturer's website)
I updated from 1900 to 2600 the other day, I was pretty far behind.
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
No overclocking, plenty of fans and temps are normal, plus the side of my case is off.
- dirt/dust/hair/fur/crud inside the case. Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
Clean as a whistle
- missing Windows Updates
I have ran updates a few times.
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
NVidia thanks for nothing... No pirated softwares.
- low-level driver problems
- or even malware
Nope I installed Windows 8 last weekend and am now on Windows 7.

Updated DX DIAGG View attachment 55644

usasma · Dec 24, 2014

Lower level is a somewhat imprecise term. BSOD's are all kernel level, but the different drivers working within the kernel space operate at different "levels". Things like storage controller drivers, chipset drivers, antivirus drivers, etc generally operate at a lower level on the system. In short, the closer a driver gets to "lower level" then the more it will resemble a hardware problem should it fail/become corrupted.

Broken hardware can be a simple as a bit of dust in the plug for one of the devices. Or it can be as complicated as a broken part inside of another component that is only used under limited circumstances (so it won't necessarily crash when using/testing that component)

Lot's of Windows Updates failures in the WER section of the MSINFO32 report. If the problems continue, please post over in the Windows Updates & Activation - Windows 7 Help Forums for further expert assistance with this issue.
This must be fixed!!!

Have you had any BSOD's with Win7 installed? If so, please zip up the contents of C:\Windows\Minidump and upload it with your next post (you may have to copy it to your Desktop in order to zip it up).

DarthKane · Dec 24, 2014

I think the failed updates were caused by me, I canceled them. But I have since done updates.

No BSOD's since Windows 7. I have also done some stress testing with Prime95 and Furmmark, no issues there. I did some other normal computer activities and so far so good.

While open a new tread if I have more problems.

usasma · Dec 25, 2014

Thanks for letting us know!
Good Luck!

Solved Troubleshoot ntoskrnl.exe, hal.dll, win32k!EngUpdateDevice

DarthKane

New Member

My Computer

System One

DarthKane

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

DarthKane

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

DarthKane

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One