Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

ialmrnt5 infinite loop problems for my Dell Dim E510


  • Please log in to reply
9 replies to this topic

#1 andyou

andyou

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:07:24 AM

Posted 15 August 2009 - 02:36 AM

Hi, thanks in advance for any help with this. Several days ago my Dell Dimension E510 crashed while playing a game. Since then I've been getting blue screens about ialmrnt5 and infinite loop problems. I've checked both at Dell and Intel to get any updates for my 82945G Express Chipset Family (as well as anything else.) Intel's site has been particularly unhelpful because it keeps directing me to drivers that my computer rejects.

I checked the computer with several anti-virus and anti-spyware programs. Also I've used a couple registry cleaners to optimize my system. I've been able to lessen the problem somewhat by lowering my hardware acceleration, increasing my virtual memory and installing an earlier driver. (System restore didn't help at all.) With these adjustments my computer works somewhat better, however as soon as it's idle, short horizontal streaks appear on the screen, and if I don't reboot, the computer crashes with the notice about ialmrnt5 or an infinite loop.

My computer info is:

AWC System Information Report

Computer System
Computer Name DELL-37BBD154D0
User Name DELL-FVP2W81
Organization
Operating System
OS Name Microsoft Windows XP Professional
OS Version 5.1.2600
ServicePack 3.0
Product ID 76487-OEM-0011903-00825
System Uptime 8/14/2009 10:23:16 PM
Internet Explorer Version 8.0.6001.18702
Microsoft DirectX Version 9.0c (4.09.00.0904)
OpenGL Version 5.1.2600.5512 (xpsp.080413-0845)
Free Physical Memory 142 MB
Free Page File 631 MB
Free Virtual Memory 2008 MB
Registry
Maximum Size 56MB
Current Size 8MB
Status OK
Center Processor
CPU Name Intel® Pentium® 4 CPU 3.00GHz
Code Name Model 4, Stepping 3
Manufacturer GenuineIntel
Current Clock Speed 2992Mhz
Max Clock Speed 2992Mhz
Voltage 1.5V
External Clock 800Mhz
Serial Number BFEBFBFF00000F43
CPU ID x86 Family 15 Model 4 Stepping 3
Socket Designation Microprocessor
16KB
2048KB
Motherboard
Model 0WG261
Manufacturer Dell Inc.
Serial Number ..CN6986161N003A.
BIOS Name Phoenix ROM BIOS PLUS Version 1.10 A07
BIOS Vendor Dell Inc.
SMBIOS Version A07
BIOS Date 1/8/2007
BIOS Features
PCI is supported Yes
Plug and Play is supported Yes
APM is supported Yes
BIOS is Upgradable (Flash) Yes
BIOS shadowing is allowed Yes
Boot from CD is supported Yes
Selectable Boot is supported Yes
EDD (Enhanced Disk Drive) Specification is supported Yes
Int 13h - Japanese Floppy for Toshiba 1.2mb (3.5, 360 RPM) is supported Yes
Int 5h, Print Screen Service is supported Yes
Int 9h, 8042 Keyboard services are supported Yes
Int 14h, Serial Services are supported Yes
Int 17h, printer services are supported Yes
ACPI supported Yes
USB Legacy is supported Yes
LS-120 boot is supported Yes
Memory Resource
Total Memory 502 MB
Used Memory 353 MB
Free Memory 149 MB
Memory Usage 70%
Physical Memory
Memory Bank
Description Physical Memory 0
Device Location DIMM_1
Capacity 256 MB
Speed 400Mhz
Manufacturer NULL
Data Width 64bit
Memory Type Unknown
Form Factor DIMM
Physical Memory
Memory Bank
Description Physical Memory 2
Device Location DIMM_2
Capacity 256 MB
Speed 400Mhz
Manufacturer NULL
Data Width 64bit
Memory Type Unknown
Form Factor DIMM
Disk drive
Name SAMSUNG HD160JJ/P
Media Type Fixed hard disk media
Capacity 159GB
Interface Type IDE
Partitions 1
Total Cylinders 19452
Total Heads 255
Total Sectors 312496380
Total Tracks 4960260
Tracks Per Cylinder 255
Sectors Per Track 512
Bytes Per Sector 63
S.M.A.R.T Support Yes
Current Temperature 48C (118.4F)
CD-ROM Drive
Name _NEC DVD+-RW ND-3530A
Drive D:
Transfer Rate NULL
Status OK
CD-ROM Drive
Name AXANU 896N89MR4 SCSI CdRom Device
Drive E:
Transfer Rate NULL
Status OK
IDE Controller
Name Intel® 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
Manufacturer Intel
Status OK
IDE Controller
Name Primary IDE Channel
Manufacturer (Standard IDE ATA/ATAPI controllers)
Status OK
IDE Controller
Name Intel® 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
Manufacturer Intel
Status OK
IDE Controller
Name Primary IDE Channel
Manufacturer (Standard IDE ATA/ATAPI controllers)
Status OK
IDE Controller
Name Secondary IDE Channel
Manufacturer (Standard IDE ATA/ATAPI controllers)
Status OK
Video Adapter
Name Intel® 82945G Express Chipset Family
Video Processor Intel® 82945G Express Chipset Family
Manufacturer Intel Corporation
Video Architecture VGA
DAC Type Internal
Memory Size 224MB
Memory Type Unknown
Video Mode 1680 x 1050 x 4294967296 colors
Current Refresh Rate 60Hz
Driver Version 6.14.10.4543
Driver Date 3/24/2006 3:47:06 AM
Monitor
Name Plug and Play Monitor
Screen Height 1050
Screen Width 1680
Status OK
Local Area Connection
Product Name Intel® PRO/100 VE Network Connection
Driver File E100B
Manufacturer Intel
MAC Address 00:13:72:B7:AC:07
Sound Device
Name SigmaTel High Definition Audio CODEC
Manufacturer SigmaTel
Status OK
Keyboard
Name USB Human Interface Device
Description Enhanced (101- or 102-key)
Function Keys 12
Status OK
USBController
Product Name Intel® 82801G (ICH7 Family) USB Universal Host Controller - 27C8
Manufacturer Intel
Protocol Supported Universal Serial Bus
Status OK
USBController
Product Name Intel® 82801G (ICH7 Family) USB Universal Host Controller - 27C9
Manufacturer Intel
Protocol Supported Universal Serial Bus
Status OK
USBController
Product Name Intel® 82801G (ICH7 Family) USB Universal Host Controller - 27CA
Manufacturer Intel
Protocol Supported Universal Serial Bus
Status OK
USBController
Product Name Intel® 82801G (ICH7 Family) USB Universal Host Controller - 27CB
Manufacturer Intel
Protocol Supported Universal Serial Bus
Status OK
USBController
Product Name Intel® 82801G (ICH7 Family) USB2 Enhanced Host Controller - 27CC
Manufacturer Intel
Protocol Supported Universal Serial Bus
Status OK
***********************************

Following a post I read at your site, my debugging info is:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini081409-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Aug 14 22:17:08.906 2009 (GMT-7)
System Uptime: 0 days 2:01:02.907
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image ialmdev5.DLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ialmdev5.DLL
*** ERROR: Module load completed but symbols could not be loaded for ialmdev5.DLL
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {82454020, 81fd36c0, 82a72160, 1}

*** WARNING: Unable to verify timestamp for ialmdnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmdnt5.dll
*** WARNING: Unable to verify timestamp for ialmrnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmrnt5.dll
Probably caused by : ialmdev5.DLL ( ialmdev5+2a6dc )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 82454020, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 81fd36c0, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 82a72160, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

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


FAULTING_THREAD: 82454020

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 3

BUGCHECK_STR: 0xEA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from bf8b90ef to bfa306dc

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a99f9a14 bf8b90ef e13934e0 00000000 00000000 ialmdev5+0x2a6dc
a99f9a50 bf8053ae e13934e0 00000000 00000000 win32k!WatchdogDrvSynchronizeSurface+0x57
a99f9a64 bf836921 e13934e0 00000000 00000000 win32k!PDEVOBJ::vSync+0x36
a99f9c80 bf9e7193 e13934e0 e252e008 00000000 win32k!EngCopyBits+0xf2
a99f9ca8 bf9e6df7 e13934e0 e3c6ea08 00000000 ialmdnt5+0x3193
a99fa1f0 bf9f96e0 e13934e0 e3c6ea08 00000000 ialmdnt5+0x2df7
a99fa218 bf9db45c e13934e0 e3c6ea08 00000000 ialmdnt5+0x156e0
a99fa2d0 bf805a01 e13934e0 e3c6ea08 00000000 ialmrnt5+0x645c
a99fa31c bf809c99 e13934e0 e3c6ea08 00000000 win32k!WatchdogDrvCopyBits+0x53
a99fa3b0 8054162c e13934d0 e11df008 e118b908 win32k!NtGdiBitBlt+0x51c
a99fa3b0 7c90e514 e13934d0 e11df008 e118b908 nt!KiFastCallEntry+0xfc
0381e6cc 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: .thread 0xffffffff82454020 ; kb

FOLLOWUP_IP:
ialmdev5+2a6dc
bfa306dc 8b54f744 mov edx,dword ptr [edi+esi*8+44h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ialmdev5+2a6dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ialmdev5

IMAGE_NAME: ialmdev5.DLL

DEBUG_FLR_IMAGE_TIMESTAMP: 44230744

FAILURE_BUCKET_ID: 0xEA_IMAGE_ialmdev5.DLL_DATE_2006_03_23

BUCKET_ID: 0xEA_IMAGE_ialmdev5.DLL_DATE_2006_03_23

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

Any help I could get on this would be greatly appreciated.

Thanks,

Allen

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,758 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:24 AM

Posted 15 August 2009 - 08:28 AM

Rather than pile driver files on top of one another...try uninstalling the current drivers...and then reinstalling either the original video drivers or updated ones.

Louis

You have a Dell system...get your drivers from the Dell website.

Edited by hamluis, 15 August 2009 - 08:29 AM.


#3 andyou

andyou
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:07:24 AM

Posted 15 August 2009 - 03:06 PM

Hi Louis,

Thanks for replying. I uninstalled my display driver while in safe mode. Rebooted and then installed the recommended Dell driver. I also reinstalled the latest Dell bios. Unfortunately the problem persists:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini081509-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Aug 15 12:53:31.468 2009 (GMT-7)
System Uptime: 0 days 0:35:50.015
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image ialmdev5.DLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ialmdev5.DLL
*** ERROR: Module load completed but symbols could not be loaded for ialmdev5.DLL
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {8246e020, 82559330, 82bdbad8, 1}

*** WARNING: Unable to verify timestamp for ialmdnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmdnt5.dll
*** WARNING: Unable to verify timestamp for ialmrnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmrnt5.dll
Probably caused by : ialmdev5.DLL ( ialmdev5+1f5ca )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8246e020, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 82559330, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 82bdbad8, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

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


FAULTING_THREAD: 8246e020

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 6

BUGCHECK_STR: 0xEA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from bf06262e to bf0625ca

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a9395eac bf06262e 8292c000 a9396174 e1a621d8 ialmdev5+0x1f5ca
a9395f24 bf8b90ef e1a621d8 00000000 00000000 ialmdev5+0x1f62e
a9395f60 bf8053ae e1a621d8 00000000 00000000 win32k!WatchdogDrvSynchronizeSurface+0x57
a9395f74 bf819177 e1a621d8 00000000 00000000 win32k!PDEVOBJ::vSync+0x36
a93961a0 bf02493b e256e008 e2a52e00 a93967c8 win32k!EngTransparentBlt+0xaa
a93966c8 bf036e5b e1a621d8 e2a52e00 a93967c8 ialmdnt5+0x393b
a93966f8 bf0133db e1a621d8 e2a52e00 a93967c8 ialmdnt5+0x15e5b
a9396740 bf81953f e1a621d8 e2a52e00 a93967c8 ialmrnt5+0x13db
a9396794 bf85801d e1a621d8 e2a52e00 a93967c8 win32k!WatchdogDrvTransparentBlt+0x59
a9396900 8054162c e23e8f58 e1a621c8 bf9a6328 win32k!NtGdiTransparentBlt+0x729
a9396900 7c90e514 e23e8f58 e1a621c8 bf9a6328 nt!KiFastCallEntry+0xfc
00dded60 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: .thread 0xffffffff8246e020 ; kb

FOLLOWUP_IP:
ialmdev5+1f5ca
bf0625ca 85c0 test eax,eax

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ialmdev5+1f5ca

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ialmdev5

IMAGE_NAME: ialmdev5.DLL

DEBUG_FLR_IMAGE_TIMESTAMP: 44230744

FAILURE_BUCKET_ID: 0xEA_IMAGE_ialmdev5.DLL_DATE_2006_03_23

BUCKET_ID: 0xEA_IMAGE_ialmdev5.DLL_DATE_2006_03_23

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

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,758 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:24 AM

Posted 15 August 2009 - 05:11 PM

I would do a search for ialmdev5.DLL and manually delete it.

Then reboot.

Louis

#5 andyou

andyou
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:07:24 AM

Posted 15 August 2009 - 07:57 PM

Found Windows\system32 had more than one version of ialmdev5.DLL. I deleted the version that wasn't the installed driver. Hopefully that will help. If the crashes continue I'll try deleting the other ialmdev5.DLL. Thanks again.

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 55,758 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:24 AM

Posted 15 August 2009 - 08:25 PM

Let us know how it turns out :thumbsup:.

Louis

#7 andyou

andyou
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:07:24 AM

Posted 15 August 2009 - 10:54 PM

I was pretty hopeful, but it did not work. Here's the dump from my last crash:

icrosoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini081509-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Aug 15 21:06:58.093 2009 (GMT-7)
System Uptime: 0 days 0:45:27.809
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image ialmdev5.DLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ialmdev5.DLL
*** ERROR: Module load completed but symbols could not be loaded for ialmdev5.DLL
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {821c7020, 82514008, 8267cb80, 1}

*** WARNING: Unable to verify timestamp for ialmdnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmdnt5.dll
*** WARNING: Unable to verify timestamp for ialmrnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmrnt5.dll
Probably caused by : ialmdev5.DLL ( ialmdev5+2a6e0 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 821c7020, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 82514008, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 8267cb80, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

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


FAULTING_THREAD: 821c7020

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 8

BUGCHECK_STR: 0xEA

PROCESS_NAME: Autumn's Treasu

LAST_CONTROL_TRANSFER: from bf8b90ef to bf06d6e0

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a99f2888 bf8b90ef e1a237c8 00000000 00000000 ialmdev5+0x2a6e0
a99f28c4 bf8053ae e1a237c8 00000000 00000000 win32k!WatchdogDrvSynchronizeSurface+0x57
a99f28d8 bf836932 e1a237c8 00000000 00000000 win32k!PDEVOBJ::vSync+0x36
a99f2af4 bf024193 e35a3a50 e259f008 00000000 win32k!EngCopyBits+0x103
a99f2b1c bf023df7 e35a3a50 e1a237c8 00000000 ialmdnt5+0x3193
a99f3064 bf0366e0 e35a3a50 e1a237c8 00000000 ialmdnt5+0x2df7
a99f308c bf01845c e35a3a50 e1a237c8 00000000 ialmdnt5+0x156e0
a99f3144 bf805a01 e35a3a50 e1a237c8 00000000 ialmrnt5+0x645c
a99f3190 bf8baa4d e35a3a50 e1a237c8 00000000 win32k!WatchdogDrvCopyBits+0x53
a99f31d8 bf850be2 bf8059b5 a99f3400 e35a3a50 win32k!OffCopyBits+0x7d
a99f3298 bf8c5fa1 00000000 a99f3400 e35a3a50 win32k!vSpReadFromScreen+0x147
a99f3330 bf827d29 e36f68c8 a99f3400 e35a3a50 win32k!vSpSmallUnderlayCopy+0xd0
a99f3418 bf938f9f e259f048 00000010 00000015 win32k!bSpUpdatePosition+0x33e
a99f3448 bf939153 e1a237c8 0000016e 0000019a win32k!EngMovePointer+0x140
a99f347c bf84ac52 e1a237c8 e28e9d50 00000000 win32k!EngSetPointerShape+0x172
a99f3514 bf84a6e6 e259f008 e28e9d40 00000000 win32k!vSetPointer+0x3e3
a99f3540 bf800daa 82c37178 e25d17d0 00000000 win32k!GreSetPointer+0x66
a99f356c bf8244b4 bbea06e8 bbea06e8 0000000c win32k!zzzUpdateCursorImage+0x1aa
a99f357c bf8264a5 bf9abdc0 00000000 a99f3610 win32k!zzzSetFMouseMoved+0xd5
a99f3598 bf825b98 bbea06e8 0000000c bf9abdc0 win32k!zzzInvalidateDCCache+0x37
a99f35e0 bf8241c9 bf9abdc0 00000000 bbf02818 win32k!zzzBltValidBits+0xfa
a99f3638 bf826eec bbea06e8 00000000 e13766b0 win32k!xxxEndDeferWindowPosEx+0x13a
a99f3658 bf91ec35 bbf02818 00000001 00000000 win32k!xxxSetWindowPos+0x101
a99f36e4 bf853c70 00000000 00000106 bbf02818 win32k!xxxOldNextWindow+0x4a2
a99f3714 bf80bb20 bbf02818 0000f050 0000001b win32k!xxxSysCommand+0x1db
a99f3774 bf80ec77 bbf02818 00000112 0000f050 win32k!xxxRealDefWindowProc+0xc97
a99f378c bf820a45 bbf02818 00000112 0000f050 win32k!xxxWrapRealDefWindowProc+0x16
a99f37a8 bf80eebe bbf02818 00000112 0000f050 win32k!NtUserfnNCDESTROY+0x27
a99f37e0 8054162c 00220122 00000112 0000f050 win32k!NtUserMessageCall+0xae
a99f37e0 7c90e514 00220122 00000112 0000f050 nt!KiFastCallEntry+0xfc
0013ece8 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: .thread 0xffffffff821c7020 ; kb

FOLLOWUP_IP:
ialmdev5+2a6e0
bf06d6e0 83e2c0 and edx,0FFFFFFC0h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ialmdev5+2a6e0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ialmdev5

IMAGE_NAME: ialmdev5.DLL

DEBUG_FLR_IMAGE_TIMESTAMP: 44230744

FAILURE_BUCKET_ID: 0xEA_IMAGE_ialmdev5.DLL_DATE_2006_03_23

BUCKET_ID: 0xEA_IMAGE_ialmdev5.DLL_DATE_2006_03_23

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

Edited by andyou, 15 August 2009 - 11:15 PM.


#8 hamluis

hamluis

    Moderator


  • Moderator
  • 55,758 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:24 AM

Posted 16 August 2009 - 10:05 AM

The only thing that I see now...is a reference to a game called Autumn's Treasures, http://www.google.com/search?hl=en&q=a...q=&aqi=g-s2.

If you have such installed, I suggest you remove it and then reinstall.

Louis

#9 andyou

andyou
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:07:24 AM

Posted 16 August 2009 - 01:30 PM

Autumn's Treasures was installed days after this problem started. The computer crashed because it now can't handle certain graphics issues. For example, the aquarium screensaver that I've always run now no longer works.

#10 hamluis

hamluis

    Moderator


  • Moderator
  • 55,758 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:24 AM

Posted 16 August 2009 - 02:12 PM

Regardless of when it was installed...if you review the contents of the crash report, you will see that it's fingered as not contributing to system functionality.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users