You have a hardware problem of some kind. I suspect your monitor or hard drive but it could be anything. Are there any other symptoms? Someone else previously reported this error here I believe.
Hi dude, I have indeed seen many people reporting this but no satisfatory answer.
The general symptom is that the screen blinks several times than freezes, sometimes when it is blinking I can notice a notification message saying that the driver has collapsed. After this, the system is stuck and I have to restart. Only rarely the system restarts by its own, that's when I get the blue screen.
I have tried to install Vista instead (which was on the computer when I bought it, and for which I can find all drivers on Dell website) and at least the computer is usable, but the driver has crashed sometimes and the games won't work.
Thanks for your message, I hope somebody else may help me.
Same problem on Dell Inspiron 1525 with Windows 7 Utimate 64-bit (same chipset). I have installed a clean Windows 7 64 and as soon as the windows installation try to "check graphic performance" the problem starts. I have tried many many drivers include one old driver for Vista, with no result. The only way i got to keep my Windows stabled (to do this post) was remove the intel graphic driver and install Standard VGA driver that comes with windows.
It doesn't even sound like the Vostro is still in shape for web surfing so the recommendation of a cheap i3 gaming system as a second computer may not be suitable. I'm still waiting for full Win 7 drivers for my printer so going from Vista 32 through Windows 7 64 bit to Windows 8 seems unlikely for me on a DG45ID. Even the upcoming nVidia 450 or 440 is less appealing to me with recent developments since I game very little. The only similar symptom I have is Windows experience index sometimes leaves Aero off for the remaining tests but returns when done with GMA 4500. Minor hardware changes have fixed everything else and may have fixed that. It looks like my 965WH will stay retired.
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.
It sounds like your hardware isn't as healthy as it was for your initial installation or your installation methods could be improved (no insult, anyone can get lackadaisical with time). You don't have the Intel installation disk which reveals the order of driver installation. INF, audio (test), graphics (evaluate with Windows Experience Index) and LAN (leave disconnected, but speeds up startup and later conflicts). At least as likely is any hardware upgrades about 4 months ago such as monitor, cables, drives, add-in cards etc. Dell has slightly different motherboards and connections so the chipset drivers might be better than the motherboard drivers if you can't use Dell drivers. The standard driver is not actually bad so more hardware information would help. Start looking at a new system unless you really like only having one computer. Check your hard drive with CHKDSK in windows or use a utility provided by the manufacturer.
Hi pal, I didn't really understand what you mean, I have just installed W7 again and the computer is working but it will crash if I ask it any complex graphic operation.
I have already run dell diagnostics on hardware but all tests passed.
What other information can I give?
Sorry for the wordy response. Maximum PC determined that Dell optimizations do change performance so your installation may differ. That is not your problem. Graphics is still dependent on the hard drive for virtual memory. Also if you have bad sectors in the area of your OS install in particular, degradation of performance can be expected. What did the Dell diagnostics tell you about the hard drive, beyond pass. I don't know if that gives info comparable to Intel Desktop Utilities or other utilities. Passing SMART may change after running CHKDSK. At first don't let it make changes.
If you're expecting a fix in the blink of an eye, I don't even support my own 965 any more even though it worked fine with Vista 64.
The diagnostics said everything was OK, and actually I installed Vista and W7 in two different partitions and both systems are giving problem...
Try installing on another drive on another port like 3 or 4 and dual boot.
You shouldn't have any warranty remaining so you can say if you installed a GTX 490 graphics card and are having problems now. If so, remove it now and use the onboard X3000.
I just run Windows Debugger on the last minidump file and got the following:
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
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 *
Attempt to reset the display driver and recover from timeout failed.
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.
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
9243cf20 55 push ebp
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
9243cf20 55 push ebp
I cannot interpret it though... any help is most welcome!
I can only hope someone else does. Now I start to think of your memory, the memory hub and I/O controller hub. Do you have any temps for the hubs or fan speed and temp of the CPU? It's best to compare those and your voltages with original values. A short somewhere on your connections could make things increasingly unstable and erratic so anything you can swap out would help.