Blue Screen Error , wont boot to windows or safe mode

Knowing the exact bsod error would help us help you.

 

Did you try leaving the password blank?

0x0000000a(0xf79b8354 0x804e5619)

 

I can find many things on the first part on microsoft site, but the two additional fields of data give me nothing.

 

The recovery console from Dell is still running the Windows Blue Screen nodes, I was incorrect before when I said it was almost done.  Looked at the wrong line, currently its running 68% finished. 

Every test result has passed thus far however.

 

It may also help to know that I was attempting to get to safe mode to uninstall some programs,

when I first received the error, and I , at that time could get back into windows.

 

I also had just installed new memory which was purchased from Dell, the original 256 mg chips were in slots 1 and 2,  I placed the new 1 gig chips in 3 and 4.  The machine has run well since

installing those on Tuesday.

 

In my attempt to get to safe mode, I went to msconfig and selected to start in safe mode, and since that time, I am now unable to get to windows.

 

When attampting to repair windows, its asking for admin password, I have never had a password with this computer, and a search of Microsoft shows an issue with this, the resolve involves 5 floppy disks?  How crazy is that.  Who has floppy disk drives in this day?

 

I do appreciate your responding to my quest.  Looking forward to any ideas you may have!

 

 

Thanks for responding! 

"Did you try leaving the password blank?"

 

 

 

"0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried 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.)"

 

found here http://aumha.org/a/stop.htm  left side choose 0A:

 

 

I would remove that add in memory. See if it will boot then.

 

"Who has floppy disk drives in this day"

 

All my PC's have them, they are still quite useful.

Thank you for the reply. 

 

I have removed the new chips and on reboot, I still receive the stop error.

 

Most of the troubleshooting steps from the Microsoft KB's seem to think a person can still get into windows or at least safe mode.  I can do neither.  The only place I can access is the bios, where some mention is made regarding the shadowing, however, I was unable to find any reference to shadowing in my bios.  I know it should be there!

 

The recovery console testing now is at 73%.  Sure seems to be going very slow! 

 

Yes I did leave the password area blank, and just hit enter, it just returns to the prompt to enter the admin pass.

 

If you cannot get into windows by any other means you will have to do the following:

 

 

How to recover from a corrupted registry that prevents Windows XP from starting

Connect your non-bootable hard drive to the other computer.
 
Open Windows Explorer.  Click on Tools|Folder Options|View.  Check the box beside "Show hidden files and folders".  Apply your change.
 
Navigate to the d:\System Volume Information folder ( d: represents the crashed drive letter).
You will see a folder named something like _restore{.........}  the dots represent an alpha-numeric sequence.

 

In this folder you will see folders named RP0....RPnn.  Find the one with the highest number.
These are your System Restore points.  In the highest numbered folder you will see a folder named snapshot.  In this folder are registry hive files which you need to recover your system:

 

_registry_user_.default
_registry_machine_security
_registry_machine_software
_registry_machine_system
_registry_machine_sam

 

Create a subdirectory; i.e, d:\Windows\TMP. Copy these files to the TMP subdirectory.  Rename them:

 

default
security
software
system
sam

 

Note:  Be sure to lose the period (.) in the file named _registry_user_.default
Delete the files in the d:\windows\system32\config subdirectory with the same names.
Copy the d:\windows\tmp files to the d:\windows\system32\config. subdirectory.
Put your drive back in its original system.  Your system should start normally.  If you get the same error go back and choose another folder ( RPnn-1) and repeat the procedure.

 

 

If you are denied access to any folders read this article to fix this issue.

http://support.microsoft.com/kb/308421

Thanks for that response. 

 

I have failed the read test of the hard drive. 

Error Code  0F00:0244

 

 Seems I will be looking to purchase a new one.  I am looking at the Dell site and all that is available is external drives??

 

I do not have another computer I can place this one in, this is my laptop that I am on currently.

 

 

Read test failure is not always a bad hard drive, it can be due to corruption or heavy fragmentation of the NTFS file system.

 

You can buy a laptop hard drive at any electronics retailer for that Dell.

 

 

If you do not care about your data on the drive, you can try a clean install of windows.

 

 

Yes, I forgot about that tool, I won't next time. Does not solve problems 100% of the time, but in your case did work well. It also requires you to be able to boot into windows and install the crash software, some bsod's are so bad you cannot do this.

 

http://support.dell.com/support/topics/global.aspx/support/dsn/en/document?c=us&dl=false&l=en&s=gen&docid=E9589B9626A0982CE030030ABD6210B6&doclang=en

 

There is also one from Microsoft

http://support.microsoft.com/kb/923800

 

Used it once, no luck helping solve my bsod, had to use windbg (much more difficult) to find the offending driver.

http://support.microsoft.com/kb/315263

I just wanted to bump this up to say what seems to have been the problems. 

 

Even after the format and reinstall of XP, I was still getting the Stop error.  Sometimes on reboot it would go to windows and give a windows has recovered from a serious error, and to send the info to Microsoft.  After sending the error, it would bring up a IE page with information about a device driver conflict.  I ran the Dell driver reset tool.  It found nothing.  Then finally was browsing for help on the dell website, I discovered the Crash Analysis Tool.  What a godsend!  It found the issue immediately.  It was a Zone Alarm file.  Needless to say, that program is now off of my system. 

 

So anyone reading this thread if your getting BSOD'S, check out that tool.  I never knew of its existence!

  well. It also requires you to be able to boot into windows and install the crash software, some bsod's are so bad you cannot do this.

 

So very true.  I could not do anything until I had formated and reinstalled the OP.  Would of been nice to include such a thing in the Resource CD.  I'm not sure exactly what I typed into the search on the help site that brought me to the tool.