| | |
Blue Screen on Boot - Quick Transition
![]() |
•
•
Join Date: May 2006
Posts: 4
Reputation:
Solved Threads: 0
I'm fairly new to building systems, but I'm working on a HTPC and have run into an O/S issue. Brief details:
- I'm working with a brand new mother board/ & CPU.
- Unable to boot into OS, even in safe modes. As a result, I can't generate a boot log file to assess the issue.
3- In the early stages of loading the OS, a blue screen appears with an error code. Unfortunately the screen transitions too quickly to read.
Is there anything I can do to view the error code, or verify where the issue resides?
- I'm working with a brand new mother board/ & CPU.
- Unable to boot into OS, even in safe modes. As a result, I can't generate a boot log file to assess the issue.
3- In the early stages of loading the OS, a blue screen appears with an error code. Unfortunately the screen transitions too quickly to read.
Is there anything I can do to view the error code, or verify where the issue resides?
•
•
Join Date: Apr 2006
Posts: 31
Reputation:
Solved Threads: 3
Tap F8 before the Windows logo appears and choose "Disable automatic restart on system failure". You'll then be able to read the STOP code. You can also attach the hard drive to a working machine and see if there is a Minidump folder under the Windows folder. If there are files in Minidump, post them on the 'net somewhere and I can debug them for you (if necessary).
Fix certain Windows problems in a snap with Dial-a-fix:
Dial-a-fix
Dial-a-fix tips
If Dial-a-fix or my suggestions have helped you, consider boosting my rep :)
Dial-a-fix
Dial-a-fix tips
If Dial-a-fix or my suggestions have helped you, consider boosting my rep :)
•
•
Join Date: Apr 2006
Posts: 31
Reputation:
Solved Threads: 3
Not really any particular resources, except Google.
7b = INACESSIBLE_BOOT_DEVICE. It's usually caused by a bad path in BOOT.INI, a missing storage driver (like installing Windows on a SATA drive without hitting F6 during setup to specify a SATA driver), or other miscellaneous controller issues. Is this a SATA drive? If so, did you use a driver during setup? If not, you may need to make a floppy disk with the SATA driver on it. You can usually find a disk maker on the motherboard CD (OK choice), and at the motherboard manufacturer's website (better choice).
7b = INACESSIBLE_BOOT_DEVICE. It's usually caused by a bad path in BOOT.INI, a missing storage driver (like installing Windows on a SATA drive without hitting F6 during setup to specify a SATA driver), or other miscellaneous controller issues. Is this a SATA drive? If so, did you use a driver during setup? If not, you may need to make a floppy disk with the SATA driver on it. You can usually find a disk maker on the motherboard CD (OK choice), and at the motherboard manufacturer's website (better choice).
Fix certain Windows problems in a snap with Dial-a-fix:
Dial-a-fix
Dial-a-fix tips
If Dial-a-fix or my suggestions have helped you, consider boosting my rep :)
Dial-a-fix
Dial-a-fix tips
If Dial-a-fix or my suggestions have helped you, consider boosting my rep :)
•
•
Join Date: May 2006
Posts: 4
Reputation:
Solved Threads: 0
Good to know. Strange thing is, the drive is a regular IDE type and when I connect it to another machine, it boots without issue. I'm goint to check the BIOS and see if I have it set to boot from the right source.
I don't have any other drives attached at this point (floppy or CD), any chance that is causing an issue ?
duwrt
I don't have any other drives attached at this point (floppy or CD), any chance that is causing an issue ?
duwrt
•
•
Join Date: Apr 2006
Posts: 31
Reputation:
Solved Threads: 3
Wow. Okay...
Does this motherboard have RAID capability? (and what motherboard is it?) If so, try disabling it in the BIOS, or moving the hard drive to a non-RAID IDE connector (usually IDE RAID has two separate IDE channels for RAID capability and two for non-RAID --- move to the non-RAID, if that's an option).
Does this motherboard have RAID capability? (and what motherboard is it?) If so, try disabling it in the BIOS, or moving the hard drive to a non-RAID IDE connector (usually IDE RAID has two separate IDE channels for RAID capability and two for non-RAID --- move to the non-RAID, if that's an option).
Fix certain Windows problems in a snap with Dial-a-fix:
Dial-a-fix
Dial-a-fix tips
If Dial-a-fix or my suggestions have helped you, consider boosting my rep :)
Dial-a-fix
Dial-a-fix tips
If Dial-a-fix or my suggestions have helped you, consider boosting my rep :)
![]() |
Similar Threads
- blue screen on boot (Windows NT / 2000 / XP)
- blue screen of death (Windows NT / 2000 / XP)
Other Threads in the Windows NT / 2000 / XP Forum
- Previous Thread: win xp, don't know how to start loading
- Next Thread: Windows Media Player problem
| Thread Tools | Search this Thread |
.net 3.5 3daccelertion 64bit 2010 activedirectory alaris android apache application arm auto black blue book canonical cellphones chinese codeplex collaboration combofix computer computerfreezes crash desktop desktops domain dotnetnuke drive error errors explorer features folder fonts freeze gadgets hardware home intel killprocess laptop laptops latitude lcd linux load mac markshuttleworth microsoft minimalizes mobile monitor netbooks novell nvidia opensource operatingsystems options oracle osinstallationproblem osx outlook partition patch port product proxy raid rds reformat remotedesktopconnection retail screen server. sp1 sp3 spyware studios ubuntu unreadable update upgrade usb verizon videogames virtual virus vulnerability wab webos weecam win win32/heur window windows windows7 windowsxp worm xp





