New
#1
BSOD on 10 lenovo computers
Hi,
I have a big problem with 10 computers of this type (M91p 4518). They're still crashing into BSOD once or twice a week. I'll post dump file down here. My sugestion was that I have to reinstall drivers for my graphic card, but that didn't help. Do you have any idea?? What about BIOS flash?
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [M:\voku sep\032112-25755-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x82c37000 PsLoadedModuleList = 0x82d804d0
Debug session time: Wed Mar 21 15:34:52.638 2012 (GMT+2)
System Uptime: 0 days 7:18:37.139
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.........
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 801dd000, 0, 0}
*** WARNING: Unable to verify timestamp for cfgpro.sys
*** ERROR: Module load completed but symbols could not be loaded for cfgpro.sys
Probably caused by : igdkmd32.sys ( igdkmd32+d0e67 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801dd000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: services.exe
CURRENT_IRQL: 8
LAST_CONTROL_TRANSFER: from 96b0614e to 96b05e67
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9d432554 96b0614e 87bd1000 00000000 9d4325a8 igdkmd32+0xd0e67
9d432564 96aac4f8 87bd1000 00000000 87bd1000 igdkmd32+0xd114e
9d4325a8 96a56e60 87bd1000 00000000 00000000 igdkmd32+0x774f8
9d4325f0 97502b14 87bd1000 00000000 9d432614 igdkmd32+0x21e60
9d432600 82cc1b10 879cca00 87bb8920 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
9d432614 82c7184d 879cca00 87bb8920 9d432640 nt!KiInterruptMessageDispatch+0x12
9d432614 82e6a45f 879cca00 87bb8920 9d432640 nt!KiInterruptDispatch+0x6d
9d4326c8 82e76507 00030002 00000002 9d432960 nt!CmpCompareCompressedName+0x4f
9d432714 82e6a244 9d432768 00000002 9d432988 nt!CmpKcbCacheLookup+0x1d8
9d432900 82e651e4 8960aa18 9d4329c0 9d432944 nt!CmpBuildHashStackAndLookupCache+0x2e6
9d432aa8 82e5cbee 8960aa18 84da6388 87a904c0 nt!CmpParseKey+0x36e
9d432b24 82e6d000 00000000 9d432b78 00000240 nt!ObpLookupObjectName+0x4fa
9d432b80 82e6af31 9d432d58 84da6388 6e664d00 nt!ObOpenObjectByName+0x165
9d432c60 82e83798 9d432dc8 000f003f 9d432d58 nt!CmOpenKey+0x1f4
9d432c80 82c7528a 9d432dc8 000f003f 9d432d58 nt!NtOpenKey+0x18
9d432c80 82c7363d 9d432dc8 000f003f 9d432d58 nt!KiFastCallEntry+0x12a
9d432d04 9821c979 9d432dc8 000f003f 9d432d58 nt!ZwOpenKey+0x11
9d432f04 88730aeb 871d7448 9d432f24 9d432f50 cfgpro+0x979
9d432f70 887339f0 9d432fb4 85391e28 00000000 fltmgr!FltpPerformPreCallbacks+0x34d
9d432f88 887471fe 9d432fb4 8874af3c 00000000 fltmgr!FltpPassThroughInternal+0x40
9d432f9c 887478b7 9d432fb4 85391e28 84e72ec8 fltmgr!FltpCreateInternal+0x24
9d432fe0 82c6e5be 8723b280 871f0008 84e72f24 fltmgr!FltpCreate+0x2c9
9d432ff8 82e7d3e7 00000000 00000000 00000000 nt!IofCallDriver+0x63
9d4330d0 00000000 00000000 00000000 00000000 nt!IopParseDevice+0xed7
STACK_COMMAND: kb
FOLLOWUP_IP:
igdkmd32+d0e67
96b05e67 51 push ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: igdkmd32+d0e67
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e1c952c
FAILURE_BUCKET_ID: 0x7f_8_igdkmd32+d0e67
BUCKET_ID: 0x7f_8_igdkmd32+d0e67
Followup: MachineOwner
---------
Thank you for help!