my broken computer: How to resolve my BSOD?

Mitth · Post by **Mitth** » 2005-03-17 03:14pm

Well, my computer died after a short power outage (see vent in HOS), and now gives me a bluescreen when I try to load windows. The message is as follows:

Code: Select all

*** STOP: 0x0000000A (0x00059000, 0x0000001D, 0x00000000, 0x804F3312)
IRQL_NOT_LESS_OR_EQUAL

*** Address 804F3312 base at 80400000, DateStamp 41773335 - ntoskrnl.exe

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

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows 2000 updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. Check your hard drive to make sure it is properly configured and terminated. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Refer to your Getting Started manual for more information on troubleshooting Stop errors.

Anyone have any suggestions? The computer hangs when I attempt to enter Safe Mode. I am trying to find my boot disks so I can run chkdsk, as I was downloading and moving some data around when the thing died, which might have been part of the problem. Until then, I don't know what to do.

Vendetta · Post by **Vendetta** » 2005-03-17 03:58pm

If you can't even get into safe mode, you're kinda up shit creek unless you have the OS cd to hand.

Usually this error just means a hosed driver or dodgy piece of hardware, but if it's being thrown up by ntoskrnl.exe, it pretty much means Windows is buggered.

If you can find the OS CD, you have a couple of choices, running chkdsk /r is one thing to try, if it can descrabble and restore the HDD, you might be able to get back in. If not, you could try extracting the file manually and replacing the borked one, but that might just throw up a new error for your amusement and enjoyment.

jcow79 · Post by **jcow79** » 2005-03-17 05:20pm

One thing I would try would be to pull out any non-essential cards from the computer. (Sounds, modem, network card) You only need a video card for the thing to POST. If any devices are "on-board" meaning they are built on to the motherboard, disable them in the bios. Then see if you can boot into safemode or even boot up normally.

Psycho Smiley · Post by **Psycho Smiley** » 2005-03-17 06:15pm

Basically what Vendetta said. The power failure caused a critical Windows driver to die. If you can't get chkdsk to help, your install is borked. Try a repair and/or reinstall.

From Googling the failed driver:

ntoskrnl - ntoskrnl.exe - Process Information

Process File: ntoskrnl or ntoskrnl.exe
Process Name: Microsoft Boot Up Kernel

Description:
ntoskrnl.exe is a critical process in the boot-up cycle of your computer...

From MS on the error message:

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.

Mitth · Post by **Mitth** » 2005-03-19 11:08am

I figured I'd try what Vendetta suggested first, as it seems easiest. I can't find a bootable CD with chkdsk on it. I can't use a floppy, as my dad's computer lacks a floppy drive.

Feh, I could make a CD myself, I suppose. I hate to use a whole 700 MB CD for a few megabytes of files.

Anyway, thanks very much for the help everyone. I might try to repair the installation next.

When I boot into Repair Mode from the Win 2k CD, I get another bluescreen error. But I'll keep working on it.

MKSheppard · Post by **MKSheppard** » 2005-03-19 11:12am

Had something like this happen to me. Reinstall Windows 2000, it will be nice enough to keep all of your old Windows 2000 user files in C:\Documents and Settings and will make a new C:\Documents and Settings folder...

Vendetta · Post by **Vendetta** » 2005-03-19 12:47pm

Mitth wrote: When I boot into Repair Mode from the Win 2k CD, I get another bluescreen error. But I'll keep working on it.

You get a bluescreen when you're accessing the Recovery Console? (when it says Press R to repair at the first screen of the install) If so, is it the same one? If not, can you post the stopcode and parameters.

That's not good, anyway. That means something in your computer is very unhealthy. I'd start thinking about unplugging any expansion cards as jcow suggested, and if you can try swapping out the RAM.

You might be able to get around it by trying Shep's solution, reinstalling the OS over the top, but that might cause ballache depending on how many programs you'll have to reinstall, because you'll get a blank registry at the end of it, so things won't all behave normally, but I would be looking at something serious being hosed.

(At work, I'd probably be looking at memory and a hard drive. If you have a spare HDD, try chucking that in and see if you can install to it)

Mitth · Post by **Mitth** » 2005-03-19 06:53pm

I cannot swap out RAM, as it's the only RAM I have. The only nonessential components I currently have running are on the motherboard (sound card, ethernet). I suppose I could disable those in the BIOS, if you think it might help.

I cannot, as of right now, get the win 2k disk loading everything properly, so I can't duplicate the bluescreen. This is just because the damn thing is scratched though, and I can fix that. When I get the error again, I'll type it up.

Batman · Post by **Batman** » 2005-03-19 07:21pm

I wouldn't worry about hardware swapouts for the moments, this is almost guaranteed to be a software problem.
Just to make sure, Mitth-you get a BSOD when booting into REPAIR MODE, not the OS Safe mode, right?
I'm a little rusty about 2K so you better cross-check with the others but W2K has two repair options: repair mode and repair console (or something to that effect). The console might still allow you to do a checkdisk.
If BOTH BSOD, sorry but you're screwed. It's reinstall time.
As for reinstalling over your old W2K, if your data is all backed up and/or in a safe place (i.e. another partition/HDD), I'd say go for it. At worst it's going to waste some time, and you'll have to do a clean install anyway.
I must advise you however that this doesn't work, at least in the long run, more often than not. Other errors, spy/malware, driver incompatibilities.
As you'll have to reinstall your apps either way it might simply not be worth the effort.
No matter what, make sure you have at the very least those drivers handy that you need to go online. The rest you can download, but those are indispensible.
But you propably already knew that.

Mitth · Post by **Mitth** » 2005-03-19 08:17pm

Hm. Well, I left the computer for a moment while fiddling around and let Windows attempt to boot normally; and I have a different error than I first did. I'm not going to type it all up, but it involves "KMODE_EXCEPTION_NOT_HANDLED" and "d347bus.sys". I am probably just gonna reformat the hard drive. Most of my shit is stored on the other hard drive. I'll lose a lot of program information though, as well as the system registry.

Hm. I have neglected to mention this so far, but the computer in question is a dual-boot system. I have Mandrake 9 running, installed on a partition on the second hard drive. As far as I know, it functions wonderfully. However, I can never get it to boot into a graphical environment of any kind. I'm stuck in whatever you call command prompt mode in Linux. This would be alright, except that I haven't the slightest clue about the commands for Mandrake, or Linux at all for that matter. I grew up on MS-DOS, but Mandrake.. is not DOS. Would it be possible to run a chkdsk and fix errors using Mandrake?

EDIT: "EXCEPTION_NOT_HANDLED", not "EXCEPPTION_NOT_EQUAL"

Vendetta · Post by **Vendetta** » 2005-03-19 10:57pm

Try disabling Plug and Play awareness in your BIOS, possibly also turn off ACPI or any other APM features as well. d347bus.sys seems to be related to PnP BIOS handling.

Xon · Post by **Xon** » 2005-03-20 12:04am

Vendetta wrote:Try disabling Plug and Play awareness in your BIOS, possibly also turn off ACPI or any other APM features as well. d347bus.sys seems to be related to PnP BIOS handling.

d347bus.sys is the default name for the kernel level driver for Daemon tools v3.47

Mitth · Post by **Mitth** » 2005-03-21 10:30pm

ggs wrote:
Vendetta wrote:Try disabling Plug and Play awareness in your BIOS, possibly also turn off ACPI or any other APM features as well. d347bus.sys seems to be related to PnP BIOS handling.
d347bus.sys is the default name for the kernel level driver for Daemon tools v3.47

it is, and that is what it relates to most likely.

I hooked the hard drive up to this computer (my dad's, the one I'm currently on) and ran chkdsk. It found nothing wrong with it. However, I'm still getting bluescreens whenever I try to do anything. I'll post some of the various ones later.

Mitth · Post by **Mitth** » 2005-03-26 09:36pm

Right. I have been distracted, and never got an opportunity to record the various error messages. I ended up formatting the hard drive, and attempting to re-install windows. When I selected the drive to install on, I got a bluescreen: "PAGE_FAULT_IN_NONPAGED_AREA". I also discovered something very odd: my computer is electrified. It's mild, but throughout the entire case and anything connected to it (motherboard, hard drives, etc) runs a current of electricity. I discovered this when I tried to take out one of my memory cards, and it nearly knocked me on my ass (more out of suprise than the shock itself). I have no idea what caused this.

Shit.

jcow79 · Post by **jcow79** » 2005-03-26 09:57pm

Mitth wrote:Right. I have been distracted, and never got an opportunity to record the various error messages. I ended up formatting the hard drive, and attempting to re-install windows. When I selected the drive to install on, I got a bluescreen: "PAGE_FAULT_IN_NONPAGED_AREA". I also discovered something very odd: my computer is electrified. It's mild, but throughout the entire case and anything connected to it (motherboard, hard drives, etc) runs a current of electricity. I discovered this when I tried to take out one of my memory cards, and it nearly knocked me on my ass (more out of suprise than the shock itself). I have no idea what caused this. Shit.

Sounds like you have a screw or standoff grounding out on the motherboard. Also be sure you're plugged into a properly grounded outlet.

Mitth · Post by **Mitth** » 2005-03-26 10:03pm

jcow79 wrote:Sounds like you have a screw or standoff grounding out on the motherboard. Also be sure you're plugged into a properly grounded outlet.

Seeing as the only thing that changed to bring this on, as far as I know, was the sudden shutoff of power to the house, and subsequent continuation of it later, I didn't think it would be that. 'Twould be an interesting coincidence. I checked anyway though, and I can't find anything. I'll look again sometime tomorrow, when I have better light.

Mitth`raw`nuruodo · Post by **Mitth`raw`nuruodo** » 2005-03-28 05:09pm

Heh. Well, my computer still conducts elecricity, but it seems to be working at the moment. Thanks for all your help guys.

What I finally decided to do was reset the BIOS to factory settings, on a whim. It now works. I don't know what changed exactly after the power died, but I suppose something in the BIOS was disagreeing with everything else.