I've got Blue Screen Of Death

Similar Questions

• I got the Blue Screen Of Death with Stop: 0 x 00000024 (5898 0x86D4, 0xC0000102, 0 x 00190203, 0 x 00000000)

  Original title: Help, I got the blue screen of death!

  Can someone help me please? Whenever I turn on my computer, it goes to the BSOD. I tried the last settings that worked, but he went to the BSOD too! In addition, safe mode it won't work goes to the BSOD as well. Nothing works. I have to go to a computer store to fix it, or is - it possible to fix it at home? Please help immediately!

  The BSOD I get says:

  A problem has been detected and windows has 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: disable or uninstall all utility defragmentation or anti-virus disk backup,. Check the configuration of your hard drive and check the updated drivers. Run CHKDSK /f to check for hard drive corruption, and then restart your computer. Stop: 0 x 00000024 (5898 0x86D4, 0xC0000102, 0 x 00190203, 0 x 00000000)

  Hi TheCookeNinja,

  I suggest you run the check disk (chkdsk) of the Recovery Console & check if you are able to boot to the desktop correctly.

  Step 1: To start the Recovery Console, you can follow this link.

   

  To start the computer and use the Recovery Console

  http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/recovery_console_overview.mspx?mfr=true

  Step 2: At the Recovery Console prompt, type the following command and then press ENTER:

  CHKDSK [/ p]: [/ r]

  Note: At first, try to run chkdsk/p & check if it helps. Later, you can run chkdsk/r.

  Reference:

   

  How to install and use the Recovery Console in Windows XP

  http://support.Microsoft.com/kb/307654

  I hope this helps.

• We had a power outage in our area, the computer was on and running, got the blue screen of death with the following: __0x000000C2, 0 x 00000043, 0xD6C61000, 0 x 00000000, 0 x 00000000 BAD POOL CALLER

  We had a power outage in our area, the computer was on and running, got the blue screen of death with the following:
  0X000000C2, 0 X 00000043, 0XD6C61000, 0X00000000, 0X00000000 BAD POOL CALLER

  If you have not saved your data and you want to start the computer with Linux Livecd such as Knoppix and copy your data files on an external hard drive. It is a precautionary measure before the step follows because things happens. ;-)

  Then do a repair installation.

  http://www.michaelstevenstech.com/XPrepairinstall.htm

  If the repair installation does not work, test the equipment to ensure that none have been damaged during the blackout and then do a clean install of Windows.

  http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

  http://michaelstevenstech.com/cleanxpinstall.html - Clean install - how-to
  http://www.elephantboycomputers.com/page2.html#Reinstalling_Windows - what you will need at hand

  If all goes well, no equipment was damaged during the shutdown. Consider buying a power supply (battery backup). APC and Belkin are good; for a computer, simply spend about $60. MS - MVP - Elephant Boy computers - don't panic!

• Comments on new MBP XP got the blue screen of death at startup.

  I get a blue screen of death when I copied and then started a guest Windows XP on my second MacBook Pro. I've used this comments XP on my old MBP for a year without problems. The two Mbps run VMWare Fusion 3.

  During startup, I got the message "features supported by the processor (s) in this machine are distinguished by the features supported by the processors of the machine on which the snapshot has been registered."

  Here are the details.

  1. I made a judgment of my guest XP on my old MBP

  2. I then copied the folder of the Virtual Machine - Open /Users/ - I chose the stermaster2_1VM.vmx -.

  2. has asked if the machine has been copied or move - I chose copied.

  3 merger then threw "features supported by the processor (s) in this machine are distinguished by the features supported by the processors of the machine on which the snapshot has been registered." -I chose Yes

  4 merger threw "cannot connect virtual peripheral Serial0 because no corresponding device is available on the host. You want to try to connect this virtual device whenever you turn on the virtual machine? "- I chose YES

  5 merger: "Virtual device Serial0 start disconnected." - I pressed OK

  6 merger: "Cannot connect virtual peripheral serial0 because no corresponding device is available on the host." - I chose Yes

  7 merger 'VMware Fusion is unable to provide all the graphics features expected by this machine virtual.' - I pressed OK

  Then a blue screen of death

  I was wondering if you see anything wrong with what I did above.

  Thank you

  Bernie

  Check if you have a file *.vmss in the Directory VM - If yes - delete it and try again

  ___________________________________

  VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

• Blue Screen of Death... Urgent!

  Hey all. It's a little urgent, so any help is appreciated. So the story:

  It all started last Saturday in the fourth. I plugged my 5s 32 GB iPhone in car charger and it blue screened, what frightens me. I quickly unplugged and and soft restarted as soon as I saw him, and everything was fine.

  Since then, so three days later, I had to restart about 50 + times. So today I got sick of this blue screen, and I decided that I would try to fix it. I looked around solutions, and many say that it happens shortly after a solution when you remove the screen, but I've had my phone for four months and have never had to remove from the screen.

  The next solution was to restore factory default, so I decided to try it, after that I backed up in iTunes which is

  Finally, I was getting it restored, when all of a sudden, BAM. projected again blue.

  Since then, happened across this restore Middle blue screen of death, and it's practically a piece of metal shit now. I can't do anything. I can't force the restart it you a blue screen. Can someone give me advice? I have some upcoming vacation and need my phone. Can anyone help?

  Try recovery Mode

  Connect your device to your computer and open iTunes.

  When your device is connected, force restart it: press and hold the sleep/wake and home for at least 10 seconds, and only release when you see the Apple logo.

  Keep now until see you the recovery mode screen and wait that he eat.

  You may need to do the above, more than once as recovery mode is difficult to enter.

  Restore as New first, then restore sauvegardΘ if you wish.

  https://support.Apple.com/en-us/HT201263

  If the steps above do not help, you tested it on an Apple Store.

• Vista workaround to access restore partition of the system (0xc0000C1F5 Blue Screen of Death error)

  Stats:

  Computer type: HP-Pavilion a6333w

  Product #: KC746AA #ABA

  Operating system: Windows Vista™ Home Premium (6.0, Build 6000) (6000.vista_ldr.071023 - 1545)

  Processor: AMD Athlon (TM) 64 X 2 processor Dual Core 4800 + (2 CPUs), ~2.5GHz

  Disk space: 500 GB

  RAM: 3 GB

  Graphics card: NVIDIA GeForce 6150SE nForce 430 <-integrated on the mother board.

  ---------------------------

  Location: Try to update Windows Vista SP1 my computer hung up.  After a cold reboot, I got a BSoD (blue screen of death) with the error 0x0000C1F5 code.

  Current problem: whenever I try to boot Vista I get the same error during the vista loading screen.

  I tried the safe mode, the last correct log on the thing, and even a system restore disc that I downloaded from PC World.

  None of these online solutions have worked.

  ---------------------------

  Is there a way to bypass the default loading process and access the recovery partition drive to do a factory reset?

  If there is a way to save the info on my HD it please let me know.

  Thanks, Jcubed.

  Message edited by Jcubed on 11/12/2008 18:06

  I think the (BugCheck Code) code is 0x0000C1F5, and there's a Microsoft Hotfix for this:

  http://support.Microsoft.com/kb/946084

• Satellite L450D - 13 X - black screen of death/Blue Screen of Death

  Hello everyone.

  I have a Toshiba Satellite L450D - 13 X for children, and for the price it's a good laptop. Have had no problems with it until two weeks ago, when the screen froze for boys while playing a game and downloading a program on the net. Had to make a stop of force and since then, we have a BSoD on each startup. That's what we tried:

  On "Starting Windows", we are given the option to either 'Launch Startup Repair' that ends as BSoD or "Start Windows normally" who returns to the list of option "starting Windows."
  Any attempt enter 'Safe Mode' BSOD results.
  Attempt to boot an ISO of the disk recovery Windows on a USB key (we did put highlight and make promotion up) results in BSoD. Borrowing a correct installation of Windows 7 DVD and highlighting what an option cause BSoD.

  In fact, the only option that we used who threw something different has been using advanced startup options. On one of these options, we've got the Blue Screen of Death with the following information:

  Unmountable_Boot_Volume
  Disable memory the Bios Options such as cache/occultation

  Technical info

  Stop: 0x000000ED (0xFFFFFA80023C2CDO 0xFFFFFFFFC0000185 0000000000000000 0 x 0 x 0000000000000000)

  I don't mind erase the hard drive and leave, there's nothing on what is essential. Very, very well, I'd appreciate a steer on it. Checked the Web for things and nothing seems to help for other options. I'm not particularly tech literate but can follow directions.

  Thanks in advance.

  It is really possible that the HARD drive is faulty.
  If possible try to get another same HDD used for test purposes and install OS using the Toshiba recovery image.

  A friend of mine had a similar problem and after Exchange of HARD drive, everything went well again.

• Portege R100 - Random Blue Screen of Death (IRQL not less or equivalent)

  Hello

  I've been making 'Blue Screen of Death' screens random in the last few weeks. The error is "IRQL not less or equal ' and it performs a memory dump each time. If I get the error and try to restart the phone after, I usually get the same screen of "Blue Screen of Death" when starting.

  I have not installed new hardware lately. Last update about a year; upgrade memory. I tried to replace the RAM with a spare that I had and I was still getting the same error.
  I have not installed new software in the last weeks, which would coincide with this error.

  I am tracking the temperature of the processor and I'm higher than 48 degrees Celsius.
  I'm not an expert, but I guess it's purely a hardware problem? As I rarely hear the CPU fan, I thought it might be overheating of the CPU.

  But even after that make the CPU fan to operate at 100% using a free software called "Fan speed" I always got the same random screen of 'Blue Screen of Death'.

  I would really appreciate any feedback and assistance. Really, I love my R100 and want to fix it.

  Select this option.

  Hey,.

  > If it's the memory controller can it be replaced?
  No, you can only replace the motherboard together. The memory controller is a part of it and it of not possible to replace the memory controller only.

  Theoretically, it could be the motherboard (memory controller) to malfunction if Memtest86 errors even you have replaced the RAM already.

  But 100% sure answer you can get a service provider approved because they have professional diagnostic tools.
  Then get in touch with the guy and ask for help. They can also order a new card of mother if she needs to be replaced.

• Blue Screen of death - now cannot load Windows (even in safe mode)

  Laptop last night (Satellite L500-19Z;) Win 7 64 bit) crashed while playing CIV4. Had a blue screen of death. before I had the chance to read one of the error messages about the computer restarted.

  It loaded windows in SafeMode very well then and informed me that he had loaded OK the problem safe mode will be linked to some recently installed software and I should uninstall programs I had installed until it loads normally. As it was late last night I closed and thought I would sort the morning (with the benefit of hindsight it may have been a mistake...).

  Today, when the computer tries to start, it tries a startup repair; Unfortunately it does not work every time and it says "Startup Repair tried several times but still cannot determine the cause of the problem"

  I looked at the paper it produces, but it passes all of the individual tests.

  I can't access also advanced recovery options system & support, that appears in the Startup Repair dialog box as it requires that I be connected, which apparently I am not (probably the machine never got to the windows screen connection before attempting repair system). The error message reads "you must be logged to access system recovery options. If you encounter problems to connect, please contact your computer administrator for help. Please click OK to restart the computer. »

  I had a go at the start in the advanced options (safe mode, safe mode with command etc., but the result is the same).

  I also tried the repair of your computer to the screen option options advanced boot, but after the screen where it asks you to choose the language and keyboard, I get the same error of connection mentioned above.

  Is it possible to repair or even run windows based hard drive recovery (do not have the DVD of recovery with me as I'm away from home for a few weeks) without connecting to windows? I expected here, but have not yet find a way to do it.

  (there is no disc in the disc drive, no other devices connected to the laptop - I tried with power outlet and the battery and have not noticed differences)

  Thank you
  James

  Hello

  Pitty, you cannot retrieve the HEXADECIMAL code
  On this side, I think that your HD or registry is damaged and you have to reinstall the entire system

  Good luck

  Post edited by: Praepositus

• USB-6009 not recognized after the blue screen of death

  I have two devices USB-6009, used with NOR-DAQmx and Labview to make some analogue simple analogue input and output.  The USB box - two 6009 were previously works very well on this PC.  Recently, I got a blue screen of death, associated with a different USB device to (non - OR) connected to the PC.  I not save the information of the blue screen of death.  When I restarted the computer, the USB-6009 devices were no longer recognized by Labview / MAX.  The Green LED on the USB - 6009 s do not come.  The USB - 6009 s appear in the Device Manager of Windows with a yellow exclamation point ("Windows cannot load the driver for this hardware device").  If I connect the USB-6009 case to another PC, MAX recognizes them on this PC, and I get the usual flashing green LED.  If I connect another USB-6009 (never connected to this PC), I get a green LED solid, and, says Windows cannot load the driver.

  I am running Vista, Labview 8.5 and NOR-DAQmx 8.9.  I rebooted 5 - 6 times, I tried disabling and the reactivation of the USB-6009 by windows Device Manager, I tried the options "update driver" in Device Manager.  Any advice on how else to solve it?  Thank you!

  The driver update and turn do nothing to the main driver - DAQmx. Reinstall or repair that.

• Blue screen of death during recovery

  Apparently, the latest updates from MS caused problems and I had the blue screen of death during the start several times on my Pavilion p6610f desktop computer. I try a system recovery and got the screen died shortly after the recovery began. Now it does not start or even turn on a screen.  Any help would be appreciated.

  Well, this is my fourth attempt at this announcement, I hope it will work this time.  Below are my answers to your questions.

  Hello jp-3,

  Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the Forums of HP, I would like to draw your attention to the Guide of the Forums HP first time here? Learn how to publish and more.

  I read your post about how you are not able to boot your Windows computer after attempting a recovery, and I'd be happy to help you! To start, I have to ask you a few questions:

  Mech Hi and thanks for your help.

  • What is product and model number from your desktop?

  It is a Pavilion p6610f desktop PC

  • What version of Windows you have installed on your computer?

  I was running 7 Home Pro

  • Has your computer finished all his important updates from Windows?

  The updates had been installed, which was when I started to have problems

  • Have you updated your drivers from HP the HP SupportWizard?

  I didn't have a chance to update anything after you restart MS. updates He immediately started crashing. I restarted three times and got a truncated blue screen every time, that's why I tried the recovery.

  • What is a current or recent problem?

  He started just after the latest version of Windows update.

  • You are able to get an image from another monitor?

  In general, I run two monitors (bothHP) via USB converter j5create JUA310, which I unplugged in case of conflict. It crashed with two configuration simple and double monitor. When I was running food, I had only the primary monitor upward.

  In the meantime, I recommend that you follow this document on screen is blank after you start the computer. This should help with the display on your screen when you start first to the top of your computer.

  I unplugged everything - HP Color laser printer duplicator Kensington USB port and USB mouse Logitech wireless (wired mice HATE!). Had previously removed just in case USB Sandisk flash drive. The computer started, monitor went up, and I received a message "windows recovered from an unexpected shutdown - check online solutions. Did respond to the message again. Did not try a BIOS update.

   

  Thanks for your help!

  Please re-post with the results of your troubleshooting, as well as the information requested above. I look forward to your reply!

  Concerning

  MechPilot
  I work on behalf of HP

• Why is it called 'Blue Screen of Death?'

  Why is the Windows crash screen called the 'Blue Screen of Death"when some people who don't know much about computers think that a BSoD means a blue screen that kills you when it's really just an error message?

  Hello

  The BSOD made his first appearance in 1987 during the beta of IBM "Operating System/2 (OS/2) developed to lattice, stir; the developer of the first OS/2 and Windows compilers. The STOP error screen hit the OS/2, when developers were porting to other tools of lattice, Inc. over the internet. The reason behind the error seems to be bugs (it means vices or defects in more technical terms) in the OS/2 software. While giving the error description of IBM (informally known as "Big Blue", then), developers of lattice, Inc., called the error like "Blue Screen of Death", combining colour with IBM and an appearance at the dead screen that comes not depart without rebooting.

  Another story, it's that the BSOD error was originally a "Black Screen of Death" (as some say) instead of "Blue Screen of Death". The term BSOD was initially given its name by Ed Brown in mid-1991. Ed Brown was then an IT technician with Coca-Cola Company, Atlanta, Georgia, United States. Ed Brown reported that the error has hit when the company implemented (Windows 3.0 operating system) in the world of Marketing Group, and the users when you try to run "WordPerfect" would randomly get BISOD error screen. The error would display a completely black screen with a cursor blinking in the upper left corner. This would happen when a user tried to run a DOS application and eventually got stuck with the BSOD error. The system had no escape from the BSOD error until it is restarted.

  The BSOD error is usually written in white text on a blue background.

• Windows 7 clean installation Blue Screen of Death (BSoD) on a loop of reboot

  Aloha everyone,
  I did an install customized windows 7 on a new Western Digital 1 TB sata hard drive, which has been formatted, partitioned, scandisk, and a ntfs c drive was created prior to installation.
  The installation ended safely.  I then install my screen reader, Window-Eyes, requiring a reboot.  After the reboot, I started to install critical updates to Windows.  On my fourth update and restarting, I got the blue screen of death, that of some people call a BSoD.  I rebooted and Windows itself restored to a previous state of good, of my just accept the default choice.  Then the rear computer works, but if I stop, restart I get the blue screen of death (BSod) is back, and the loop begins again, i.e. windows restores good condition that works well, until you stop, but on reboot - BSoD is BACK!
  I removed the automatic update option, I disabled ScanDisk, drivers updated, bluetooth devices, deactivated sideshow, etc., without any positive result.  I called Microsoft for assisstance and the technician acted like this isn't a known issue, but he assured me that he could solve the problem.  He took control of my computer remotely and do not tell me anything except that the computer would check and repair any problem on reboot, and if he did does not resolve the problem, I have to remember.  The computer has rebooted without the BSod, but I stopped to check if the loop went, and it is not!  To restart the BSOd was back.  It is to note that if I put the computer to sleep, I get a clean start, but stop, restart or hibernation, I get the blue screen of death (BSoD)!
  It is a Dell Dimension XPS 420 with a intel Q6600 processer, 3 GB of ddr2 memory, which came with OS Vista Home premium 32-bit.  The Vista system, the last time I got a BSoD has been for more than a year.

  After researching this problem on Google, it appears that there is a problem without a solution.
  I ran "which has crashed, you can get:
  http://www.resplendence.com/downloads

  The following accident report:
  Monday, December 21, 2009 23:23:44 your computer crashed
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA800573B060, 0xFFFFFA800573B340, 0xFFFFF80002D91240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\122109-16972-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Monday, December 21, 2009 20:22:10 crashed your computer
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\122109-33306-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Sunday, December 20, 2009 15:28:42 crashed your computer
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002ADC00C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\122009-17565-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Thursday, December 17, 2009 12:27:45 AM your computer crashed
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\121609-28111-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Monday, December 14, 2009 20:59:21 crashed your computer
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA80059A3060, 0xFFFFFA80059A3340, 0xFFFFF80002DC4240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\121409-25506-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Sunday, December 13, 2009 02:17:55 your computer crashed
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA80058A4060, 0xFFFFFA80058A4340, 0xFFFFF80002D8A240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\121209-24648-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Conclusion
  6 dumps were found and analysed. Note that it is not always possible to
  assert with certainty whether a reported driver is really responsible for crashing
  your system or that the cause is in another module. However, it is suggested
  looking for updates for the products that these drivers belong to and regularly
  Visit the Windows Update or activate the automatic updates for Windows. In the case of a piece of
  defective material is in trouble, a Google search on the bug control
  Errors, as well as the name of the model and brand of your computer can help you investigate
  This further.
  end of the crash report.
  A side comment:
  Them are 56 reported problems, and none of them have solutions. If I go through each problem report and check for solutions, about 80% of the times I ask myself to send to Microsoft for more information about the problem and I click on send, but I always get the following:
  [Window title]
  Incident reports

  [Main instruction]
  Problem connecting to the Windows error reporting service

  [Content]
  Some of the reports can not be uploaded to the Windows error reporting service. Please try again later.

  [Close] »
  I tried several times with the same result, that is, the details of the problem which has need of Microsoft is not be received.  To this end, the problem will not be found.
  Thanks much for any help.
  Manny
  P.S. I'll never upgrade a Windows operating system.  My recommendation for anyone who is planning to upgrade to Windows 7 is to try first on a dual boot using the free download.  If it works for you, consider yourself lucky and buy the upgrade.  If it does not, then remove Windows 7 and stay with your old system.

  Please check your RAM for errors (use memtest86 + to test). "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• Blue screen of death (stop 0x0000007B) after April Windows Update on XP Home.

  My machine (Dell Dimension 3100 with XP Home) home is set for automatic recovery of Windows updates. I reload often, but when I was forced to start again last week, I got the blue screen of death. Apart from the general BSOD error message, I got the stop code:

  STOP 0x0000007B...

  I forgot the subsequent stop codes, but search recall I was doing on them indicated drivers disk or storage-related problem.

  I ran all sorts of Dell diagnostics on my hardware, get absolutely no problem. Scan of a viral infection was also negative. A colleague help out me suggested removing the updates of Windows of April, he did help and usefulness of the ERD. XP loaded and started after that, if I had to go through a process of slooow restart for most updates. My office also now charge many times slower - I suspect drivers and services can't find what they expect to find and take considerable time to make mistakes.

  My Dell has a range of Intel (RAID-1) matrix installed. I strongly suspect that this pilot was in trouble after the April update Windows Update.

  So, what should I do to prevent this from happening again? I don't know the specific fix involved. I have disabled the automatic updates for now.

  TIA

  Rick

  Complete sweep of Kaspersky AV, booted from the CD, turned up negative, so I doubt that it is an infection.

  I'm sorry, but this does not exclude the possibility of infection. See step # 3 in my previous response, or contact Ms. PCSafety for assistance.

  Or see http://msdn.microsoft.com/en-us/library/ff559218 (VS.85) .aspx and/or http://aumha.org/a/stop.php#0x7b for more troubleshooting ideas.

  Or if you let Windows Update to install an update for the driver (never a good idea), try a roll-back of pilot.

  ~ Robear Dyer (PA Bear) ~ MS MVP (that is to say, mail, security, Windows & Update Services) since 2002 ~ WARNING: MS MVPs represent or work for Microsoft

• I downloaded an update and restarted my computer, received the blue screen of death shortly after the computer restarts. Now it does not start

  I don't know when the downloaded update, the computer has been restarted on September 10, 2010 to install updates. Shortlyl once the computer is restarted, I got the blue screen of death.  with the details of error like:

  Stop 0 x 000000050 (0 x 000000000000000, 0xFFFFF88001DCAE4, 0xFFFFF8A00B490027, 0 x 00000000000002) do not know if the number of zeros is exactly right in one of those, but it's super frustrating.

  I tried to restart my computer in repair as recommended (get blue screen of death), I tried to reboot normally, loop just restart procedures asking if I want to restart in repair mode.  I tried SafeMode (BSOD), I tried to restart with last working restart (restart loops), I tried to choose the "Computer repair" BSOD I tried a diagnosis and all past.

  Help!

  Thank you.

  So yes actually hear nothing helped me.  Seems that, given that the computer is not stopped correctly and my hard drive was not recognized there starting the cycle upward or give me the BSOD.  Put it in my Ubuntu CD spare which I've had since my last PC hard drive became corrupt and force back across my hard drive.  After doing this, I was able to do a boot repair, who led for the BSOD.  Not sure how that actually fixed, lost about 10 hours of my day.  So I guess I can chalk up to Microsoft and a reminder on why I should buy Mac for now on... an update shouldn't really cause such problems.

  I get that not everyone has the same PC, so it is difficult to tell if an update is bad, but he should not do this and if an update is the cause of a certain segment of consumers who are updating must be taken down for everyone, or at least the users with the configuration that is known to have problems with an update.

  Problem is solved, had to go back to a previous version of good boot where I have not install updates again.  Now, I'm trying to understand who was was bad, so I can leave my computer knows to ignore.

  Nice day.

  Just in case someone needs to know how to use Ubuntu to back up files on their PC that does not load windows, please see the link below:

  http://www.howtogeek.com/HOWTO/Windows-Vista/use-Ubuntu-Live-CD-to-backup-files-from-your-dead-Windows-computer/