24682
Views
6
Replies
3
Participants
Last post by
phbk,
Jump to Latest
Hey guys, so up until now, this machine has given me nothing but trouble. At first the motherboard would hang randomly during BIOS, then it kept scrambling boot order around, and now this. After I got it running, a week later it fails to boot and stalls at the Q-code B4, or «USB Hot plug».
At first, I saw this before the hang:
Code:
Code:
USB Device Found: Generic-CompactFlash 1.01Normally, after this, it lists all the USB devices, which includes the front panel card readers and keyboard+mouse, plus some things like «AMI Virtual Floppy0». So I disconnected my front panel card reader, since that’s where it hung up, and restarted. Still error B4 but with nothing showing.
I have removed every USB device from the system, including the keyboard and mouse, and switched to a PS/2 keyboard, but it still hangs at B4 every time…
Motherboard is ASUS Z10PE-D16 WS with two Xeon E5-2650 V3’s.
Try updating the BIOS to the latest version and clearing the CMOS.
If it still gives you issues, I think that you might have a defective motherboard. The USB controller looks like it’s problematic.
Are you still in the return period? I’d consider the possibility of getting it exchanged for a good one.
It’s 2 days past of the return window.
I’ll try clearing the CMOS. Part of me thinks those AMI Virtual USB drives have something to do with this, but there’s no way to disable them if I can’t access the BIOS setup.
See less
See more
1
I’d recommend you contact the seller and see if you cannot arrange for something. Usually if it’s a couple of days, they won’t freak out. Ask about bringing them the system in maybe.
Another option is to RMA back to Asus. Make sure you take extensive pictures though, as Asus RMA can be problematic. I’d check to see if there is a Z10 club here on OCN as well and ask about it, along with their support forums.
Quote:
Originally Posted by CrazyElf
I’d recommend you contact the seller and see if you cannot arrange for something. Usually if it’s a couple of days, they won’t freak out. Ask about bringing them the system in maybe.
Another option is to RMA back to Asus. Make sure you take extensive pictures though, as Asus RMA can be problematic. I’d check to see if there is a Z10 club here on OCN as well and ask about it, along with their support forums.
The seller was Amazon, but I suppose I can still contact them about it.
Could you point me towards the Z10 club thread? Which forum would that be in?
Possible solution — Worked for me.
I have experienced this issue as well, and I may have the solution.
For me, it was also hanging in boot with «Press F2 or Del to enter BIOS» longer than normal, i normally dont see it for more than 1 sec, if that long.
Not it was there for about 20-30 secs, and ends with «Error. Press F1 to enter BIOS»
It all began when I bought a new keyboard from Corsair, but even when I unplugged it, it still had the error.
I also have had a SSD disc attached temporary the day before, so I thought it may have been me interfeering with my existing drives, that made the error.
I read as well that it was due to USB the error came.
However after having tried alkot, I noticed than when entering BIOS with F1, it always displayed a wrong date. Like 1900 or something (don’t have pictures, sry.)
Then I knew what was wrong…
All my computerparts are connected to same power output, and I always switched it off, to shut down printers etc.
I bought a packet of CR2032 batteries, and changed the one on the motherboard (also a CR2032)
After that new battery came in, my problems were gone.
Cheap and simple way to try out.
Hope this helps others.
See less
See more
I have experienced this issue as well, and I may have the solution.
For me, it was also hanging in boot with «Press F2 or Del to enter BIOS» longer than normal, i normally dont see it for more than 1 sec, if that long.
Not it was there for about 20-30 secs, and ends with «Error. Press F1 to enter BIOS»
It all began when I bought a new keyboard from Corsair, but even when I unplugged it, it still had the error.
I also have had a SSD disc attached temporary the day before, so I thought it may have been me interfeering with my existing drives, that made the error.
I read as well that it was due to USB the error came.
However after having tried alkot, I noticed than when entering BIOS with F1, it always displayed a wrong date. Like 1900 or something (don’t have pictures, sry.)
Then I knew what was wrong…
All my computerparts are connected to same power output, and I always switched it off, to shut down printers etc.
I bought a packet of CR2032 batteries, and changed the one on the motherboard (also a CR2032)
After that new battery came in, my problems were gone.
Cheap and simple way to try out.
Hope this helps others.
See less
See more
- This is an older thread, you may not receive a response, and could
be reviving an old thread. Please consider creating a new thread.
Hi guys,
I hope someone can help me!
I purchased the X470 ROG Crosshair VII Hero board with an AMD 2700X and 16GB of G.Skill 3600MHz CAS 16 RGB Ram.
The rest of the system is: MSI GTX 1080Ti Gaming X, Samsung 850 Evo 500GB SATA M.2, 250GB 850 Evo SSD and a 1TB WD Blue HDD.
I am running Windows 10.
So basically, every now and then — way too often to be honest — when I boot my PC up from off, it will stick on the screen for bios (the one where it says press DEL or F2) and stays there forever. The mouse and keyboard aren’t active so now way to do anything other than hard power off.
I have tried disconnecting all USB devices (including the front panel for the case), removing one stick of Ram, clear cmos, the 2 pin bios reset (with a screw driver), and just about everything else!
My bios is the latest (0702) but this has been happening since day 1.
Somtimes it will boot up just fine and others I will be restarting, clearing cmos, resetting everything over and over for hours just to get back to WIndows.
I am now at the point where I don’t shut my PC down… Ever. Which is wrong when I have just dropped £750 on this upgrade,
This is my first Asus or ROG board and so far I am just frustrated and starting to wish I’d stuck with MSI!
Any help would honestly be very much appreciated!!
All the best,
Iain.
- Категория: Инструкции
-
В данном материале представлены все известные POST-коды на Китайских материнских платах LGA 2011 и LGA 2011-3. Если вы например столкнулись с проблемой запуска системы то по номеру кода можно узнать в чём причина неполадки, что значительно облегчает выявление неисправности. Если ваша плата оснащена пост картой — это огромный плюс, вы всегда будите в курсе, система работает исправно или нет.
Если после запуска системы всё в порядке, POST-код должен быть АА, если он другой, то стоит посмотреть на расшифровку кодов ниже и выявить причину.
Для быстрого поиска нажмите Ctrl+F и введите искомый код.10 PEI Core is started.
11 Pre-memory CPU initialization is started.
12~14 Reserved.
15 Pre-memory North-Bridge initialization is started.
16~18 Reserved.
19 Pre-memory South-Bridge initialization is started.
1A~2A Reserved.
2B~2F Memory initialization.
31 Memory installed.
32~36 CPU PEI initialization.
37~3A IOH PEI initialization.
3B~3E PCH PEI initialization.
3F~4F Reserved.
60 DXE Core is started.
61 NVRAM initialization.
62 Installation of the PCH runtime services.
63~67 CPU DXE initialization is started.
68 PCI host bridge initialization is started.
69 IOH DXE initialization.
6A IOH SMM initialization.
6B~6F Reserved.
70 PCH DXE initialization.
71 PCH SMM initialization.
72 PCH devices initialization.
73~77 PCH DXE initialization (PCH module specific).
78 ACPI Core initialization.
79 CSM initialization is started.
7A~7F Reserved for AMI use.
80~8F Reserved for OEM use (OEM DXE
initialization codes).
90 Phase transfer to BDS (Boot Device Selection) from DXE.
91 Issue event to connect drivers.Regular Boot
92 PCI Bus initialization is started.
93 PCI Bus hot plug initialization.
94 PCI Bus enumeration for detecting how many resources are requested.
95 Check PCI device requested resources.
96 Assign PCI device resources.
97 Console Output devices connect(ex.Monitor is lighted).
98 Console input devices connect(ex.PS2/USB keyboard/mouse are activated).
99 Super IO initialization.
9A USB initialization is started.
9B Issue reset during USB initialization process.
9C Detect and install all currently connected USB devices.
9D Activated all currently connected USB devices.
9E~9F Reserved.
A0 IDE initialization is started.
A1 Issue reset during IDE initialization process.
A2 Detect and install all currently connected IDE devices.
A3 Activated all currently connected IDE devices.
A4 SCSI initialization is started.
A5 Issue reset during SCSI initialization process.
A6 Detect and install all currently connected SCSI devices.
A7 Activated all currently connected SCSI devices.
A8 Verify password if needed.
A9 BIOS Setup is started.
AA Reserved.
AB Wait user command in BIOS Setup.
AC Reserved.
AD Issue Ready To Boot event for OS Boot.
AE Boot to Legacy OS.
AF Exit Boot Services.
B0 Runtime AP installation begins.
B1 Runtime AP installation ends.
B2 Legacy Option ROM initialization.
B3 System reset if needed.
B(4,5) USB(PCI) device hot plug-in.
B6 Clean-up of NVRAM.
B7 Reconfigure NVRAM settings.
B8~BF Reserved.
C0~CF Reserved.
E0 S3 Resume is stared(called from DXE IPL).
E1 Fill boot script data for S3 resume.
E2 Initializes VGA for S3 resume.
E3 OS S3 wake vector call.S3 Resume
F0 Recovery mode will be triggered due to invaild firmware volume detection.
F1 Recovery mode will be triggered by user decision.
F2 Recovery is started.
F(3,4)Recovery firmware image is found(loaded)
F5~F7 Reserved for future AMI progress codes.
50~55 Memory initialization error occurs.
56 Invalid CPU type or speed.
57 CPU mismatch.
58 CPU self test failed or possible CPU cache error.
59 CPU micro-code is not found or micro-code update is failed.
5A Internal CPU error.
5B Reset PPI is failed.
5C~5F Reserved.
D(0,1,2)-(CPU,IOH,PCH) initialization error.
D3 Some of the Architectural Protocols are not
available.
D4 PCI resource allocation error. Out of Resources.
D5 No Space for Legacy Option ROM initialization.
D(6,7) No Console Output(input) Devices are found.
D8 It is an invaild password.
D9~DA Can’t load Boot Option.
DB Flash update is failed.
DC Reset protocol is failed.
DE~DF Reserved.
E8 S3 resume is failed.
E9 S3 Resume PPI is not found.
EA S3 Resume Boot Script is invaild.
EB S3 OS Wake call is failed.
EC~EF Reserved.
F8 Recovery PPI is invaild.
F9 Recovery capsule is not found.
FA Invalid recovery capsule.
FB~FF Reserved.
Дополнительная информация:
I was in a hurry when i type this post so i wasn’t able to give my full system specs.
CPU: fx8350 stock speed
GPU: XFX r9 280x stock speed
MOBO: MSI 970 Gaming
HDD: 1TB Seagate
SSD: Corsair 128GB LX
PSU: EVGA 850w Bronze
DVD player
Keyboard: Razer Arctosa
Mouse: 3-Lue Gaming Mouse
Also to add on, i saw this code just when i turn on my pc before i post this very post «9C» would you be willing to define what that is so a noob can understand? Also, when the 9C code pooped up, the screen just stays black and didnt proceed to the bios.
So here is the full story:
I Upgraded my system with a new mobo, ssd, psu and HDD.
Mobo: MSI 970 gaming
SSD: Corsair LX 128GB
HDD: Seagate Baracuda 1tb
PSU: EVGA 850w
The gpu, ram, cpu are all the same.
So when i upgraded my system with the new component mentioned above and downloaded OS, things started to go downhill. The most ANNOYING thing ever is when my pc refuse to boot when cold booted. So when i turn on my pc after school, all the fan would starts, cpu, case, gpu everything but monitor just stays black. All i can do is click the restart button maybe once, twice or three times before my pc would properly boot to bios and eventually to windows. Sometimes some codes would pooped up (see first post) most of the times the code 99 would pooped up and it proceed to the bios and to windows. But sometimes it can also show another type of codes (see first post) and it could either boot to windows normally, or the screen would just stays black and the code is on the bottom corner.
Could this be a driver issue? I do have a razer keyboard, but i dont have any of their fancy software installed and i heard razer can cause some incompatibility, but i dont know.
i unplug my GPU and plugged it in again and the problem still persist.
I change my ram to different slots and the problem still persist.
Things i need to try:
1. re-arrange my sata cable ordering because currently i have my ssd (which holds my OS) on the last slot)
2. move my GPU to the second PCI express lane
3. Unplug my razer keyboard and uninstall any trace of razer software, plugged in some other keyboard and see if it works
4. Try booting without any thing connected to the motherboard, such as mics, mouse, keyboards and such
5. «fix» my HUD cables because i have a corsair air 540 and their USB, audio etc cables are all black, so i dont know which one is positive or negative. (This case does have HDD light thingy, and it wasnt working before, so i just flipped the cable around and boom it works, so i can try something similar with the other sets of cables)
Any suggestion? My previous motherboard was this Gigabyte motherboard and this same setup (except for the SSD and the motherboard of course) worked flawlessly. Im not trying to bash MSI here, im just saying that when i upgraded my MOBO, problem started to appear. So could this be a compatibility issue with MSI motherboard and the rest of my setup?
p.s. i got this mobo from newegg and if you read some of the reviews, some of them posted their rig and more or less they have the same specs as i do… Kinda weird that i am getting this problem.