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

Computer spontaneous reboot


  • Please log in to reply
20 replies to this topic

#1 AlesiaWinning

AlesiaWinning

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 25 March 2009 - 05:17 PM

Hello,

I'm new here and the reason to join you is unfortunately not very happy.
My problem is that the computer is rebooting spontaneously. I checked different topics here (http://www.bleepingcomputer.com/forums/topic52621.html) and on other forums and havenít found the answer.
Here are the details:
--------------
Computer: ASUS M2N bought in 2003
Microsoft Windows XP Pro, Service Pack 3
60 Gb hard drive is split in three parts: C: Program files, Swap and Data
Anti-virus Nod 32 and Lavasoft Ad Aware SE Personal
--------------
The computer reboots in various situations: when I turn it on in the morning just as soon as Windows logo appears (can restart several times in a row), while surfing on the net, watching a DVD, playing music or sitting idle. It can work ok for few days then reboot many times during one day.
The computer has almost 6 years, the problem started few months ago. No major changes in software, no hardware changes at all. SW - only updates of the versions of programs installed previously, as far as i remember.
I updated and ran the antispyware programs and found no infections. I supposed the restart can be due to the fact that I hadnít reinstalled it all since 2 years so reinstalled the OS a new hard drive in January 2009. Problem persisted. No viruses identified, HDD ventilation seems to be ok.
--------------
I got the message of the BSOD that is the same for 3 times it rebooted in 2 days when I unchecked ďautomatic restartĒ in Startup and Recovery Settings:

IRQL_NOT_LESS_OR_EQUAL
STOP: 0x0000000A (0xF88A92A0; 0x00000002; 0x00000001; 0x804D9BBA)


Since 5 days it changed and now I always get the

IRQL_NOT_LESS_OR_EQUAL
STOP: 0x0000000A (0xF8C691C0; 0x00000002; 0x00000001; 0x804D9B68)


I also went to Event Viewer and checked Errors codes (in System), there are plenty, most frequent are:

Event ID: 7000 / Event ID: 7 / Event ID: 1000 / Event ID: 10010
And other event IDs can happen: 1001, 1003, 17, 29, 4202, 4201, 14103, 108.

Last restart few minutes ago: no errors in Applications, one error in System that does not exactly correspond in time to the BSOD moment (3 minutes after BSOD)Ö

I have done memory tests (Memtest 86 and Windows memory diagnostics), both found no errors.

Where to search now? :thumbsup: Should I provide some more info?
Thank you

BC AdBot (Login to Remove)

 


#2 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:52 PM

Posted 25 March 2009 - 05:28 PM

Check your devices in Device Manager (Start > Run > type "devmgmt.msc" (without the quotes) and press Enter). Look for any "!", "?" or "X" symbols.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#3 AlesiaWinning

AlesiaWinning
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 26 March 2009 - 07:12 AM

Check your devices in Device Manager (Start > Run > type "devmgmt.msc" (without the quotes) and press Enter). Look for any "!", "?" or "X" symbols.


Thank you Budapest, I checked Device Manager, no conflicts, no "!", "?", "X" symbols, devices list looks ok.

Edited by AlesiaWinning, 26 March 2009 - 07:13 AM.


#4 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:52 PM

Posted 26 March 2009 - 06:03 PM

Try running through the steps given here:

http://www.bleepingcomputer.com/forums/top...ml#entry1181652
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#5 AlesiaWinning

AlesiaWinning
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 27 March 2009 - 02:39 PM

Ok, my homework for this WE, i'll report here about the results.

#6 AlesiaWinning

AlesiaWinning
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 29 March 2009 - 02:31 PM

Hello,

First, the virus scans didn't find anything abnormal: Panda reacted on cookies plus small .exe files i knew about (related to archiving prog, msn messenger - emoticones, an application for screenshots...). Lavasoft full scan: no errors.

Second, while looking for .dmp was surprised: no MEMORY.DMP under C:\WINDOWS, and in the C:\WINDOWS\Minidump I have only one minidump dated March 7th 2009 whereas the computer crashed tens of times since then. So i debugged the only .dmp I found.

Here are the details:



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


Loading Dump File [C:\WINDOWS\Minidump\Mini030709-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Mar 7 23:07:07.836 2009 (GMT+2)
System Uptime: 0 days 1:47:52.399
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
*** WARNING: Unable to verify timestamp for ialmdnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for ialmdnt5.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {82d8d5c0, 82c4fd28, 82b560b0, 1}

*** 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+120b4 )

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

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: 82d8d5c0, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 82c4fd28, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 82b560b0, 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: 82d8d5c0

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: wmplayer.exe

LAST_CONTROL_TRANSFER: from bf9ee5b4 to bfa130b4

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ef7c2df4 bf9ee5b4 e2451018 e2451018 ef7c2e20 ialmdev5+0x120b4
ef7c2e04 bf9db3a4 e2452e40 00000000 00000000 ialmdnt5+0xb5b4
ef7c2e20 bf8b919f e2452e40 00000000 00000000 ialmrnt5+0x63a4
ef7c2e5c bf805533 e2452e40 00000000 00000000 win32k!WatchdogDrvSynchronizeSurface+0x57
ef7c2e70 bf83695d e2452e40 00000000 00000000 win32k!PDEVOBJ::vSync+0x36
ef7c308c bf9e5ce3 e2452e40 e2450008 ef7c3760 win32k!EngCopyBits+0xf2
ef7c30b4 bf9e5b85 e2452e40 e1937e90 ef7c3760 ialmdnt5+0x2ce3
ef7c3630 bf9dad0e e2452e40 e1937e90 ef7c3760 ialmdnt5+0x2b85
ef7c36e8 bf805b86 e2452e40 e1937e90 ef7c3760 ialmrnt5+0x5d0e
ef7c3734 bf830c1e e2452e40 e1937e90 ef7c3760 win32k!WatchdogDrvCopyBits+0x53
ef7c3874 bf82bb06 00000001 e2b3dc90 00000000 win32k!GreSetDIBitsToDeviceInternal+0x95a
ef7c38ec 804de7ec 09010bed 00000000 00000044 win32k!NtGdiSetDIBitsToDeviceInternal+0xc1
ef7c38ec 7c90e4f4 09010bed 00000000 00000044 nt!KiFastCallEntry+0xf8
0007cbec 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: .thread 0xffffffff82d8d5c0 ; kb

FOLLOWUP_IP:
ialmdev5+120b4
bfa130b4 83e6fb and esi,0FFFFFFFBh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ialmdev5+120b4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ialmdev5

IMAGE_NAME: ialmdev5.DLL

DEBUG_FLR_IMAGE_TIMESTAMP: 40e46391

FAILURE_BUCKET_ID: 0xEA_IMAGE_ialmdev5.DLL_DATE_2004_07_01

BUCKET_ID: 0xEA_IMAGE_ialmdev5.DLL_DATE_2004_07_01

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

#7 hamluis

hamluis

    Moderator


  • Moderator
  • 55,726 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:52 AM

Posted 29 March 2009 - 02:35 PM

http://www.processlibrary.com/directory/files/ialmdev5/

From what I see, it appears that your onboard video drivers may be corrupt/damaged.

Louis

#8 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:52 PM

Posted 29 March 2009 - 06:16 PM

Try updating your video driver.

How to update a Windows hardware driver
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#9 AlesiaWinning

AlesiaWinning
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 30 March 2009 - 02:35 PM

http://www.processlibrary.com/directory/files/ialmdev5/

From what I see, it appears that your onboard video drivers may be corrupt/damaged.

Louis


Hello, this link brought me to Registry Booster that i run, and here is the results log attached.

Attached Files



#10 AlesiaWinning

AlesiaWinning
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 30 March 2009 - 02:41 PM

Try updating your video driver.

How to update a Windows hardware driver


I checked the version, and the video driver I currently have is the latest / the only one available at the Asus support page. It dates back to 2004 with no later updates on the manufacturer's site (Asus).

By the way during January reinstallation, the recent versions of all drivers have been downloaded and installed.

#11 hamluis

hamluis

    Moderator


  • Moderator
  • 55,726 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:52 AM

Posted 30 March 2009 - 03:57 PM

You seem to have missed the info on the file you named...and responded to the advertising. I would never suggest a program like the one advertised as a fix for anything...I believe it helps if users can see what a given file named as a culprit...is supposed to do or where it's supposed to be...in order to help rule out the possibility of malware.

FWIW: The primary reason that some may suggest updating a driver...is that drivers (or any other file) can be become damaged and not give any sign, other than the fact that the program/compoent does not function properly.

It's immaterial if you have the latest version installed...if that file is crippled or misbehaving.

Hence the suggestion to uninstall current drivers...and then reinstall/update.

Louis

#12 AlesiaWinning

AlesiaWinning
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 04 April 2009 - 01:49 PM

Try updating your video driver.

How to update a Windows hardware driver


I checked the version, and the video driver I currently have is the latest / the only one available at the Asus support page. It dates back to 2004 with no later updates on the manufacturer's site (Asus).

By the way during January reinstallation, the recent versions of all drivers have been downloaded and installed.


I redownloaded the video driver (the same i had and the latest available, though dating back to 2004) and updated it in the middle of the week, result : two crashed today, in the morning at launch (instead of launch) and in the afternoon, when being idle.

No more minidumps created, still only have the one form March 7th... May be i should take this one away (delete and saveguarg somewhere else) to force the computer to create a new one?

#13 hamluis

hamluis

    Moderator


  • Moderator
  • 55,726 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:52 AM

Posted 04 April 2009 - 02:23 PM

Did you uninstall the old drivers...before trying to update/install the downloaded drivers?

Louis

#14 AlesiaWinning

AlesiaWinning
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:52 PM

Posted 05 April 2009 - 04:44 AM

Did you uninstall the old drivers...before trying to update/install the downloaded drivers?

Louis


Yes, i uninstalled the driver with Control Panel / Remove Programs, and then installed the freshly downloaded one.
What surprises me is that the spontaneous reboot is the same before and after i completely reinstalled the OS on a new hard drive.

I think now: when changing the hard disk, we discovered that the ventilator grid was quite dusty, and took off the bottom cover to clean everything. Thus we saw there was a square copper plate lying over motherboard, near the processor, and unfixed. But it is not the processor heatsink. It was not clear where it should be fixed and what elements it serves, and we took it away to avoid occasional shortcuts. I didn't observe any changes (positive or negative) before or after taking it away. May it be related?

Olga

#15 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:52 PM

Posted 05 April 2009 - 04:55 PM

You could try monitoring your system temps with SIW (under Hardware > Sensors).
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users