New Build Will Not Post

By alphamale
in Hardware Hangout

 Share

Recommended Posts

Community Regular

alphamale

Posted
Posted

hi

i built a new computer and put it place today and hooked everything up and turned it on and it will not post. i get the bios screen and then nothing just sits there. i unplugged it and took to my bench where it was assembled and it fired right up. runs like a top and did so for maybe 36hours before i moved it. i updated 7 and did scans and defrags and turned it on and off many times before moving it.

so on the bench it has a ps2 mouse and a usb keyboard and an old monitor. thats it. not the case in its work area.

in the work area i have new connected to box:

external siig usb/card reader connected by usb

27' planar monitor connected by hdmi

keyboard, mouse, wired, by usb

usb connection to the surge protector

usb connected inkjet printer

the usb scanner never got hooked up.

build is:

ga-z77x-d3h board

intel i7 3.5

gskill f3-1600c9d x2 x8g

pc power 600w supply modular

2 hd

external usb floppy

when i ordered i had another supply selected maybe it was 750, out of stock and so i took the alternate. is it possible the usbs are sucking the power and preventing post? the usbs in use sit on the board

any educated guesses?

Link to comment
https://www.neowin.net/forum/topic/1132754-new-build-will-not-post/
Share on other sites
Grand Master

Yusuf M. Veteran

Posted
  • Veteran
Posted

Try booting it up with just the mouse, keyboard, and monitor connected. If that works, then add each device one by one. Sometimes, there's an issue with booting up while a USB device is connected. It used to happen to me years ago with Windows XP. I have to unplug a USB device (usually a thumb drive) and plug it in after I boot to the desktop.

Rising Star

tim_s

Posted
Posted

Try booting it up with just the mouse, keyboard, and monitor connected. If that works, then add each device one by one. Sometimes, there's an issue with booting up while a USB device is connected. It used to happen to me years ago with Windows XP. I have to unplug a USB device (usually a thumb drive) and plug it in after I boot to the desktop.

Yes because the USB is on the bus

Either,

A: Remove the usb devices and try again.

B: plug in the USB devices when plugging into the test environment.

Community Regular

alphamale

Posted
  • Author
Posted

you are spot on with the trouble shooting steps. i described the problem and asked about the underlying cause. if it is really the lack of power or a bad supply on this new box i will change it out. the supply is modular and i never wanted one of those it just sounded like trouble and some how i bought one.

i am not lazy but the effort to eliminate and replicate is greater than supply replacement if that was a weighted possibility and then the trouble shooting would be required. it just feels like a power issue. on my bench it boots, move it and plug everything up and bam... trouble.

thank you for the replies

Grand Master

articuno1au

Posted
Posted

Nothing wrong with modular supplies.

90%+ of the top end power supplies are modular and work perfectly.

It's useful just to get rid of the cable clutter >.<

Also, the trouble shooting steps seem easy enough O.o I'd just run them. First thing that came to my mind was a USB conflict.

Rising Star

tim_s

Posted
Posted

i am not lazy but the effort to eliminate and replicate is greater than supply replacement if that was a weighted possibility and then the trouble shooting would be required. it just feels like a power issue. on my bench it boots, move it and plug everything up and bam... trouble.

thank you for the replies

Nobody can tell you how to spend your money lol

Grand Master

Astra.Xtreme

Posted
Posted

The best advice here is to unplug everything except the power cord and monitor. See if it boots, and if it does, progressively plug things in until it doesn't boot. Then you'll have the culprit. More than likely it's something USB that's holding everything up. You could go into BIOS and mess with the boot settings if you want.

Of if you can get into BIOS, check the voltages levels. If any of them are off by a decent margin, then yeah it's your power supply. If they all match, then your power supply is fine.

Let us know if that works or not.

Community Regular

alphamale

Posted
  • Author
Posted

i will just follow up to close this out. i wanted to be sure that the power supply was adequate and not causing the issue, but before i went to that trouble i tested the new hdmi cable and the new keyboard the very basic stuff and it was the new keyboard. i have worked with computers for years and never had a usb keyboard stop boot. computer is a nice build that should love me long time. so i will exchange keyboard for new one. so thanks for your replies.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By Slugsie · Posted

      The machines are starting to fight back any way they can.
    • Linux 7.1 arrives with an NTFS overhaul and major hardware performance boosts

      By Accuphase · Posted

      No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By zikalify · Posted

      Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • Microsoft confirms Recycle Bin bug across all versions of Windows

      By snowy owl · Posted

      I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs

      By hellowalkman · Posted

      Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.

  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post

  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!