BSOD Distorted screen


  1. Posts : 1
    Windows7 64 bit
       #1

    BSOD Distorted screen


    i have been getting BSOD since last 1 week , i initially thoughtit was recent software causing that i removed all recent updates (excluding microsoft silverlite) , i had issues with DVD RW (i saw exclamation in device manager and i uninstalled it)

    sometimes i get distorted screen , my last screen was distorted and sometimes with stop messages following are some of the messages.

    1. System service exception
    Stop 0x000003b (P1,p2,P3,P4)
    Win32k.sys -Adress FFFF9600.....


    2. Reference by pointer
    Stop0300000018 (PXXX1,PXX2,PX3,pXX4)

    3. Stop 0x000000F4 (P1,P2,P3,p4)

    4. saying issue may be related to video adapter

    stop 0x0000007e (p1,p1,p3,p4)
    PARTMGR.SYS Address FFFFf88000E8B64 5 base at FFFFF88000e70000 datestam 4f641bc1


    5. Distorted BSOD

    with 5th being the latest , in between now and then i have been getting distirted one

    I get these BSOD sometimes once in a day to twice thrice a day.
      My Computer


  2. Posts : 378
    Windows 10 Pro x64 (UPGRADED - 10/20/2016)
       #2

    Could you please give us your full system specifications including your power supply manufacturer and model? (Including wattage) Your most recent (14/04/17)

    Be sure to update the BIOS, low level chipset drivers, and other major device drivers.
    ============================================================
    BCCode: 9F 0x0000009F

    Are you using any Roxio or Nero programs? These have been known to cause this problem even
    if they were working well for a long period of time. If so check with their support.

    Code:
    Loading Dump File [C:\Users\KFlamson\Downloads\02HW021583-Wed_07_05_2017_202410_72\041417-41995-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0012e3a2?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`08eff022?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`08173a52?
    Symbol search path is: srv*
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.23153.amd64fre.win7sp1_ldr.150804-0600
    Machine Name:
    Kernel base = 0xfffff800`0360f000 PsLoadedModuleList = 0xfffff800`03851730
    Debug session time: Fri Apr 14 08:00:06.938 2017 (UTC + 1:00)
    System Uptime: 0 days 0:13:22.701
    Loading Kernel Symbols
    ..
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    .............................................................
    ................................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000009F, {4, 258, fffffa80036acb50, fffff80000b9a3d0}
    
    *** WARNING: Unable to verify timestamp for ctxusbm.sys
    *** ERROR: Module load completed but symbols could not be loaded for ctxusbm.sys
    Implicit thread is now fffffa80`036acb50
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : ctxusbm.sys ( ctxusbm+2f98 )
    
    Followup:     MachineOwner
    ---------
    
    0: 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: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    	subsystem.
    Arg2: 0000000000000258, Timeout in seconds.
    Arg3: fffffa80036acb50, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9a3d0, nt!TRIAGE_9F_PNP on Win7 and higher
    
    Debugging Details:
    ------------------
    
    Implicit thread is now fffffa80`036acb50
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  7601.23153.amd64fre.win7sp1_ldr.150804-0600
    
    SYSTEM_MANUFACTURER:  LENOVO
    
    SYSTEM_PRODUCT_NAME:  20AN0069US
    
    SYSTEM_SKU:  LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p
    
    SYSTEM_VERSION:  ThinkPad T440p
    
    BIOS_VENDOR:  LENOVO
    
    BIOS_VERSION:  GLET85WW (2.39 )
    
    BIOS_DATE:  09/29/2016
    
    BASEBOARD_MANUFACTURER:  LENOVO
    
    BASEBOARD_PRODUCT:  20AN0069US
    
    BASEBOARD_VERSION:  0B98401 WIN
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 4
    
    BUGCHECK_P2: 258
    
    BUGCHECK_P3: fffffa80036acb50
    
    BUGCHECK_P4: fffff80000b9a3d0
    
    DRVPOWERSTATE_SUBCODE:  4
    
    FAULTING_THREAD:  036acb50
    
    CPU_COUNT: 4
    
    CPU_MHZ: 9be
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3c
    
    CPU_STEPPING: 3
    
    CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 21'00000000 (cache) 21'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_SESSION_HOST:  KYLE-PC
    
    ANALYSIS_SESSION_TIME:  07-05-2017 21:40:37.0118
    
    ANALYSIS_VERSION: 10.0.15063.0 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff80003674cc2 to fffff8000368218a
    
    STACK_TEXT:  
    fffff880`0430ee50 fffff800`03674cc2 : fffffa80`036acc10 fffffa80`036acb50 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`0430ef90 fffff800`036860ef : fffff880`060477c0 fffffa80`07f704b8 fffffa80`00000000 fffff880`00f5dbb7 : nt!KiCommitThreadWait+0x1d2
    fffff880`0430f020 fffff880`06001ebf : fffffa80`08879e00 fffffa80`00000000 fffffa80`08879e00 fffffa80`07f75400 : nt!KeWaitForSingleObject+0x19f
    fffff880`0430f0c0 fffff880`060042e0 : fffffa80`08879e02 fffffa80`08879e30 fffffa80`08a2b050 fffff880`0430f298 : usbhub!UsbhSyncSendCommand+0x287
    fffff880`0430f1a0 fffff880`060043e5 : fffffa80`08879e30 00ff0000`02000680 00000000`000000ff 00000000`00000000 : usbhub!UsbhGetDescriptor+0x80
    fffff880`0430f210 fffff880`06004b85 : 00000000`00000000 fffff880`060300ff 00000000`c0000000 fffffa80`08a2b050 : usbhub!UsbhGetHubConfigurationDescriptor+0x85
    fffff880`0430f290 fffff880`06006298 : 00000000`00000000 00000000`00000000 00000000`c0000000 fffffa80`08a2b050 : usbhub!UsbhConfigureUsbHub+0x69
    fffff880`0430f300 fffff880`06024467 : fffff880`060470c0 00000000`00000005 00000000`00000002 fffffa80`07ffecb0 : usbhub!UsbhInitialize+0x2d0
    fffff880`0430f390 fffff880`06024963 : ffffffff`c0000034 00000000`00000004 fffffa80`08a2b708 fffffa80`08a2b000 : usbhub!UsbhModuleDispatch+0xc7
    fffff880`0430f3d0 fffff880`06024fe2 : fffffa80`08a2b1a0 fffffa80`08a2b1a0 fffffa80`08a2b708 fffffa80`08a2b050 : usbhub!Usbh_FDO_WaitPnpStart+0x113
    fffff880`0430f420 fffff880`0602703b : 00000000`00000000 fffffa80`0854dc60 fffffa80`0854de00 fffffa80`08a2b100 : usbhub!Usbh_FDO_Pnp_State+0x6e
    fffff880`0430f460 fffff880`06025925 : fffffa80`08a2b1a0 fffffa80`08a2b050 fffffa80`0854dee0 fffffa80`0854dc60 : usbhub!UsbhFdoPnp_StartDevice+0x143
    fffff880`0430f4e0 fffff880`06001fdf : fffff880`06001f60 00000001`05eb2900 fffffa80`08a2b050 fffffa80`087b39b0 : usbhub!UsbhFdoPnp+0x9d
    fffff880`0430f510 fffff880`05eb3f98 : fffffa80`00000020 fffffa80`08696060 fffffa80`08a2b050 fffffa80`08a2b050 : usbhub!UsbhGenDispatch+0x7f
    fffff880`0430f540 fffffa80`00000020 : fffffa80`08696060 fffffa80`08a2b050 fffffa80`08a2b050 fffff800`037c5e60 : ctxusbm+0x2f98
    fffff880`0430f548 fffffa80`08696060 : fffffa80`08a2b050 fffffa80`08a2b050 fffff800`037c5e60 fffff880`0430f610 : 0xfffffa80`00000020
    fffff880`0430f550 fffffa80`08a2b050 : fffffa80`08a2b050 fffff800`037c5e60 fffff880`0430f610 00000000`00000000 : 0xfffffa80`08696060
    fffff880`0430f558 fffffa80`08a2b050 : fffff800`037c5e60 fffff880`0430f610 00000000`00000000 fffffa80`0854dee0 : 0xfffffa80`08a2b050
    fffff880`0430f560 fffff800`037c5e60 : fffff880`0430f610 00000000`00000000 fffffa80`0854dee0 00000000`00000000 : 0xfffffa80`08a2b050
    fffff880`0430f568 fffff880`0430f610 : 00000000`00000000 fffffa80`0854dee0 00000000`00000000 00000000`00000000 : nt!DEVPKEY_Device_SessionId
    fffff880`0430f570 00000000`00000000 : fffffa80`0854dee0 00000000`00000000 00000000`00000000 fffffa80`087b39b0 : 0xfffff880`0430f610
    
    
    STACK_COMMAND:  .thread 0xfffffa80036acb50 ; kb
    
    THREAD_SHA1_HASH_MOD_FUNC:  795de22f439fd14a285c7f002be562fa58bb7a3a
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3e04941bf7b104b23ccac19a642beb883e75aa5c
    
    THREAD_SHA1_HASH_MOD:  1dfdb5978abeb240d6a49cf51b431a360411d8d0
    
    FOLLOWUP_IP: 
    ctxusbm+2f98
    fffff880`05eb3f98 ??              ???
    
    SYMBOL_STACK_INDEX:  e
    
    SYMBOL_NAME:  ctxusbm+2f98
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ctxusbm
    
    IMAGE_NAME:  ctxusbm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  57c4352f
    
    FAILURE_BUCKET_ID:  X64_0x9F_4_ctxusbm+2f98
    
    BUCKET_ID:  X64_0x9F_4_ctxusbm+2f98
    
    PRIMARY_PROBLEM_CLASS:  X64_0x9F_4_ctxusbm+2f98
    
    TARGET_TIME:  2017-04-14T07:00:06.000Z
    
    OSBUILD:  7601
    
    OSSERVICEPACK:  1000
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 7
    
    OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2015-08-04 17:57:48
    
    BUILDDATESTAMP_STR:  150804-0600
    
    BUILDLAB_STR:  win7sp1_ldr
    
    BUILDOSVER_STR:  6.1.7601.23153.amd64fre.win7sp1_ldr.150804-0600
    
    ANALYSIS_SESSION_ELAPSED_TIME:  beb
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_4_ctxusbm+2f98
    
    FAILURE_ID_HASH:  {a4ab4afb-8473-cc92-8216-7be9d288c596}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm ctxusbm
    Browse full module list
    start             end                 module name
    fffff880`05eb1000 fffff880`05ed7000   ctxusbm  T (no symbols)           
        Loaded symbol image file: ctxusbm.sys
        Image path: \SystemRoot\system32\DRIVERS\ctxusbm.sys
        Image name: ctxusbm.sys
        Browse all global symbols  functions  data
        Timestamp:        Mon Aug 29 14:14:23 2016 (57C4352F)
        CheckSum:         00028EB9
        ImageSize:        00026000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 13:27.
Find Us