This BSOD means that the registry configuration failed. This BSOD means that one of the top-level registry keys , also known as core system hives , cannot be linked in the registry tree. This BSOD means that there is an error in the registry. This BSOD means that the requested page of kernel data from the paging file could not be read into memory. This BSOD means that a system thread generated an exception that the error handler did not catch.
This BSOD means that a hardware malfunction has occurred. This BSOD means that a fatal error occurred during setup. This BSOD means that a kernel-mode application generated an exception that the error handler did not catch.
This BSOD means that a uniprocessor-only driver has been loaded on a multiprocessor system. This BSOD means that a thread exited while its kernel stack was marked as not swappable. This BSOD means that a queue entry was removed that contained a null pointer. This BSOD means that the software license agreement has been violated.
This BSOD means that a fatal machine check exception has occurred. This BSOD means that one or more critical user-mode components failed to satisfy a health check. This BSOD means that the driver is in an inconsistent or invalid power state. This BSOD means that the power policy manager experienced a fatal error. This BSOD means that corruption has been detected in the image of an executable file in memory. This BSOD means that the kernel-mode handle table detected an inconsistent handle table entry state.
This BSOD means that a session unload occurred while a session driver still held memory. This BSOD means that the video port created a non-fatal minidump on behalf of the video driver during run time. This BSOD means that a session driver still had mapped views when the session unloaded. This BSOD will display if a driver attempts to write to a read-only memory segment.
This BSOD means that a thread attempted to acquire ownership of a mutex it already owned. This BSOD means that the driver wrote to an invalid section of the special pool. This BSOD means that the current thread is making a bad pool request. This BSOD means that the driver attempted to access a freed memory pool. This BSOD means that the system has referenced memory which was earlier freed. This BSOD means that the system accessed memory beyond the end of some driver's pool allocation.
This BSOD means that a driver failed to cancel pending operations before unloading. This BSOD means that a driver has been incorrectly ported to the terminal server. This BSOD means that a driver did not cancel pending operations before unloading.
This BSOD means that a driver has referenced memory which was earlier freed. This BSOD means the driver accessed memory beyond the end of its pool allocation.
This BSOD means a driver is trying to unmap an address that was not mapped. This BSOD means that the internal locked-page tracking structures have been corrupted. This BSOD means that a driver accessed a stack address that lies below the stack pointer of the stack's thread. This BSOD means that a driver has corrupted pool memory that is used for holding pages destined for disk. This BSOD means that a workitem did not disable impersonation before it completed. This BSOD means that one of your computer components is faulty.
This BSOD means that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. This BSOD means that a thread tried to release a resource it did not own. This BSOD means that memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued. This BSOD means that a thread's saved floating-point state is invalid.
This BSOD means that an active executive worker thread is being terminated. This BSOD means that a thread in a device driver is endlessly spinning. This BSOD means that a critical system process died.
When successful, the data on the drive remains intact, but if you don't have a suitable Windows XP installation CD or the repair fails, your still stuck.
If the data is that critical I would recommend purchasing a new drive for your machine and installing your operating system and applications on that.
You can then acquire a USB drive shell, mount the old drive in it, and extracting the data to the new drive in it.
Ok I got the disc and I tried running the recovery install or even a clean install but it only boots in dell media direct everytime and I cant get it to stop. I have it set to boot through the CD first. Ok I figured out how to not boot in media direct but it wont except the install cd they sent me. I accidently tried a windows 98 cd and it went through the process when I went to f12 and booted through CD but it said wrong machine.
I cant even get to that with the XP install cd. I'm afraid you will need to explain what you mean by stating that it will not accept the install CD. When you boot properly from the Windows XP installation disk you should get the choices of installing a fresh copy of the operating system, repairing the existing operating system, or quitting.
What messages do you see on the screen as you attempt to boot? Another thing I was wondering is what disk did they send you? If you cannot perform a repair install using the Windows XP installation disk, and are therefore forced to do a complete install, you must decide if you want to keep Media Direct. If you do, you must begin with the Media Direct portion of the installation so that the disk can be properly partitioned prior to installing the operating system.
Heres what I don't understand. When I accidently used a windows 98 disk to try and recover it went through the proper motions of giving me the options to reinstall it. Of course I received a message saying wrong machine. But when I used this dvd they sent me that says Reinstallation DVD Microsoft Windows XP Media Center Version with Update Rollup 2 , it just seems to bypass it and run a normal startup which leads to a blue screen thats says "unmountable boot drive".
I never get the options to do a recovery or a repair like it doesnt even read the disk. It might be helpful to note that my antivirus protection was not up-to-date and so I don't really know if my laptop is affected by a bug. Will I loose all my files, folders and pictures?? Also, the information that you sent me did not really give any valuable thought that I could possibly use Please help, I am desperate!!
I do not know how to let you understand that I cannot upload anything from my computer as I have a solid blue screen with the message that I have already posted. I just cannot get past the blue screen to do anything. How do I upload the mini-dump file when I cannot get pass the blue screen?? I have lost the desktop, I only have the accursed blue screen!!
I have tried all the troubleshooting there is to try and still nothing. What next??? If this screen appears again follow these steps: Check to make sure any new hardware or software is properly installed. I have tried all the troubleshooting suggestions but nothing works; can you help me??
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. SpiritX Volunteer Moderator. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. In reply to SpiritX's post on March 1, The technical information listed on the blue screen is as follows: Stop: 0 x 0 x , 0 x CD, 0 x , 0 x F6BA6BB8 Beginning dump of physical memory Physical memory dump complete Contact your system administrator or technical support group for further assistance It might be helpful to note that my antivirus protection was not up-to-date and so I don't really know if my laptop is affected by a bug.
In reply to JoyanP's post on March 13, Hi, We need the actual minidump file. If you have problems uploading copy it to somewhere else on your computer, such as the desktop, and then upload it from there. We can analyze the minidumps if you make them available from the SkyDrive or other file sharing sites such as MediaFire. Do all the checks and updates that you can to see if those help.
Remember this may be a memory or other hardware problem that will require a computer shop's assistance. I left the link here out in my original posts above - here it is for reference.
0コメント