Strange boot problem (non-serious)

[Hatsjer]

Hello there. 

 

My strange random boot problem stars with a normal BIOS loading and posting, and when it begins to load windows; Neither of my two screens (HDMI (primary) & DVI-D) recieves any input. 

A quick hard reset fixes this issue. It has so far never occured more than twice in a row. - I always do a complete shutdown. System is 2 months old at most by the time of writing.

 

At first I though it was the video card which was faulty, as I had an other issue, which caused lots of red horizontal one pixel one frame lines to appear. They increased with more information which was being outputted, but after I swapped my HDMI cable, haven't I seen them since, poiting it was possibly my cable who was faulty.

 

Something however game me the feeling it was NOT the videocard which was faulty, as my keyboard who got built in sleep mode, and it did not respond to it. Two days ago while my computer was off did I bump into a bottle, which hit my keyboard, and the keyboard light it's light up, as it was woken up from sleep / idle mode. I powered on my computer, and neither of my screens recieved any input after BIOS posting. I don't know if this is relevant, but when checing my CPU usage, does task manager says my computer has been powered for days, even though I do a full shutdown every night. 

 

Aside from my screens not recieving any input, have I not detected any other issues, but I fear it may get worse, and would like to get it fixed. 

 

My specs are: 

Case: Fractial Design Define R5 Black

Storage: 1 500GB Samsung 960 EVO SSD + 1 4TB (old) HDD

CPU: Intel i7 7700k (not OCd)

GPU: MSI GeForce GTX 1070 Armor OC

CPU cooler: Corsair hydro series H100i V2

MB: Asus prime Z270-A S-1151 ATX

PSU: Corsair CS650M 650W 80 gold +

RAM: Corsair Vengance LPX 16 (8x2)

OS: win 10 64 bit (does there exist win 10 32 bit?)

 

https://puu.sh/vSG6M/25689d2d86.png

 

DxDiag attached.

DxDiag.txt

[Anghammarad]

Sounds like a config issue regarding shutdown that your machine just wents into hibernate/suspended mode. The Shutdown option in windows 10 has many options behind it in the settings. That would explain the uptime in the task manager.

 

to your question, yes there are 32 bit win 10 editions, but honestly, who today has a machine with less than 4 gigs ram... *shrug*

[Hatsjer]

8 minutes ago, Anghammarad said:

Sounds like a config issue regarding shutdown that your machine just wents into hibernate/suspended mode. The Shutdown option in windows 10 has many options behind it in the settings. That would explain the uptime in the task manager.

 

to your question, yes there are 32 bit win 10 editions, but honestly, who today has a machine with less than 4 gigs ram... *shrug*

Hmm. That would make sense. I have sleep, shutdown & restart. Putting it into sleep mode via my KB, will wake my computer my just moving my mouse. 

During the incident when my KB lit up while the comp was off, did nothing wake my computer, othen than the power button. 

 

My two bosses has 3 old desktop computers running non-stop (never shuttting them down. I have seen uptime of 40+ days) with 2 GB of ram. It shouldn't be a surprise with the fact out of the 5 of us at work, am I the tech guy. 

Edited August 16, 2017 by Hatsjer
was -> wake

[Anghammarad]

 

4 minutes ago, Hatsjer said:

Hmm. That would make sense. I have sleep, shutdown & restart. Putting it into sleep mode via my KB, will wake my computer my just moving my mouse. 

During the incident when my KB lit up while the comp was off, did nothing was my computer, othen than the power button. 

 

My two bosses has 3 old desktop computers running non-stop (never shuttting them down. I have seen uptime of 40+ days) with 2 GB of ram. It shouldn't be a surprise with the fact out of the 5 of us at work, am I the tech guy. 

I forgot to mention, the screen being black after bios post is an old known issue with sleep/hibernate and windows. 

 

Hibernate, iirc was included with 2000 pro, my old company laptop had that and I liked using that feature a lot, because a celeron 400 with 500 megs ram wasn't a rocket in starting up =P. From the days I used that feature I know that screen keeps being dark because the pickup of windows was borked. Hard off and reboot was the only option then. 

 

Aunt Edit reminds me:

 

In the settings of win 10 (don't remember which exactly) you could change what "Shut Down" is doing. For example when you chose shutdown, it goes into hibernate instead, or suspended mode instead of shutting down.

[Hatsjer]

1 minute ago, Anghammarad said:

 

I forgot to mention, the screen being black after bios post is an old known issue with sleep/hibernate and windows. 

 

Hibernate, iirc was included with 2000 pro, my old company laptop had that and I liked using that feature a lot, because a celeron 400 with 500 megs ram wasn't a rocket in starting up =P. From the days I used that feature I know that screen keeps being dark because the pickup of windows was borked. Hard off and reboot was the only option then. 

 

So we can atleast all agree this is a software-only problem?

[Anghammarad]

Just now, Hatsjer said:

So we can atleast all agree this is a software-only problem?

From what I see/read I would hint to that. All clues you provided go in that direction.

[Hatsjer]

Just now, Anghammarad said:

From what I see/read I would hint to that. All clues you provided go in that direction.

That's a major relief. Not having to worry abut any faulty hardware and warranties and all that stuff.