Surface Pro (2017) vs Surface Pro 4
I have a couple of strange and very vexing problems. The shop returned it saying it the problem was too infrequent for them to solve (sometimes it's very frequent and sometimes it isn't). Does anyone have an inkling of an idea what I could do to fix this?
(I posted this yesterday in tech consumer forum by accident, so sorry for the repost)
Bootproblems (for 1.5 years now and increasing in frequency):
When the start-up button is pressed, there's always sound (so something is starting), but nothing boots (no BIOS, no ASUS express gate, nothing). Sometimes it takes a couple of minutes (or much more than a couple) of hard resets to get the system to boot. Somtimes it automatically boots after a couple of minutes (or much more than a couple) of pressing the button.
Crashes (for about a year now)
My computer freezes, shuts down (and restarts), has BSOD's (often PFN_List corrupt), grey screen, columns of colors (with the cursor unaffected), rows of colors (with the cursor affected). There appears to be no pattern in when it's bound to happen. It used to often happen more often dring the quiet moments and around an hour after a game had been played on it (though rarely during). Now it appears mostly random, though I believe stressing it does increase the risk now.
Audio devices not recognised (for about a week or two)
My computer doesn't recognise any audio jack (nor microphone), neither at the front or at the back. They don't show up in the list of audiodevices (also not with "show disconnected" or "show disabled". When I connect my TV (with internal speakers) via HDMI, the audio works perfectly. Keyboard doesn't work in boot menu (to start windows normally or otherwise), but does work in BIOS or Windows itself. (for about a week or two)
My mouse (USB-connection) had moments where it automatically disconnected (and often connected again) for a while.
Problem persists after formatting the hard drives or using a different hard drive to install Windows on.
Problem persists with Ubuntu instead of Windows installed.
Problem persists with different plug, cables, speakers, keyboard, mouse or screen.
1 x CooMas GX650 650W ATX2
2 x Arctic F8 PWM 80X80X25
1 x Asus M4A79T Del.790FX F RG SA
1 x AMD X4 II965 AM3 3400 BLACK 8M
1 x G.Skill Ripjaws X 8GB (1600MHz, 240-polig, 2x 4GB) DDR3-RAM
2 x Samsung 1 TB SAT2 HD103SJ
1 x XFX 1GB D5 X HD5850 Black Edition R
1 x Sams 22x DL SATA SH-S223C BlB
1 x Iiya 22,0 E2208HDD-B1 CCFL
Agreed - I would also strip down PC, clean and rebuild in case of loose connections.
Check out power switch on case, quick way, use reset switch instead
I replaced my PSU yesterday with a new one (Corsair CX750wM) and the audio is fixed, the keyboard works everywhere, but I still get;
- Crashes (so far 3. different colors, but always vertical lines)
- Boot-up problems. When turned on, it doesn't always actually boot the system (though it's on as I can open discs and hear some noise inside).
- (There was also a moment where my CPU seemed to be between 90-100% for no reason. But that settled after a while)
Would a graphic card problem cause the system not to boot? Is it perhaps my motherboard or processor (damaged by my damaged psu or by the same cause that damaged my psu)?
Has the motherboard it's own graphics chip (onboard)? I would remove the dedicated card and connect the monitor to the onboard one. BIOS should automatically detect this. See if any better.
Took me a bit too long to figure out, but my motherboard doesn't have an onboard graphic chip. Could you explain your reasoning a bit? Is it possible for a graphics card to mess with booting? What can I exclude?
My computer had trouble starting up at all in the meantime, so I put in my old PSU again and it could boot again. The keyboard and audio worked there again too. Unfortunately, it still crashes and freezes at every possible point.
Then I think we may be looking at a corrupt boot files possibly due to a dying Hard drive.
- Scan for malware and virus
- do a disk check on your drives for bad sectors
- try running something like memtest to check the RAM
Thank you, but I have to add: - The problem precedes a change of RAM - The problem persists on a different OS on a different hard drive
Oh dear that now only leaves a faulty main board.
This thread is now locked and can not be replied to.