BSOD on 10 lenovo computers

[sixxy]

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!

 

[mgorman87]

Please provide a report

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[sixxy]

Here it is, even with dmp file.
View attachment 206878

My system is Windows 7 Prof 32bit

Thanks for help!

 

[mgorman87]

You didn't upload a report, you uploaded one dump file. I need the whole report. Follow the instructions in the link I gave you

 

[sixxy]

Well, I didn't know that. Here it is!
View attachment 207069

 

[James7679]

Have you tried this? Intel® Driver Update Utility for graphics drivers

 

[writhziden]

You still have only followed bits and pieces of the instructions. Carefully go through each step in the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html and follow them to the letter. Post back with the full crash reports.

 

[sixxy]

Hope this is it. Thanks for reply.
View attachment 209578

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\sixxy\Windows_NT6_BSOD_jcgriff2\041712-17893-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.17790.x86fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0x82c1c000 PsLoadedModuleList = 0x82d654d0
Debug session time: Tue Apr 17 00:40:00.416 2012 (UTC - 6:00)
System Uptime: 0 days 1:48:01.998
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+1384f0 )

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 94e15021 to 94f434f0

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b428cffc 94e15021 87bd0000 b428d034 958d8eae igdkmd32+0x1384f0
b428d048 94edbebf 87bd0000 b428d580 00000000 igdkmd32+0xa021
b428d598 94edc14e 87bd0000 00000000 b428d5ec igdkmd32+0xd0ebf
b428d5a8 94e824f8 87bd0000 00000000 87bd0000 igdkmd32+0xd114e
b428d5ec 94e2ce60 87bd0000 00000000 00000000 igdkmd32+0x774f8
b428d634 958d8b14 87bd0000 00000000 b428d658 igdkmd32+0x21e60
b428d644 82ca6b30 87e11a00 8776d920 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
b428d658 82c567cd 87e11a00 8776d920 b428d684 nt!KiInterruptMessageDispatch+0x12
b428d658 82e4bb56 87e11a00 8776d920 b428d684 nt!KiInterruptDispatch+0x6d
b428d74c 82e4f074 00000020 858a66fc b428d8fc nt!CmpParseCacheLookup+0xb3
b428d928 82e4a224 8960aa18 b428d9e8 b428d96c nt!CmpBuildHashStackAndLookupCache+0xd6
b428dad0 82e41c2e 8960aa18 84d95388 87732008 nt!CmpParseKey+0x36e
b428db4c 82e52040 00000000 b428dba0 00000240 nt!ObpLookupObjectName+0x4fa
b428dba8 82e4ff71 b428dd80 84d95388 6e664d00 nt!ObOpenObjectByName+0x165
b428dc88 82e687d8 b428ddf0 000f003f b428dd80 nt!CmOpenKey+0x1f4
b428dca8 82c5a20a b428ddf0 000f003f b428dd80 nt!NtOpenKey+0x18
b428dca8 82c585bd b428ddf0 000f003f b428dd80 nt!KiFastCallEntry+0x12a
b428dd2c 82828979 b428ddf0 000f003f b428dd80 nt!ZwOpenKey+0x11
b428df2c 88723aeb 85135068 b428df4c b428df78 cfgpro+0x979
b428df98 887269f0 b428dfdc 8783a0c0 00000000 fltmgr!FltpPerformPreCallbacks+0x34d
b428dfb0 8873a1fe b428dfdc 8873df3c 00000000 fltmgr!FltpPassThroughInternal+0x40
b428dfc4 8873a8b7 b428dfdc 8783a0c0 851bf0b8 fltmgr!FltpCreateInternal+0x24
b428dff8 0012000e 00000000 00000000 00000000 fltmgr!FltpCreate+0x2c9
af634200 00000000 00000002 00000000 b1a3af28 0x12000e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdkmd32+1384f0
94f434f0 55              push    ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdkmd32+1384f0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd32

IMAGE_NAME:  igdkmd32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e1c952c

FAILURE_BUCKET_ID:  0x7f_8_igdkmd32+1384f0

BUCKET_ID:  0x7f_8_igdkmd32+1384f0

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

It appears to be caused by the cfgpro.sys driver. I am unable to find any information about this driver online. It may be malware or a virus.

• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan.
  
  
• Run a full scan with your Symantec antivurs software.

Your graphics card driver from Intel also seems to be corrupted. Fully uninstall it and re-install it.

1. Download the drivers you want for your display card(s)
   1. Click Start Menu
   2. Right Click My Computer/Computer
   3. Click Manage
   4. Click Device Manager from the list on the left
   5. Expand Display adapters
   6. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
      
      Alternatively:
      1. Login as an adminstrative user
      2. Click Start Menu
      3. Click Control Panel
      4. Click Hardware and Sound
      5. Click Device Manager (the last link under Devices and Printers)
      6. Expand Display adapters
      7. Do the following for each adapter (in case you have multiple display cards)
         • Right click the adapter
         • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
         • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
2. Restart your computer after uninstalling drivers for all display cards
3. Install the driver you selected for the display cards once Windows starts

 

[sixxy]

I'm here again . I uninstalled and re-installed drivers on every computer where were problem. After few days it crashed again. Everything is same. I tried open dump files with BlueScreenView and on every computer is same fault driver. It looks like this...
View attachment 211102
FYI: Im in touch with guy who made for us cfgpro and he claims that its not fault of cfgpro. Cfgpro is software which disable internet browsing with firefox portable. We're using it for running web aplication.

 

[writhziden]

Can you give a website for the cfgpro driver. We have a driver list that is maintained by one of our gurus on here, and it would be helpful to get that information for the list.

Also, please provide the full crash reports through the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[event3horizon]

It may be your symantec antivirus. Just a hunch.. no proof. Run one of them in safe mode for a while.

ALSO what is this?

csp_kontr_xp.exe c:\program files\codisplus\csp_kontr_xp.exe 1696 8 200 1380 30.4.2012 9:08 1.1.0.1 19,00 kB (19 456 bajtů) 10.5.2011 12:48

 

[writhziden]

I agree with [URL="http://www.sevenforums.com/member.php?u=178069"]event3horizon[/url]. You are using web based software that seems fairly unknown. If it is unknown to us and Google, chances are it is unknown to Symantec. That may be causing conflicts with the antivirus software.

 

[James7679]

csp_kontr_xp.exe c:\program files\codisplus\csp_kontr_xp.exe 1696 8 200 1380 30.4.2012 9:08 1.1.0.1 19,00 kB (19 456 bajtů) 10.5.2011 12:48

Do you really want to know what CODIS is?

Probably best not to worry about that too much guys.

 

[event3horizon]

csp_kontr_xp.exe c:\program files\codisplus\csp_kontr_xp.exe 1696 8 200 1380 30.4.2012 9:08 1.1.0.1 19,00 kB (19 456 bajtů) 10.5.2011 12:48

Do you really want to know what CODIS is?

Probably best not to worry about that too much guys.

ahaaaaaaaaaa

 

[James7679]

Can you give a website for the cfgpro driver. We have a driver list that is maintained by one of our gurus on here, and it would be helpful to get that information for the list.
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

I think this is for lab equipment. sixxy, do you have lab equipment connected to these computers? If so, you need to contact the vendors about possible driver updates.