Link to home
Start Free TrialLog in
Avatar of BabalooInternet
BabalooInternet

asked on

NEW COMPUTER RANDOMLY REBOOTS--BSOD!!!!

I´ve just build a new computer:

P4 Prescott 2.8Ghz 800Mhz 1Mb L2
MOBO: Gigabyte GA8S648FXL
512MB DDR 333 x1
80GB Seagate UDMA 7200 rpm
Radeon 7000 64DDR/TV/DVI
Modem Creative HSP 56K V.92 PCI
Windows XP Home Oem
350W  Powersup

The Computer randomly rebooted after the first time I installed the operating system.  I thought it was a virus at first after the "Computer is Shutting down" Message appeared.  I reinstalled the OS and it only started to happen after I installed Service Pack 2.  Thought that was the problem but not.  I then tried a copy of windows Xp Pro and I thought it worked at first but then it happened again.  There was some errors on the harddrive during a Scandisk and I replaced the harddrive with a new one.  Reinstalled XP Home again and the the BSOD appeared after the "Network Configuration" window during the installation.  It happened three times and and the fourth time the installation finished.

BSOD:

IRQL_NOT_LESS_OR_EQUAL

Technical information
***Stop: 0x0000000A (0x0000FE6C, 0x00000002, 0x00000000, 0x804E35Ef)

Everytime after the computer reboots the message appears: "The system recovered from a serious error"
Does anyone know what causes this and how can I solve this problem??
Thank you
BabalooInternet
Avatar of Luc Franken
Luc Franken
Flag of Netherlands image

Hi BabalooInternet,

Most likely bad RAM in this case. But to start:
1) Reset your BIOS to defaults
2) Reseat all hardware in your computer
3) Check if no shortages against the case are made by the motherboard

Greetings,

LucF
Avatar of DoTheDEW335
DoTheDEW335

Troubleshooting a Stop 0x0000000A error in Windows XP
http://support.microsoft.com/?kbid=314063

and

 Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL

The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.
Interpreting the Message

This Stop message has four parameters:

   1. Memory address that was improperly referenced.
   2. IRQL that was required to access the memory.
   3. Type of access (0x00000000 = read operation, 0x00000001 = write operation).
   4. Address of the instruction that attempted to reference memory specified in parameter 1.

If the last parameter is within the address range of a device driver used on your system, you can determine which device driver was running when the memory access occurred. You can typically determine the driver name by reading the line that begins with:

**Address 0xZZZZZZZZ has base at <address>- <driver name>

If the third parameter is the same as the first parameter, a special condition exists in which a system worker routine, carried out by a worker thread to handle background tasks known as work items, returned at a higher IRQL. In that case, some of the four parameters take on new meanings:

   1. Address of the worker routine.
   2. Kernel interrupt request level (IRQL).
   3. Address of the worker routine.
   4. Address of the work item.

Resolving the Problem

The following suggestions are specific to Stop 0xA errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

    * A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
    * A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.
    * If you encounter a Stop 0xA message while upgrading to Windows XP Professional, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP Professional, contact the hardware manufacturer to obtain compatible updates. For more information about simplifying your system for troubleshooting purposes, see " Troubleshooting Concepts and Strategies" and "Troubleshooting Startup" in this book.

For more information about Stop 0xA messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x0000000A, and 0xA.

http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_hwpg.asp

you can test it with memtest86+ :

http://www.memtest.org/            
do you have a PCI USB 2.0 card by any chance?   I was working on a client's computer the other day, and found out the root of his issue was with the USB card he had installed.   Popped it out and BAM...started working again.

I'd recommend doing a hardware trial and error.
Remove all nonessential parts (this means removing anything PCI, and leaving only one stick of RAM).

Do a reboot, if it loads up, it means there is a specific piece that is causing your issues.   Keep rebooting and adding individual parts until it crashes again.  The last piece of hardware that you reinstalled is going to be the one that is causing the issue.

er correction, the last poiece that you reinstalled right before a crash again.   lol
Avatar of BabalooInternet

ASKER

Wel, first of all, thank you for all that replied.

To LucF:I reset the bios, reseated all hardware, and made sure there was no bad contact anyware, but nothing helped.  I also had the suspicion that it was the memory but was not sure (as it is brand new).

But I did get the folowing BSOD message:

A problem has been detected and windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Run system diagnostic utillity supplied by your hardware menufacturer- In particuler, run a memory check, and check for faulty or mismatched memory. Try changing video adaptors.

Disable or remove any newly installed hardware and drivers. Disable or remove any newly installed software.  If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advance Startup options, and select safe mode.

Technical Information:

***Stop: 0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000)

After I rebooted the message appeared again "The system recovered from a serious error" and also after a manual reboot.

After I got this BSOD, I recon that it MUST be the memory.
I swapped it with a old memory from my own computer, 512mb DDR 400, and it has NOT rebooted itself until now. (for the last three Hours).
My own computer also had not show any problems at all, wich means the memory is NOT defective, but why should the frequency of the memory make any difference?? What would be the problem then, if the memory is working fine??
Still, Lucf has been the closest so far, but I have to wait and see if the problem is solved.
ASKER CERTIFIED SOLUTION
Avatar of Luc Franken
Luc Franken
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
<< What would be the problem then, if the memory is working fine??>>
Motherboard/Power supply/CPU could all be culprits

If you read the info I posted it says go through all your hardware.
I want to know your program configuration
Run  msinfo32 and navigate to Hardware Resources > IRQs. Click anywhere in the right pane.  Press CTRL-A and then CTRL-C. Copy that data to the clipboard and paste that data here.

I also want to know your software list
Run  msinfo32 and navigate to Software > Program Group. Click anywhere in the right pane.  Press CTRL-A and then CTRL-C. Copy that data to the clipboard and paste that data here.

cpc2004
check your cpu cooling if you're getting random reboots.  Modern BIOSes will report cpu temp (even after a reboot it'll be close enough!) - you should be seeing about 40 degrees.  If it's near 70, watch out!  Normally they just reboot though, no time for a BSOD!

but I'd suspect the RAM from what you've said (follow the advice above to check it out....)

I had a system that was fine for 9 months, then rebooted randomly.  Either stick of 512 displayed the fault, so I thought it wasn't the RAM.  Till I ran memtest, found 64000 errors on the first stick, and 30000 on the 2nd!

if you're really sure the RAM's good, then the mobo is next...
Thanks again fo all that replied.

It was a Memory Compatibility problem. Credit go's to LucF.

MOBO: Gigabyte GA8S648FXL

Memory that's not Compatible:

Elixir
M2U51264DS88A1F-6K
512MB DDR 333MHz CL 2.5

Memory That is Compatible:

Elixir
M2U51264DS8HB3G-5T
512MB DDR 400MHz CL3

Thanks
BabalooInternet
Glad to help :)

LucF