1.    07 May 2017 #1
    Join Date : Feb 2017
    Posts : 22
    Windows 10 64 bit

    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
      My ComputerSystem Spec
  2.    08 May 2017 #2
    Join Date : Jan 2016
    Posts : 643
    windows 10 Pro

    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
    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
    Start with updating these drivers/devices to the latest driver versions.
      My ComputerSystem Spec
  3.    08 May 2017 #3
    Join Date : Feb 2017
    Posts : 22
    Windows 10 64 bit
    Thread Starter

    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?

    Quote Originally Posted by lifetec View Post
    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
    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
    Start with updating these drivers/devices to the latest driver versions.
      My ComputerSystem Spec
  4.    09 May 2017 #4
    Join Date : Jan 2016
    Posts : 643
    windows 10 Pro

    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 ).
      My ComputerSystem Spec
  5.    09 May 2017 #5
    Join Date : Feb 2017
    Posts : 22
    Windows 10 64 bit
    Thread Starter

    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.
    Quote Originally Posted by lifetec View Post
    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 ).
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
BSOD kmode exception not handled boot loop
Hi, today I got a very ridiculous problem with my computer. First of all, CPU, RAM & mainboard are new since january (System Infos in my profile) I was away for a few minutes after watching youtube videos and I saw that my pc was in a boot loop...
BSOD Crashes and Debugging
BSOD Kmode exception not handled
Hello everyone! I bought a new pc and when I did fresh install of Windows 10 on SSD, as soon as Windows loaded (after welcome screen) I got these errors: OneDriverSetup.exe cannot start WerFault.exe dllhost.exe and than BSOD with error...
BSOD Crashes and Debugging
BSOD KMODE Exception Not Handled Netio.Sys
Hello, and thanks very much for providing this service. I've been getting intermittent Netio.sys BSODs, typically while browsing using Chrome, or doing nothing. I was having a bunch of them in September, but they seemed to go away for a time. Now...
BSOD Crashes and Debugging
BSOD - Kmode Exception Not Handled - Netio.sys
Hello, I recently have been having a few BSOD's and they all point to netio.sys. Unfortunately it happens very random with me doing different tasks. I'm unable to duplicate it. I've have run a System File checker on it and that's come back...
BSOD Crashes and Debugging
BSOD kmode exception not handled (and maybe resulting network issue)
Hi all, I was advised to make my own thread for this issue, so here goes: My father is also having BSOD's with this same error message KMODE exception not handled. I built him a pc a few years back based on an Asrock Z77 Pro4-M, and it has run...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 18:03.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums