Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Random Restarts

Original Message
Name: Longspur
Date: November 30, 2007 at 01:39:46 Pacific
Subject: Random Restarts
OS: XP Media
CPU/Ram: amd sempron 2500 @GB Ram
Model/Manufacturer: generic
Comment:
My computer has been recently randomly restarting so I set XP to display the error message and it reads
"IRQL_NOT_LESS_OR_EQUAL"
stop 0x0000000a (0x00000028,0x00000002,0x00000000,0x00000000,0x804ea566)
begining dump of physical memory,physicalmemory dump complete.

Hopefully this looks familiar to someone cause it is quite annoying and becoming a serious problem for me.
Any help is greatly apprciated in advance.
Thank you
Longspur


Report Offensive Message For Removal


Response Number 1
Name: mountain
Date: November 30, 2007 at 07:33:53 Pacific
Subject: Random Restarts
Reply: (edit)
go into device manager, if you can and dump all drivers from everything.
reboot, let windows reload.
mebbe need to go to safemode to do that

Report Offensive Follow Up For Removal

Response Number 2
Name: XpUser4Real
Date: November 30, 2007 at 10:11:32 Pacific
Subject: Random Restarts
Reply: (edit)
a google search brought this up:
http://www.google.com/search?hl=en&...

Some HELP in posting on Cnet plus free progs and instructions Glad to Help!


Report Offensive Follow Up For Removal

Response Number 3
Name: beckrl
Date: November 30, 2007 at 17:04:22 Pacific
Subject: Random Restarts
Reply: (edit)
Longspur i use this site for any stop error.
http://aumha.org/a/stop.htm
Look at the end of the code number 0x0000000a (0A) and find it in the columns.
This will led you to MS.
http://support.microsoft.com/?kbid=...

Cause: Stop error 0x0000000A (Stop 0x0A) indicates that there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software.

I found also a quick fix is to recover windows.This link shows how to recover
http://support.microsoft.com/kb/307545
I use these in recovery console.

delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default

copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default

Hope this helps:)



Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Random Restarts

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




how to setup call of duty to joytok

WindowsME / HotMail Problem

Corrupt memory

Convert fat32 to Ntfs

Best WinMo phone of 2008


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC