Windows 10: Weird desktop display issues, KMODE EXCEPTION NOT HANDLED BSOD

I included some screenshots and my BSOD collection files that you need here to help me with this issue. Over the past month my desktop has been turning to a black background and my menus are not showing up properly. I am beginning to think my new RX 480 is to blame but this rig is relatively new so it's hard to pinpoint exactly what new hardware change could have caused this. As you can see on Synctoy, my syncs are not showing up. Sometimes when I right click the words on the right click menu don't pop up either on different programs. And on the desktop, when I highlighted these icons, they turn to a black background. I hope this is a software issue and not a hardware issue. Attachment 133971Attachment 133972

Attachment 133970

:)

 

Windows 10 BSOD on startup (SYSTEM EXCEPTION/KMODE EXCEPTION)

You are not back to square one. When you put out your first post, kmode exception was for ntfs.sys and ntoskrnl.exe. Now it is for netio.sys. So we should think why kmode exception has changed form.

 

Windows 10 BSOD on startup (SYSTEM EXCEPTION/KMODE EXCEPTION)

Sad to say that after leaving the house for a few hours and switching the computer on I got another BSOD (KMODE EXCEPTION pointing to NETIO.SYS). Every start up program was disabled so looks like I'm back to square one.

 

Analyzing your latest dumpfiles they point to your Razer devices an your intel networkcard I219-V
Code: BugCheck 1E, {ffffffffc0000005, fffff8012527e0d4, 0, ffffffffffffffff} *** WARNING: Unable to verify timestamp for rzpnk.sys *** ERROR: Module load completed but symbols could not be loaded for rzpnk.sys Probably caused by : memory_corruption BugCheck 1E, {ffffffffc0000005, fffff8019c01d0d4, 0, ffffffffffffffff} *** WARNING: Unable to verify timestamp for rzpnk.sys *** ERROR: Module load completed but symbols could not be loaded for rzpnk.sys *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption[/quote] Code: BugCheck 9F, {3, ffffe68d9e4e7060, ffffb10085a5c8e0, ffffe68dabb3f560} Probably caused by : pci.sys Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffe68d9e4e7060, Physical Device Object of the stack Arg3: ffffb10085a5c8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe68dabb3f560, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5850cc6b MODULE_NAME: pci FAULTING_MODULE: fffff800807a0000 pci CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre DPC_STACK_BASE: FFFFB10085A64FB0 STACK_TEXT: ffffb100`85a5c8a8 fffff801`a9c6cd8b : 00000000`0000009f 00000000`00000003 ffffe68d`9e4e7060 ffffb100`85a5c8e0 : nt!KeBugCheckEx ffffb100`85a5c8b0 fffff801`a9c6cc9e : ffffe68d`a8621010 00000000`00000001 00000000`00000002 ffffe68d`a8621088 : nt!PopIrpWatchdogBugcheck+0xeb ffffb100`85a5c910 fffff801`a9aac9f0 : ffffe68d`a8621048 ffffe68d`a8621048 00000000`00140001 00000000`00000002 : nt!PopIrpWatchdog+0x22 ffffb100`85a5c960 fffff801`a9bc784a : 00000000`00000000 ffffb100`8558b180 ffffb100`85597bc0 ffffe68d`a680a080 : nt!KiRetireDpcList+0x440 ffffb100`85a5cbe0 00000000`00000000 : ffffb100`85a5d000 ffffb100`85a56000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: 10.0.14393.594 FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_e1i63x64_IMAGE_pci.sys BUCKET_ID: 0x9F_3_POWER_DOWN_e1i63x64_IMAGE_pci.sys[/quote] Start with updating these drivers/devices to the latest driver versions.

 

Thanks for getting back to me on this. I opened device manager and tried to update and it said all the things are the latest version. Is there any more specific information it provided?

Code: BugCheck 9F, {3, ffffe68d9e4e7060, ffffb10085a5c8e0, ffffe68dabb3f560} Probably caused by : pci.sys Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffe68d9e4e7060, Physical Device Object of the stack Arg3: ffffb10085a5c8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe68dabb3f560, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5850cc6b MODULE_NAME: pci FAULTING_MODULE: fffff800807a0000 pci CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre DPC_STACK_BASE: FFFFB10085A64FB0 STACK_TEXT: ffffb100`85a5c8a8 fffff801`a9c6cd8b : 00000000`0000009f 00000000`00000003 ffffe68d`9e4e7060 ffffb100`85a5c8e0 : nt!KeBugCheckEx ffffb100`85a5c8b0 fffff801`a9c6cc9e : ffffe68d`a8621010 00000000`00000001 00000000`00000002 ffffe68d`a8621088 : nt!PopIrpWatchdogBugcheck+0xeb ffffb100`85a5c910 fffff801`a9aac9f0 : ffffe68d`a8621048 ffffe68d`a8621048 00000000`00140001 00000000`00000002 : nt!PopIrpWatchdog+0x22 ffffb100`85a5c960 fffff801`a9bc784a : 00000000`00000000 ffffb100`8558b180 ffffb100`85597bc0 ffffe68d`a680a080 : nt!KiRetireDpcList+0x440 ffffb100`85a5cbe0 00000000`00000000 : ffffb100`85a5d000 ffffb100`85a56000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: 10.0.14393.594 FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_e1i63x64_IMAGE_pci.sys BUCKET_ID: 0x9F_3_POWER_DOWN_e1i63x64_IMAGE_pci.sys[/quote] Start with updating these drivers/devices to the latest driver versions.[/quote]

 

Look on the supportpages of Razer and the Killer network if they have newer drivers or info about compatibility with the new Creator Update. (Google or Bing it ).

 

Thanks for the info. Many of the display issues seemed to work out when I updated Radeon drivers. And I haven't had a BSOD yet so I'm hoping that fixed things. If not I'll probably come back to this post and look at the sites you guys mentioned.