Solved

Complete mess of a first build. No post after 1mo working.

So, forgive me if this is in the wrong spot I wasn't entirely sure where to put this. I put together my first machine a little over a month ago. Everything went relatively smoothly and I was playing games without a problem, until about a week and a half ago.

In the middle of a game the computer shut off. No blue screen, no freeze, no lag, just shut off. On restart, I was stuck in an infinite boot loop with only the motherboard logo. I tried new RAM, tweaked around in the BIOS, etc. After TONS of fiddling, including a wipe of the SSD, I was finally able to get to the windows logo screen with the little balls that go in a circle. (attempting to reinstall windows 10 from USB) It would stay on that screen for about 30 minutes and then BOSD with error Unexpected_Kernel_mode_trap. Now, google told me that most people just let it run through this error and loading sequence a few times and eventually it worked, so I let it run all night with no luck. Next morning, I restarted and looked around the BIOS since what I was doing obviously wasn't working. My SSD was in a frozen state so I cleared it, but that didn't work either. I found someone who had a very similar problem to mine and they fixed it by updating the BIOS. Now, I have never done anything technological in my entire life before this and 99% of these terms I learned in the last week and a half so I went ahead and flashed the bios to the newest version from ASUS for my mobo. Now it's on Q-code 35 with no post, no bios, no beeps (there has never been any beeps, though). I checked the CPU for bent pins, reseated the ram, unplugged everything that isn't essential and still nothing. I understand now that apparently flashing the bios is one of the best ways to brick your mobo.

I don't know where to go or what to try from here. Am I just doomed to buy a new mobo? What if I still have the same problems even with the new mobo?

Honestly I am so incredibly tired of trying to fix this thing. I've sunk over 1600 into it so far and for not even a month of use.

I am not 100% sure what information to post so please let me know what you need and how to get it. The motherboard is an ASUS Maximus VIII Ranger z170
14 answers Last reply Best Answer
More about complete mess build post 1mo working
  1. It might be useful for you to post your full settings. If this Q-code 35 appeared straight after you updated your BIOS, could you try resetting the CMOS via the header/removing the CMOS battery.

    If it was me in this situation at this stage I would probably go back to square 1 and try booting the PC with just 1 RAM stick, the CPU and the monitor plugged into the onboard graphics. If you can get into BIOS no problem like this then reconnect your SSD and try booting to windows at that point.
  2. I've tried clearing the CMOS and booting with bare minimums but I still have the same problem. The SSD doesn't have windows installed, it's empty, I forgot to mention I was trying to boot from USB windows ISO when the boot loops / logo screen issues were happening. I haven't heard of a CMOS battery but I'll try looking for one
  3. found the battery, removed and reseated it. only things on are 1 stick of 8gb DDR4 ram, the CPU and the PSU, monitor plugged in via HDMI directly to motherboard. Still no post with Q-code 35.
  4. Dustybin said:
    It might be useful for you to post your full settings. If this Q-code 35 appeared straight after you updated your BIOS, could you try resetting the CMOS via the header/removing the CMOS battery.

    If it was me in this situation at this stage I would probably go back to square 1 and try booting the PC with just 1 RAM stick, the CPU and the monitor plugged into the onboard graphics. If you can get into BIOS no problem like this then reconnect your SSD and try booting to windows at that point.


    This is a stupid question, but what do you mean by full settings?
  5. goinginsane said:
    Dustybin said:
    It might be useful for you to post your full settings. If this Q-code 35 appeared straight after you updated your BIOS, could you try resetting the CMOS via the header/removing the CMOS battery.

    If it was me in this situation at this stage I would probably go back to square 1 and try booting the PC with just 1 RAM stick, the CPU and the monitor plugged into the onboard graphics. If you can get into BIOS no problem like this then reconnect your SSD and try booting to windows at that point.


    This is a stupid question, but what do you mean by full settings?



    Sorry, it is my fault I meant to say Full Specs i.e. PSU, GPU, RAM (model).
  6. I am kinda interested in your PSU model mainly, the initial symptoms of it switching off etc could easily have been caused by a fault with the PSU and there is some discussion (after doing some digging) of PSU issues being often related to an ASUS board getting suck on q-code 35.
  7. Dustybin said:
    goinginsane said:
    Dustybin said:
    It might be useful for you to post your full settings. If this Q-code 35 appeared straight after you updated your BIOS, could you try resetting the CMOS via the header/removing the CMOS battery.

    If it was me in this situation at this stage I would probably go back to square 1 and try booting the PC with just 1 RAM stick, the CPU and the monitor plugged into the onboard graphics. If you can get into BIOS no problem like this then reconnect your SSD and try booting to windows at that point.


    This is a stupid question, but what do you mean by full settings?



    Sorry, it is my fault I meant to say Full Specs i.e. PSU, GPU, RAM (model).


    I am a 22 year old girl who had my older sister buy me the pieces (lol) so I am not 100% sure but this is what I have listed on the papers from newegg:
    MB: ASUS Maximus VIII Ranger z170
    VGA MSI GTX 970 4GD5T OC RT
    CPU Intel Core i5 6600k 6M 3.90 G R
    SSD 250g Samsung Mz-75e250b AM R
    MEM 8G*2 GSK f4-2400c15g-16GVR RT (Ripjaws V)
    CPU Cooler CM RR-212E-20pk-R2 R
    PSU Raidmax Hybrid2 RX-630ss 630W
    KB&MS Cooler Master DevastatorII BL R

    If it looks like I missed anything let me know I will try and find it! :)
  8. The PSU in the system is low quality (I suspected it might be), my suggestion to you would be that you replace it with a good quality unit. A bad PSU can cause a myriad of problems for your system including damaging other parts.

    http://www.tomshardware.co.uk/forum/id-2547993/psu-tier-list.html

    Any PSU in the first 2 tiers should be fine for your system specs.
  9. Dustybin said:
    The PSU in the system is low quality (I suspected it might be), my suggestion to you would be that you replace it with a good quality unit. A bad PSU can cause a myriad of problems for your system including damaging other parts.

    http://www.tomshardware.co.uk/forum/id-2547993/psu-tier-list.html

    Any PSU in the first 2 tiers should be fine for your system specs.


    Thank you! I will try this. Do you think any of the other parts are already damaged? Should I try replacing the mobo anyway?
  10. It is possible your motherboard, CPU, RAM or anything else could have gone pop when this went wrong. Really if changing the PSU doesn't resolve the issue you should look into either returning your motherboard or taking the system to a local shop for diagnosis. Since the system didn't work with just CPU, RAM, Motherboard and PSU you can at least concentrate on those parts.
  11. Dustybin said:
    It is possible your motherboard, CPU, RAM or anything else could have gone pop when this went wrong. Really if changing the PSU doesn't resolve the issue you should look into either returning your motherboard or taking the system to a local shop for diagnosis. Since the system didn't work with just CPU, RAM, Motherboard and PSU you can at least concentrate on those parts.


    Ok, thank you. Unfortunately I can't return the motherboard it's past the return dates by a few days. But, I'll get the new psu and try a local shop if it doesn't work. My $1600 system is quickly turning into a hell of a lot more LOL. Thank you for the help! :)
  12. No worries, glad I could be of help. If the store return date has past you should still be able to get a warranty replacement from ASUS if you've only had the motherboard a couple of months. I don't know what country you're in and you will probably have to pay postage but it should be cheaper than buying a new board.

    Good luck though!
  13. Dustybin said:
    No worries, glad I could be of help. If the store return date has past you should still be able to get a warranty replacement from ASUS if you've only had the motherboard a couple of months. I don't know what country you're in and you will probably have to pay postage but it should be cheaper than buying a new board.

    Good luck though!


    Thank you! After trying all night to get their RMA form to load it finally went through and I was given a number. The instructions are a tiny bit confusing, but basically they said put the cpu cap on, pack it with 3 inches of padding (they said packing peanuts?) on all sides and use a tracked shipment method.

    So I put it back into the original box it came in? Or just loose in the box with padding? What is the best way to pack a motherboard for RMA?
  14. Best answer
    If you have the box and the anti static bag it came in then that is ideal. Personally I will always put electronics in an anti static bag and then inside a cardboard box (the original box is best). I will then wrap the bubble wrap around the box then normally put that inside a shipping bag. I worked for a small computer shop selling spare parts for a while and we never got negative packing feedback with this method.
Ask a new question

Read More

no post Motherboards New Build