Windows 10 Graphics issues after upgrade to Windows 10: SYSTEM_SERVICE_EXCEPTION sgfxk64.sys

JakubKrol

New Member
Joined
Apr 14, 2016
Messages
11
Hi,

2 days ago I upgraded to Windows 10 my HP ProBook 450 G0.

After I realized my graphic drivers are not working properly I tried to update them to the lastest listed at drivers download section for my model.

After this I had BSODs and couldn't even see login screen. I removed installed update in safe mode.

So right now I'm using some default driver I guess.

In the devices manager on Intel(R) HD Graphics 4000 I have something like (manual translation) "Windows has stopped this device because of raported troubles. (Code 43)".

I cannot use HDMI & internal display. To use HDMI I need to restart my PC. After using HDMI I cannot use internal display. A lot of issues, because of this driver...

I really need this, as I'm teacher and I', using both internal display & HDMI for presentations...



Any solutions? Any logs I can get to help you help me Link Removed?





This is log from dump:

Code: 
==================================================
Dump File         : 041316-12640-01.dmp
Crash Time        : 2016-04-13 20:24:32
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff801`d6cc83ab
Parameter 3       : ffffd000`9e42a500
Parameter 4       : 00000000`00000000
Caused By Driver  : sgfxk64.sys
Caused By Address : sgfxk64.sys+83ab
File Description  : SMSC Graphics Adapter WDDM Kernel Mode Driver
Product Name      : SMSC Graphics Adapter WDDM Software
Company           : SMSC
File Version      : 5.1.0.0
Processor         : x64
Crash Address     : ntoskrnl.exe+142760
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\041316-12640-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 10586
Dump File Size    : 194 945
Dump File Time    : 2016-04-13 20:24:08
==================================================


and info:

Code: 
ntoskrnl.exe    ntoskrnl.exe+14d2e9    fffff803`d9083000    fffff803`d984f000    0x007cc000    0x56cd4410    2016-02-24 07:48:00    Microsoft® Windows® Operating System    NT Kernel & System    10.0.10586.212 (th2_release_sec.160328-1908)    Microsoft Corporation    C:\WINDOWS\system32\ntoskrnl.exe   
sgfxk64.sys    sgfxk64.sys+83ab    fffff801`d6cc0000    fffff801`d6ce8000    0x00028000    0x50ef0f27    2013-01-10 20:57:43    SMSC Graphics Adapter WDDM Software    SMSC Graphics Adapter WDDM Kernel Mode Driver    5.1.0.0    SMSC    C:\WINDOWS\system32\drivers\sgfxk64.sys   
hal.dll        fffff803`d9010000    fffff803`d9083000    0x00073000    0x5632d17a    2015-10-30 04:10:02    Microsoft® Windows® Operating System    Hardware Abstraction Layer DLL    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\hal.dll   
kdcom.dll        fffff803`d789f000    fffff803`d78aa000    0x0000b000    0x5632d938    2015-10-30 04:43:04    Microsoft® Windows® Operating System    Serial Kernel Debugger    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\kdcom.dll   
mcupdate.dll        fffff801`d4850000    fffff801`d48de000    0x0008e000    0x5632d912    2015-10-30 04:42:26                       
werkernel.sys        fffff801`d48e0000    fffff801`d48f0000    0x00010000    0x5632d90b    2015-10-30 04:42:19    Microsoft® Windows® Operating System    Windows Error Reporting Kernel Driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\werkernel.sys   
CLFS.SYS        fffff801`d48f0000    fffff801`d4955000    0x00065000    0x5632d172    2015-10-30 04:09:54    Microsoft® Windows® Operating System    Common Log File System Driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\CLFS.SYS   
tm.sys        fffff801`d4960000    fffff801`d4985000    0x00025000    0x5632d166    2015-10-30 04:09:42    Microsoft® Windows® Operating System    Kernel Transaction Manager Driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\tm.sys   
PSHED.dll        fffff801`d4990000    fffff801`d49a7000    0x00017000    0x5632d16c    2015-10-30 04:09:48    System operacyjny Microsoft® Windows®    Sterownik błędów sprzętowych charakterystycznych dla platformy    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\PSHED.dll   
BOOTVID.dll        fffff801`d49b0000    fffff801`d49bb000    0x0000b000    0x5632d165    2015-10-30 04:09:41    Microsoft® Windows® Operating System    VGA Boot Driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\BOOTVID.dll   
cmimcext.sys        fffff801`d49c0000    fffff801`d49ce000    0x0000e000    0x5632d166    2015-10-30 04:09:42    Microsoft® Windows® Operating System    Kernel Configuration Manager Initial Configuration Extension Host Export Driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\cmimcext.sys   
ntosext.sys        fffff801`d49d0000    fffff801`d49dc000    0x0000c000    0x5632d165    2015-10-30 04:09:41    Microsoft® Windows® Operating System    NTOS extension host driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\ntosext.sys   
CI.dll        fffff801`d4200000    fffff801`d4299000    0x00099000    0x5632d767    2015-10-30 04:35:19    Microsoft® Windows® Operating System    Code Integrity Module    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\CI.dll   
msrpc.sys        fffff801`d42a0000    fffff801`d42fc000    0x0005c000    0x5632d746    2015-10-30 04:34:46    Microsoft® Windows® Operating System    Kernel Remote Procedure Call Provider    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\msrpc.sys   
FLTMGR.SYS        fffff801`d4300000    fffff801`d4362000    0x00062000    0x5632d176    2015-10-30 04:09:58    System operacyjny Microsoft® Windows®    Menedżer filtrów systemu plików firmy Microsoft    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\FLTMGR.SYS   
ksecdd.sys        fffff801`d4370000    fffff801`d4395000    0x00025000    0x5632d833    2015-10-30 04:38:43    Microsoft® Windows® Operating System    Kernel Security Support Provider Interface    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\ksecdd.sys   
clipsp.sys        fffff801`d43a0000    fffff801`d4445000    0x000a5000    0x5632d7db    2015-10-30 04:37:15    Microsoft® Windows® Operating System    CLIP Service    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\clipsp.sys   
Wdf01000.sys        fffff801`d4450000    fffff801`d4515000    0x000c5000    0x5632d4db    2015-10-30 04:24:27    System operacyjny Microsoft® Windows®    Aparat wykonawczy struktury sterowników trybu jądra    1.17.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\Wdf01000.sys   
WDFLDR.SYS        fffff801`d4520000    fffff801`d4533000    0x00013000    0x5632d168    2015-10-30 04:09:44    Microsoft® Windows® Operating System    Kernel Mode Driver Framework Loader    1.17.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\WDFLDR.SYS   
acpiex.sys        fffff801`d4540000    fffff801`d4563000    0x00023000    0x5632d854    2015-10-30 04:39:16    Microsoft® Windows® Operating System    ACPIEx Driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\acpiex.sys   
WppRecorder.sys        fffff801`d4570000    fffff801`d457d000    0x0000d000    0x5632d166    2015-10-30 04:09:42    Microsoft® Windows® Operating System    WPP Trace Recorder    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\WppRecorder.sys   
cng.sys        fffff801`d4580000    fffff801`d4618000    0x00098000    0x56a84d7c    2016-01-27 06:54:20    Microsoft® Windows® Operating System    Kernel Cryptography, Next Generation    10.0.10586.212 (th2_release_sec.160328-1908)    Microsoft Corporation    C:\WINDOWS\system32\drivers\cng.sys   
ACPI.sys        fffff801`d4620000    fffff801`d46b0000    0x00090000    0x56cbf9c9    2016-02-23 08:18:49    System operacyjny Microsoft® Windows®    Sterownik ACPI dla systemu NT    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\ACPI.sys   
WMILIB.SYS        fffff801`d46b0000    fffff801`d46bc000    0x0000c000    0x5632d166    2015-10-30 04:09:42    Microsoft® Windows® Operating System    WMILIB WMI support library Dll    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\WMILIB.SYS   
WindowsTrustedRT.sys        fffff801`d46c0000    fffff801`d46df000    0x0001f000    0x5632d826    2015-10-30 04:38:30    Microsoft® Windows® Operating System    Windows Trusted Runtime Interface Driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\WindowsTrustedRT.sys   
WindowsTrustedRTProxy.sys        fffff801`d46e0000    fffff801`d46eb000    0x0000b000    0x5632d825    2015-10-30 04:38:29    Microsoft® Windows® Operating System    Windows Trusted Runtime Service Proxy Driver    10.0.10586.0 (th2_release.151029-1700)    Microsoft Corporation    C:\WINDOWS\system32\drivers\WindowsTrustedRTProxy.

Regards,
JK.
 
Solution
Hi,

Thank you guys, YOU ROCK!
I did what I wrote here, driver installed without BSOD and graphics are working now Both displays work, changing them dynamically, switching, GPU acceleration etc.
So it was probably one of old drivers from some strange stuff and/or I needed also chipset update. Anyway, one more plus - I finally removed old stuff from my PC.

PS. Can I accept two answers ?

Thank you, regards,
JK.
Sort by date Sort by votes

Hi,
in order to help you best we really need to see your actual dump files. If you read the following thread and then post the results we can at least then read the dump files:
How to ask for help with a BSOD problem
 
Upvote 0 Downvote
Hi,

@1st Line Support - Ok, thanks, Il'' try this one.
@kemical - Thank you. Here are all the data uploaded. However it looks like it didn't copy mini-dump (I used CCleaner after BSOD, but I can just install drivers again and get new dump). Do you want me to send it also?

Regards,
JK.
 

Attachments

Upvote 0 Downvote

Newest intel driver I could find is Link Removed. Try using those and see how it goes.
 
Upvote 0 Downvote
Hi,

Thanks @nmsuk, but as far as I know, HP has a little bit different drivers.
Anyways I tried this one previously (right now I have it installed) and no BSOD, but it looks it does not work at all. I even cannot open Control Panel (it simply won't start).

Regards,
JK.
 
Upvote 0 Downvote
Hi,

@nmsuk I tried it, but the result is:
> no BSOD, but it looks it does not work at all. I even cannot open Control Panel (it simply won't start).
I also tried Intel Driver Update Utity with the same results.
I'm thinking about Code 43 on this device. How can I check exact error?

Regards,
JK.
 
Upvote 0 Downvote

Hi,
as you correctly surmised there is no dump file present. In the meantime try uninstalling your Intel driver using the DDU. The display driver uninstaller will remove any old bits of driver left behind from previous installs and leaves it clean ready for the new driver. It's best used in safe mode:
Display Driver Uninstaller (DDU) V15.7.5.5 Released. - Wagnardmobile Forum

Once you have the driver removed use the driver found on your systems support page. As your already aware laptop drivers are mainly supplied by the manufacturer so try the versions on the webpage first:
Link Removed
 
Upvote 0 Downvote
That report an error 0xC0000005 which is a program trying to run at the wrong privileged level.
I would suggest you go to Start Button -> Control Panel -> Device Manager, find your Display Adapter driver and right mouse on it and select un-install, when prompted Tick the delete driver option. Re-install the driver fresh with the HP Support Assistant
 
Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff801cf2d83ab, ffffd0005e854500, 0}

*** WARNING: Unable to verify timestamp for sgfxk64.sys
*** ERROR: Module load completed but symbols could not be loaded for sgfxk64.sys
Probably caused by : sgfxk64.sys ( sgfxk64+83ab )

Followup: MachineOwner
Hi,
bugcheck 3B can be caused by a faulty system service or gpu drivers passing bad data. The exception code c0000005 means data held in the memory couldn't be read.

I'm a little puzzled by this driver:
sgfxk64.sys Thu Jan 10 18:57:43 2013: SMSC Graphics Adapter driver

As you'll note it's part of the probably cause and i wonder where you got it from. I cannot seem to find it on your support page as the only gpu drivers present are Intel and AMD, so where is it coming from?

If it's coming from when you use the HP assistant then uninstall it. Try not to use these automatic driver finding apps as invariably they get it wrong.

I also notice your running Avast AV. This is known on occasion to cause the odd issue and we usually ask if you would remove it and just use the onboard Defender (you can always re-install it later) as it's ultra stable.

Post any new dump files.
 
Upvote 0 Downvote
Thanks Rich, I didn't think it looked like anything connected to the driver support page. Perhaps the OP has an external gpu solution too?
 
Upvote 0 Downvote
Hi,

I don't have any external GPU I guess it would be important.
I think this comes from default Windows graphics driver.
Anyway, I'll try solution with avast!.

If it won't work - I'm going back to Win 7. A little bit sad, Win 10 is really ergonomic.

Thank you for your time and your help,
regards,
JK.
 
Upvote 0 Downvote
You must log in or register to reply here.