Unsolved
This post is more than 5 years old
4 Posts
0
16034
September 9th, 2010 11:00
Vostro 1510 Windows 7 video driver (Intel 965) collapsing
Hi there, I am having a very odd problem, but googling I noticed I am not the only one (only I couldn't find any solution).
About 4 months ago I installed W7 (clean install) and got the graphics driver from the Intel website, everything went fine for a while. Then the screen started freezing and the system rebooted after a blue screen. The message said there was some problem at a "igxprd32" file. I decided to do nothing by then since I believed this would be solved when I reinstalled W7 from the beginning. Only the problem got worse and worse until the system froze right after complete boot, or not more than 15 minutes after started.
Then I installed W7 again (clean install again), got the updated drivers but the problem persisted. I tried virtually everything, even running the Vista drivers instead but nothing seems to work. I can only use the computer if running a standard graphics driver, but in this case the resolution is awful as expected, and there is no more gaming
May somebody help me out?
Thanks!
kirkd
6 Operator
•
5.2K Posts
0
September 9th, 2010 13:00
It appears Intel ha shad mucho problems with this video driver.
See this SITE for some hints. You should also search the web for more info on the igxprd32 driver.
zoidblerg
4 Posts
0
September 11th, 2010 12:00
I don't know if I made a confusion but now the driver that has been crashing is igdkmd32.sys... :(
I cannot use any Aero theme on W7 or play any game.
Anything else?
zoidblerg
4 Posts
0
September 11th, 2010 21:00
This is what the minidump file says:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091110-34788-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a15000 PsLoadedModuleList = 0x82b5d810
Debug session time: Sat Sep 11 18:39:40.772 2010 (UTC - 3:00)
System Uptime: 0 days 1:17:29.520
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 85838510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9243cf20, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000d, Optional internal context dependent data.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
FAULTING_IP:
igdkmd32+11f20
9243cf20 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:
8d289898 929c0adb 00000116 85838510 9243cf20 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8d2898bc 929c18fa 9243cf20 00000000 0000000d dxgkrnl+0x8cadb
8d2898e0 9172392c 00000000 00000000 8d2899a4 dxgkrnl+0x8d8fa
8d289958 9174acd9 fffffcfb 00048ba8 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8d289984 9173444b 880cb008 8d2899a4 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
8d289a1c 91735aaf 9b2a3288 00000001 00000000 dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x181
8d289a34 91745451 c2f8fd88 36687cda 883b6000 dxgmms1!VIDMM_GLOBAL::WaitForAllPagingEngines+0x1b
8d289a94 91735edb c2f8fd88 b3f11738 8553e190 dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0x339
8d289ac0 917378b4 8804b008 00000016 898615b0 dxgmms1!VIDMM_GLOBAL::PageInAllocations+0x8f
8d289bb8 9174e93e c2f1f2f0 00000000 8553e190 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x95e
8d289d18 9174f22f 8aa267e0 873ad0d8 8d289d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
8d289d28 9174f4cc 8aa267e0 82a513f1 880cb008 dxgmms1!VidSchiSubmitQueueCommand+0x61
8d289d3c 9174f573 880cb008 00000000 882b5558 dxgmms1!VidSchiRun_PriorityTable+0x24
8d289d50 82c236d3 880cb008 a94b4d66 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8d289d90 82ad50f9 9174f4f4 880cb008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd32+11f20
9243cf20 55 push ebp
SYMBOL_NAME: igdkmd32+11f20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4aba7471
FAILURE_BUCKET_ID: 0x116_IMAGE_igdkmd32.sys
BUCKET_ID: 0x116_IMAGE_igdkmd32.sys
Followup: MachineOwner
---------
What does it mean???
zoidblerg
4 Posts
0
September 22nd, 2010 08:00
Well, if someone might be interested, and to save my experience to the posterity :) I am sorry to inform that the problem was solved immediately after replacing the motherboard. So this was not a driver issue at all. :(
It's cost me more than I was willing to spend, but modern life has its expenses... :)