[BSOD] Lenovo Thinkpad T420

isabdo70 · 27 Oct 2014

Dear all,

I went through the different steps mentioned in "clean-up-factory-bloatware" article, apart from last point which consists of re-installing my machine! But still I have BSOD and it drives me crazy.

I attached the DM Log Collector results. Hope you'll be able to find what causes this.

Thanks for your help
Isma

koolkat77 · 27 Oct 2014

Similar errors from NVIDIA,

Arc said:

Though there are other issues, like some unnecessary nvidia services ...

Code:

BugCheck 7F, {8, 80050033, 406f8, fffff88004d5103f}

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

Followup: MachineOwner
---------

....

You could try an older driver version.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\LT-IT39-27_10_2014_134204_61\102714-6988-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e8e890
Debug session time: Mon Oct 27 17:10:16.177 2014 (UTC + 6:00)
System Uptime: 0 days 0:13:32.859
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff880105a6697}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff880105a6697

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  5

LAST_CONTROL_TRANSFER:  from fffff80002cc0169 to fffff80002cc0bc0

STACK_TEXT:  
fffff800`047d7d28 fffff800`02cc0169 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`047d7d30 fffff800`02cbe632 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`047d7e70 fffff880`105a6697 : 00640020`006e0061 00650073`00650069 00700055`00200073 00640061`00720067 : nt!KiDoubleFaultAbort+0xb2
fffff880`0afbb000 fffff880`105a039d : 00000000`00000000 003d0050`00530045 fffffa80`092ef410 0076006c`006f0076 : dxgmms1!VidSchiUpdateCurrentIsrFrameTime+0x8f
fffff880`0afbb030 fffff880`105a0044 : 00000000`0000cb8a 00000000`00000000 00000000`02020000 002d006f`00690073 : dxgmms1!VidSchiProcessIsrVSync+0x69
fffff880`0afbb0c0 fffff880`1059ff82 : 006c00c4`003d004f 006c0069`002000e4 fffffa80`0aa41000 fffff880`0afbb510 : dxgmms1!VidSchDdiNotifyInterruptWorker+0xb0
fffff880`0afbb110 fffff880`104a613f : fffffa80`0979b480 006e0065`0065006c 00000000`02020000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`0afbb140 fffff880`0f8dd5ae : fffff880`0afbb330 fffff880`0afbb330 00000000`00000000 fffffa80`0968f000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`0afbb170 fffff880`0afbb330 : fffff880`0afbb330 00000000`00000000 fffffa80`0968f000 fffff880`0f8dd53e : nvlddmkm+0xcf5ae
fffff880`0afbb178 fffff880`0afbb330 : 00000000`00000000 fffffa80`0968f000 fffff880`0f8dd53e fffffa80`0968f000 : 0xfffff880`0afbb330
fffff880`0afbb180 00000000`00000000 : fffffa80`0968f000 fffff880`0f8dd53e fffffa80`0968f000 00000000`00000000 : 0xfffff880`0afbb330


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f
fffff880`105a6697 ff1563290000    call    qword ptr [dxgmms1!_imp_KeQueryPerformanceCounter (fffff880`105a9000)]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

FAILURE_BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiUpdateCurrentIsrFrameTime+8f

Followup: MachineOwner
---------

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f80e000 fffff880`104a3000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Sep 12 14:34:37 2014 (5412B01D)
    CheckSum:         00C5788A
    ImageSize:        00C95000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to