Blue screen windows install sata

However when I tried to install the XP in a real machine, the XP could be normally installed without errors in both the text and GUI phase, but it turned to blue screen at the first time bootup after the GUI installation phase. I also tried to enter the Safe mode and the Safe mode with Command Prompt, but they would all go to blue screen and reboot immediately so that I could hardly to look at the blue screen error code.

I tried with the latest version of Virtualbox 4. This problem seems to be a regression. I was trying to instal it using Ubuntu The machine is a Fujitsu Lifebook UH Contact — Privacy policy — Terms of Use. Login Preferences. Browse Source. Ticket new defect Opened 13 years ago Last modified 8 years ago.

Attachments Capture Change History Changed 13 years ago by vadimrapp attachment Capture Changed 13 years ago by Cherife attachment screenshot Changed 13 years ago by Cherife attachment VBox. No problems. I repeat: SATA is unusable. I am using 4. If you need more information, please let me know. Last edited 8 years ago by JQ previous diff. Note: See TracTickets for help on using tickets. VirtualBox 2. Warning: By doing this, all stored data on the system hard drive will be lost!

Therefore, you should only consider this option if all other possible solutions have failed to help. There is no way to completely protect yourself from the Windows blue screen of death, because internal errors can occur even through no fault of the user.

It can occur as a result of a faulty update or due to spontaneous hardware failures. There are certain strategies that you can use, though, to prevent losing important data and reduce the chances that a blue screen will appear. There are more than CMD commands available with Windows. The command prompt can be used to control large parts of the operating system, computer, or drives. To do this, though, you have to know the right commands. Here we explain how to use CMD commands and which functions they have.

Our article For a long time, Windows users were left behind when it came to command interpreters because the command prompt did not allow full access to operating system internal components, and scripting also offered only limited possibilities. The cross-platform program not only does much better than cmd.

This article introduces three ways of checking your Windows version in just a few seconds: using a keyboard shortcut, via the Control Panel, or using the Windows Command Prompt CMD.

Every Windows user knows: No matter which version you use, the popular Microsoft operating system has its bad days. Sometimes these are so serious that the worst possible outcome happens: Windows won't boot anymore. Do not turn off your computer. Find out how to fix it. With a real estate website, you can set yourself apart from the competition With the right tools, a homepage for tradesmen can be created quickly and legally compliant Why wait?

Grab your favorite domain name today! Matching email. SSL certificate. Save now. First steps after a blue screen Try to remember exactly what you were doing on the PC right before you saw the blue screen. Have you looked through all the menu options? Sometimes it is buried in a sub menu. Steve Consolini This person is a verified professional. Or not even have an AHCI option at all, if it's older. If that's the case then something else is causing the BSOD. If you can put Windows 7 on that machine, you should do it.

Yeah trying to put win 7 on it now. So I'll see how that goes. Thai Pepper. JRC This person is a verified professional. That's not true. I don't actually recall getting a no drive detected error in this case, but I can certainly see that happening too. Jordan Feb 19, at UTC. I racked my brain a few years ago when I had this problem. However when it is interpreted by someone trained to debug it has been identified as one of the misbehaving drivers.

The debugging of the posted minidump file also confirmed that this is one of the misbehaving drivers. OK, diagnostic info uploaded to the same spot same link. BTW, this is brand new system, less than a month old. All is brand new and clean Windows install. I have no issues with the display whatsoever.

If the driver misbehaves, it must be only when the add-on SATA controller is present. I'd rather suspect that some USB related driver misbehaves.

All those external drives worked fine attached to my old system, so I suspect some incompatibility of Windows with the new AMD based hardware as the same issue happens on the second motherboard ditto for the blue screen. The blue screen generated by storahci. Does not seem very likely.

None of these seem to be happening on my new system. Why do I need to do what you recommend? Could you explain? Are you saying that after doing that there will be no blue screen with SATA adapter installed on my motherboard? I have serious doubts. The debugging analysis of the bsod minidump was provided.

A review of the msinfo32 and dxdiag was performed in relationship to the debuging. OK, since the original problem was the blue screen with SATA adapter present in the motherboard I didn't think that nVidia or Symantec drivers were at fault.