My VAIO has been randomly rebooting itself when I try to shut it down or put on stand-by. After such crashes Windows XP displays a serious error dialog. Happened a few times already.



WinDbg identified ialmdev5.dll as the culprit based on one mini dump. Do I need to update the Intel 945GM drivers? Which ones should I go for if my motherboard is Phoenix Technologies R0020J4? The other dumps refer to win32k.sys as driver fault. I have not seen BSOD though. Help.

Here are a couple different ones. Advice would be highly appreciated.

moved to our Blue Screen Errors

Shame. Fewer people are gonna see it. Also, as stated in the first post, there has been no BSOD.

Keeps on happening. Help!

BTW, it's probably more appropriate to move the thread to the XP/2000 BSOD forum.

Both of these were cuased by iamlmdev.dll. Here is how to fix it

How to Fix Ialmdev5.dll Blue Screen Error

1. The first thing the user should do is identify the motherboard chipset and if ialmdev5.dll is a part of this component.
2. Next, download the driver you need from Intel Corporation’s website.
3. Save this driver in your computer.
4. Uninstall your current chipset drivers.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Mini031511-01.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;srv*e:\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.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Mar 15 06:39:16.234 2011 (GMT-4)
System Uptime: 0 days 2:16:28.933
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, {85c43da8, 86a9d568, 85f3cda0, 1}

Probably caused by : ialmdev5.DLL ( ialmdev5+1f2b2 )

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

0: 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: 85c43da8, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 86a9d568, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 85f3cda0, 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:  85c43da8

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  Skype.exe

LAST_CONTROL_TRANSFER:  from bf062344 to bf0622b2

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
a9408bdc bf062344 f629609c e2653000 bf048b4a ialmdev5+0x1f2b2
a9408c80 bf962fc1 a9408d00 e263c008 e1ba23f8 ialmdev5+0x1f344
a9408d00 e18bab78 00010000 00000001 a9408d58 win32k!WatchdogDdContextDestroy+0x3b
a9408d10 bf000e2a 04600006 00000000 00000000 0xe18bab78
a9408d58 8054167c 0012fb18 0012fb00 7c90e514 dxg!DxD3dContextDestroy+0x34
a9408d58 7c90e514 0012fb18 0012fb00 7c90e514 nt!KiFastCallEntry+0xfc
0012fb00 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  .thread 0xffffffff85c43da8 ; kb

FOLLOWUP_IP: 
ialmdev5+1f2b2
bf0622b2 8b16            mov     edx,dword ptr [esi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ialmdev5+1f2b2

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
---------

Yesterday I tried updating the chipset driver. All that changed in the display adapter settings was the date (15/02/2008) but not the version (it is still 6.14.10.4926). The serious error has come up today yet again. The dump is attached. Any ideas? Another odd thing is that I have two display adapters listed in the display manager. They are exactly the same, including their driver dates and versions.

This one was caused by igxpgd32.dll (part of your graphics driver). It was a memory exception.

I would do two things.

1-re-install the video driver this way

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.


2- Run memtest to make sure the memory is ok.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Mini032511-01.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;srv*e:\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.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Mar 25 05:29:24.343 2011 (GMT-4)
System Uptime: 0 days 0:00:48.031
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...
Unable to load image igxpgd32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpgd32.dll
*** ERROR: Module load completed but symbols could not be loaded for igxpgd32.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf031135, a938a2d4, 0}

*** WARNING: Unable to verify timestamp for igxprd32.dll
*** ERROR: Module load completed but symbols could not be loaded for igxprd32.dll
Probably caused by : igxpgd32.dll ( igxpgd32+d135 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf031135, The address that the exception occurred at
Arg3: a938a2d4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
igxpgd32+d135
bf031135 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

TRAP_FRAME:  a938a2d4 -- (.trap 0xffffffffa938a2d4)
ErrCode = 00000000
eax=01081fb0 ebx=01081fb0 ecx=00000002 edx=00000007 esi=01082000 edi=a938a3a0
eip=bf031135 esp=a938a348 ebp=a938a3b0 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
igxpgd32+0xd135:
bf031135 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  igfxsrvc.exe

LAST_CONTROL_TRANSFER:  from bf030388 to bf031135

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
a938a3b0 bf030388 e1dca808 00000048 01081fb0 igxpgd32+0xd135
a938a960 bf0369db e1dca808 00000048 01081fb0 igxpgd32+0xc388
a938aa04 bf03f6ba e2679450 00435044 00000048 igxpgd32+0x129db
a938aa2c bf01a7b1 e2679450 00435044 00000048 igxpgd32+0x1b6ba
a938aa5c bf8988a5 e2679450 00435044 00000048 igxprd32+0x87b1
a938aaa8 bf86ad30 e2679450 00435044 00000048 win32k!WatchdogDrvEscape+0x46
a938aad4 bf86a9c6 e2679450 00435044 00000048 win32k!PDEVOBJ::Escape+0x37
a938ac44 bf86afde e359c008 00435044 00000048 win32k!GreExtEscape+0x4e0
a938ad3c 8054167c 0a010248 00000000 00000000 win32k!NtGdiExtEscape+0x336
a938ad3c 7c90e514 0a010248 00000000 00000000 nt!KiFastCallEntry+0xfc
0012f544 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igxpgd32+d135
bf031135 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igxpgd32+d135

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igxpgd32

IMAGE_NAME:  igxpgd32.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  47b60024

FAILURE_BUCKET_ID:  0x8E_igxpgd32+d135

BUCKET_ID:  0x8E_igxpgd32+d135

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf031135, The address that the exception occurred at
Arg3: a938a2d4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
igxpgd32+d135
bf031135 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

TRAP_FRAME:  a938a2d4 -- (.trap 0xffffffffa938a2d4)
ErrCode = 00000000
eax=01081fb0 ebx=01081fb0 ecx=00000002 edx=00000007 esi=01082000 edi=a938a3a0
eip=bf031135 esp=a938a348 ebp=a938a3b0 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
igxpgd32+0xd135:
bf031135 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  igfxsrvc.exe

LAST_CONTROL_TRANSFER:  from bf030388 to bf031135

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
a938a3b0 bf030388 e1dca808 00000048 01081fb0 igxpgd32+0xd135
a938a960 bf0369db e1dca808 00000048 01081fb0 igxpgd32+0xc388
a938aa04 bf03f6ba e2679450 00435044 00000048 igxpgd32+0x129db
a938aa2c bf01a7b1 e2679450 00435044 00000048 igxpgd32+0x1b6ba
a938aa5c bf8988a5 e2679450 00435044 00000048 igxprd32+0x87b1
a938aaa8 bf86ad30 e2679450 00435044 00000048 win32k!WatchdogDrvEscape+0x46
a938aad4 bf86a9c6 e2679450 00435044 00000048 win32k!PDEVOBJ::Escape+0x37
a938ac44 bf86afde e359c008 00435044 00000048 win32k!GreExtEscape+0x4e0
a938ad3c 8054167c 0a010248 00000000 00000000 win32k!NtGdiExtEscape+0x336
a938ad3c 7c90e514 0a010248 00000000 00000000 nt!KiFastCallEntry+0xfc
0012f544 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igxpgd32+d135
bf031135 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igxpgd32+d135

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igxpgd32

IMAGE_NAME:  igxpgd32.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  47b60024

FAILURE_BUCKET_ID:  0x8E_igxpgd32+d135

BUCKET_ID:  0x8E_igxpgd32+d135

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

0: kd> lmvm igxpgd32
start    end        module name
bf024000 bf04f000   igxpgd32 T (no symbols)           
    Loaded symbol image file: igxpgd32.dll
    Image path: igxpgd32.dll
    Image name: igxpgd32.dll
    Timestamp:        Fri Feb 15 16:12:04 2008 (47B60024)
    CheckSum:         0002E91D
    ImageSize:        0002B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm igxpgd32
start    end        module name
bf024000 bf04f000   igxpgd32 T (no symbols)           
    Loaded symbol image file: igxpgd32.dll
    Image path: igxpgd32.dll
    Image name: igxpgd32.dll
    Timestamp:        Fri Feb 15 16:12:04 2008 (47B60024)
    CheckSum:         0002E91D
    ImageSize:        0002B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The recommended utility does not support Intel drivers. Is it safe to remove them through Device Manager > Display Adapters > Driver > Uninstall? Once again, I have two identical adapters listed there. The only difference is the location.

PCI bus 0, device 2, function 0
PCI bus 0, device 2, function 1

Which slot is the card in?

What utility are you running when you see the error?

As can be seen in the first post, it is an integrated video card (Intel 945GM). Errors always come up upon XP load.

I have opened this thread to see if we cant get you some additional help


Ken

Hi imusorka,

What is the exact model vaio you have?

Also which Intel chipset does it have?