BSOD during most newer video games

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Alex Davis, Feb 5, 2013.

  1. Alex Davis

    Alex Davis New Member

    Joined:
    Feb 5, 2013
    Messages:
    4
    Likes Received:
    0
    I've been getting repeated crashes on my l502x laptop whenever playing most video games, especially those that are a little more graphically intensive. Until recently I could play these no problem, but now after 15 minutes to an hour in the screen locks up, the sound turns into a drone, then I go to BSOD or in some cases the computer hard reboots. I recently ran a windows memory diagnostic and it came back clean and I reinstalled the video drivers, but it didn't help. Here's hoping the wizards on this forum can come up with a solution!

    My laptop is an XPS L502x with an Intel i5-2410 cpu @2.30GHz
    6.00 GB ram
    64 bit operating system

    View attachment W7F_06-02-2013.zip

    Here is my W7F Diagnostic file with CPU-z screenshot and RAMMon.

    Thanks for your time!
     
  2. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    Majority of your crashdumps appear to be a sudden removal of the device associated with the Synaptic Touchpad driver, which probably means the touchpad itself. While usually this is normal behavior during a power down situation like putting the system to sleep or shutting down, the touchpad shouldn't be magically disappearing during normal use. I have a feeling this means either the motherboard or the keyboard/pad component is not doing so hot, which also means you'll need to turn the system in for repair/replacement if that's the case. I do notice the driver itself is old (Dec 17, 2010) so try updating it and see if that helps.

    I also am noticing a couple of your most recent crashes being caused by what I believe to be a recent bug in the Nvidia drivers since the 310 driver series came out, which has been causing a number of people a lot of grief. If it persists, you may have success downgrading the driver before the 310 driver series. My current research into the situation has not turned up any more specifics on the issue, other than I am fairly confident it's a consistent problem.

    If you wish for an improved assessment on the situation, you can turn on Driver Verifier as instructed here, making sure to restart the system afterwards. This will set Windows into a more alert state on detecting driver bugs, and if it finds one it will BSOD the system, which you can send us the crashdump for. As mentioned in the article, it may cause a boot loop, which means it's doing its job. Go into safe mode and disable Driver Verifier from there, then you can send us the crashdumps.



    Analysts:

    The spattering of crashdumps I looked at, starting with the oldest, has shown in a fairly consistent manner a power IRP for the Synaptic touchpad driver behind held up for a considerable amount of time. So far the ones I've checked have not shown that the IOStatus field for the IRP was populated with any error, so it doesn't appear to be a problem with the driver not understanding the power IRP given to it. I actually have a feeling it may have something more to do with the video card. So far whenever I dump the raw stack for the thread holding the IRP it has Nvidia drivers showing up all inside it. Updating the Nvidia driver didn't seem to fix the problem for the client, so there may actually be a hardware issue. It's possible the video card may be holding up the Synaptic touchpad IRP, but I cannot determine this by the minidumps. Using Driver Verifier will assist in providing us more clues.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8005f52c20, fffff80000b9c4d8, fffffa800b021010}
    
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    Probably caused by : ACPI.sys
    
    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 (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8005f52c20, Physical Device Object of the stack
    Arg3: fffff80000b9c4d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: [COLOR=#ff8c00]fffffa800b021010[/COLOR], The blocked IRP
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  ACPI.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc106
    
    MODULE_NAME: ACPI
    
    FAULTING_MODULE: fffff88000f5c000 ACPI
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`00b9c488 fffff800`02f33773 : 00000000`0000009f 00000000`00000003 fffffa80`05f52c20 fffff800`00b9c4d8 : nt!KeBugCheckEx
    fffff800`00b9c490 fffff800`02eca8b6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x22df0
    fffff800`00b9c530 fffff800`02ec9bb6 : fffff800`030612e0 00000000`0112e67c 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5a0 fffff800`02eca7de : 0000028e`5e76bde5 fffff800`00b9cc18 00000000`0112e67c fffff800`0303d208 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cbf0 fffff800`02ec9f27 : fffff880`0ff7e6c2 fffff800`0112e67c 00000092`9f25ae3f 00000000`0000007c : nt!KiTimerExpiration+0x1be
    fffff800`00b9cc90 fffff800`02ec6f9a : fffff800`03039e80 fffff800`03047cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_[COLOR=#ff0000]SynTP[/COLOR]_IMAGE_ACPI.sys
    
    BUCKET_ID:  X64_0x9F_3_[COLOR=#ff0000]SynTP[/COLOR]_IMAGE_ACPI.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd>[COLOR=#0000cd] !irp[/COLOR] [COLOR=#ff8c00]fffffa800b021010 [/COLOR][COLOR=#0000cd]1[/COLOR]
    Irp is active with 9 stacks 8 is current (= 0xfffffa800b0212d8)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
    Flags = 00000000
    ThreadListEntry.Flink = fffffa800b021030
    ThreadListEntry.Blink = fffffa800b021030
    IoStatus.Status = 00000000
    IoStatus.Information = 00000000
    RequestorMode = 00000000
    Cancel = 00
    CancelIrql = 0
    ApcEnvironment = 00
    UserIosb = 00000000
    UserEvent = 00000000
    Overlay.AsynchronousParameters.UserApcRoutine = 00000000
    Overlay.AsynchronousParameters.UserApcContext = 00000000
    Overlay.AllocationSize = 00000000 - 00000000
    CancelRoutine = 00000000   
    UserBuffer = 00000000
    &Tail.Overlay.DeviceQueueEntry = fffffa800b021088
    Tail.Overlay.Thread = 00000000
    Tail.Overlay.AuxiliaryBuffer = 00000000
    Tail.Overlay.ListEntry.Flink = fffffa800c7e50b8
    Tail.Overlay.ListEntry.Blink = fffff8000306f300
    Tail.Overlay.CurrentStackLocation = fffffa800b0212d8
    Tail.Overlay.OriginalFileObject = 00000000
    Tail.Apc = 00000000
    Tail.CompletionKey = 00000000
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[ [COLOR=#006400]16, 2[/COLOR]]   0 e1 [COLOR=#ff8c00]fffffa8008c96e20 [/COLOR]00000000 00000000-00000000    pending     [COLOR=#006400][I]//16,2 IRP code means Power IRP: Remove Device[/I][/COLOR]
    [COLOR=#ff0000]          Unable to load image \SystemRoot\system32\DRIVERS\SynTP.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SynTP.sys
    *** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
     \Driver\SynTP (IopUnloadSafeCompletion)[/COLOR]
                Args: 00014400 00000001 00000004 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8005d42c90    
    
                Args: 00000000 00000000 00000000 00000000
    
    0: kd>[COLOR=#0000cd] !devobj[/COLOR] [COLOR=#ff8c00]fffffa8008c96e20[/COLOR]    [COLOR=#006400]//device it wishes to remove is most likely touchpad[/COLOR]
    Device object (fffffa8008c96e20) is for:
     InfoMask field not found for _OBJECT_HEADER at fffffa8008c96df0
     \Driver\[COLOR=#ff0000]SynTP [/COLOR]DriverObject fffffa8008c94e70
    Current Irp 00000000 RefCount 0 Type 00000027 Flags 00002004
    DevExt fffffa8008c98ba0 DevObjExt fffffa8008c96f90 
    ExtensionFlags (0x00000800)  
                                 Unknown flags 0x00000800
    [COLOR=#ff0000]AttachedDevice (Upper) fffffa8008c8c060 \Driver\mouclass     
    AttachedTo (Lower) fffffa8008c965b0 \Driver\i8042prt[/COLOR]
    Device queue is not busy.
    
    
    0: kd> [COLOR=#0000cd]!niemiro.rawstack[/COLOR]
    dps fffff80000b9c000 fffff80000b9cff8
    fffff800`00b9c000  00000000`00000000
    fffff800`00b9c008  00000000`00000000
    fffff800`00b9c010  00000000`00000000
    fffff800`00b9c018  00000000`00000000
    fffff800`00b9c020  00000000`00000000
    
    ...
    
    fffff800`00b9c630  fffff800`00b9c6b0
    [COLOR=#ff0000]fffff800`00b9c638  fffff880`100915dc*** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x23d5dc[/COLOR]
    fffff800`00b9c640  00000000`00000000
    fffff800`00b9c648  fffff800`0304e8c8 nt!NonPagedPoolDescriptor+0x8
    fffff800`00b9c650  00000000`00000202
    fffff800`00b9c658  fffff800`02ec357a nt!KiDeferredReadyThread+0x31a
    fffff800`00b9c660  fffff880`02f64180
    fffff800`00b9c668  fffffa80`054cc040
    fffff800`00b9c670  fffffa80`087d1040
    fffff800`00b9c678  fffff800`02ff44d3 nt!ExAllocatePoolWithTag+0x103
    fffff800`00b9c680  fffff800`00b9c6e0
    fffff800`00b9c688  fffff880`1004ec1f [COLOR=#ff0000]nvlddmkm[/COLOR]+0x1fac1f
    fffff800`00b9c690  fffff800`00b9c6f0
    fffff800`00b9c698  fffff880`1004ec1f [COLOR=#ff0000]nvlddmkm[/COLOR]+0x1fac1f
    fffff800`00b9c6a0  00000000`00000000
    fffff800`00b9c6a8  ffffe199`f84851e4
    fffff800`00b9c6b0  fffffa80`0a6d1000
    fffff800`00b9c6b8  fffffa80`054cc148
    fffff800`00b9c6c0  fffff800`00b9c720
    fffff800`00b9c6c8  fffff880`1004ec1f [COLOR=#ff0000]nvlddmkm[/COLOR]+0x1fac1f
    fffff800`00b9c6d0  fffff800`00b9c780
    fffff800`00b9c6d8  00000000`00000000
    fffff800`00b9c6e0  fffff800`00b9c710
    fffff800`00b9c6e8  fffff880`1004ed7b [COLOR=#ff0000]nvlddmkm[/COLOR]+0x1fad7b
    
    ...
    
    
     
    #2 Vir Gnarus, Feb 5, 2013
    Last edited: Feb 5, 2013
  3. Alex Davis

    Alex Davis New Member

    Joined:
    Feb 5, 2013
    Messages:
    4
    Likes Received:
    0
    Hi Vir Gnarus, thanks for the response.

    My computer actually has a toggle to disable/enable the touchpad during normal use, which I use regularly. Could that be what is showing up in that section?

    I'll turn on driver verifier later once I get off work and post the results for you.
     
  4. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    I'm not sure, but that sounds like it could be it. Are you able to invoke a BSOD by turning it off? Understand that you'll have to wait around 10-15 minutes after the action in order for the BSOD to occur, if it does.
     

Share This Page

Loading...