FORUMS

Top-Beitragende letzte Woche
1
Stan_Nur Points: 507 Lv 30
2
9389998 Points: 279 Lv 30
3
Karkas12 Points: 245 Lv 30
4
CATeX Points: 243 Lv 30
5
ricroon Points: 202 Lv 30
6
McMurphy_YouTub... Points: 190 Lv 30
7
Peetstar Points: 176 Lv 30
8
Valllyy Points: 166 Lv 30
9
WHURL Points: 163 Lv 30
10
BEAM ME UP! Points: 158 Lv 30

X51 R2 intermitted booting issues

  • 36

After having this issue for a while, and trying a fresh boot to see if there was "something" else at play, I'm scratching my head about an intermittent problem with the X51 not booting consistently.

I've changed the PSU (existing 330w to new 330w), done a few fresh installs, switched from a DVI to HDMI monitor and cable and run various memory stress tests etc, with no success.

The problem is that about 50% of the time when booting from cold, the Alienware face will appear, then black screen, then the face reappears and the circle of dots (windows 10) goes around a few times, then black screen again and nothing more.  Fans continue to whirr, lights are all on, but no mouse trail on screen, nothing, no response to keyboards, disc access appears to continue for a short period.  Pressing the power switch powers down the machine more or less instantly at that point.  If I leave it powered up for a long time, nothing else happens.

Mostly it runs crash free when in use, though there are occasional crashes.

I'm just wondering how to debug this.  I'm fairly happy it's not the OS or drivers given the number of fresh installs, and as it happens at boot it's not likely to be an app crashing.  

So I'm thinking it's more likely some intermittent fault with a component - most likely culprit being the the graphics card, which would be an expensive replacement to test.

Does this fault seem consistent with ones anyone else has had?  Any suggestions for how to debug this fully?

Antworten • 3

Have you tried booting into safe mode with recovery media?


No, but as the issue is one at boot time, how might that help?  It's intermittent and I've not detected a repeatable pattern, but it will sometimes occur after an actual crash of the machine, and sometimes occur when the machine is being booted clean from cold.  So I can't pin it down to either over-heating, or a driver / software in use problem.

I can / will try booting with a recovery media, but unless I permanently used that boot route and discovered that the issue I have never presents itself under those circumstances, I can't see how using that method would help at all.  

Plus, as I said, I've done at least two completely fresh installations and the issue re-arose almost straight away, so I'd have thought that any corrupted software / drivers etc would be able to be ruled out.

Is there a log of memory that I can access post-failure (on the next successful boot) that might help?  I've read that enabling Ctrl ScrlLk to capture memory output from a frozen PC can be used in some circumstances, not sure whether that would be available to me?


(Edit, just realised I've posted under an old account - both Hillside and larkim are me / the same).