Blue Screen 32 bit

All of these dumps have the same error code:

STOP 0x00000116: VIDEO_TDR_ERROR

Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card

BSOD Index

Each dump points to the same driver, igdkmd32.sys, which is an Intel Graphics Kernel Mode Driver.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {85b4b008, 906283c0, 0, 2}

*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
Probably caused by : igdkmd32.sys ( igdkmd32+163c0 )

Followup: MachineOwner


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 859d1008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 906473c0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP: 
igdkmd32+163c0
906473c0 55              push    ebp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8b4d8b74 90f92adb 00000116 859d1008 906473c0 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8b4d8b98 90f938fa 906473c0 00000000 00000002 dxgkrnl+0x8cadb
8b4d8bbc 90fc392c 00000000 00000102 86fb3008 dxgkrnl+0x8d8fa
8b4d8c34 90feda32 fffffcfb 0007f17a 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8b4d8c5c 90fee153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8b4d8c98 90fca8f0 8b4d8c90 8724b5c8 8724b7c8 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8b4d8d28 90fef4b7 86fb3008 8325b3f1 86fb3008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8b4d8d3c 90fef573 86fb3008 00000000 86fd8d48 dxgmms1!VidSchiRun_PriorityTable+0xf
8b4d8d50 8342d6bb 86fb3008 ac05e7cf 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8b4d8d90 832df0f9 90fef4f4 86fb3008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
igdkmd32+163c0
906473c0 55              push    ebp

SYMBOL_NAME:  igdkmd32+163c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd32

IMAGE_NAME:  igdkmd32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b800b3b

FAILURE_BUCKET_ID:  0x116_IMAGE_igdkmd32.sys

BUCKET_ID:  0x116_IMAGE_igdkmd32.sys

Followup: MachineOwner

You have a couple of older drivers that should be updated or deleted.

The first is a bit of a mystery to me, Alidevice.SYS 2008. It is a driver from your part of the world. Since I do not read Chinese, I cannot tell you much about it other than some malware programs identify it as a keylogger. You can do a Google search and perhaps determine what program or hardware it is associated with. This link may help you if you read Chinese.

Ö§¸¶±¦ÉçÇø-Æä´ú°¢Àí°Í°Í½âÊÍAlidevice.sysÇý¶¯

I found the above link on the Kaspersky forum: Keylogger - Kaspersky Lab Forum

The second driver is seehcri.sys 2008. It is a Sony Ericsson Mobile driver.

Both of these drivers should be updated. The first might can be deleted depending on what you can find out about it.

Since the BSOD's point to a video problem, I suggest that you download and install a fresh copy of Igdkmd32.sys from the Intel website in case your existing driver has become corrupted.

If that and updating the above drivers do not solve the problem, your next step will be to test your graphics including monitoring the temperature. Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

Please let us know the results of your test.

Here you go: https://www.sevenforums.com/crash-loc...eshooting.html

Thanks, Jonathan; I had forgotten about that thread. I now have it bookmarked.

It sounds like that driver and the program it is associated with buried pretty deep into you system. Thanks for getting back with us. Here's hoping your BSOD's are gone.

Could you test your temps with Speedfan?