What's new

Third New Problem: Aggressive CPU Slowdown

Status
Not open for further replies.
You should never defrag an SSD @mimarsinan - I don't see any of these issues it would appear you have an axe to grind or perhaps a fix to sell...

Hold your horses cowboy, maybe you yourself have an issue with users who have legitimate real world problems that you don't know how to solve?

*Read* if you want to help, suppress the urge to reply if you don't have anything to contribute.

I wrote that I am trying to TRIM the thing, and the software, not recognizing its an SSD, is defragging it instead.

Got it?
 
I think the key here is that he re-imaged the machine before he used it. One of the problems he reported he's seeing on his SP4 as well. Sounds like his OEM Windows 10 image may have some Surface driver problems. I've never felt a need to reimage a machine I just took out of the box before trying it first to see if there were any problems.

No, I imaged the machine in its factory state before booting up into the out-of-the-box experience.

Once you've figured out what that is, you might find its a useful trick.

Keeping fingers crossed!
 
Last edited:
Exactly this. I had a few problems on my machine, so sent it back for a replacement. I did spend a few days trying to rectify things... but why bother? It's a brand new machine and under warranty so you're completely within your rights to ask for a free replacement. It sucks but hey, shit happens (to any kind of hardware)

Quit your moaning :)

If it happens on your replacement Surface too... well then that's another conversation altogether.

I love your positive attitude!

There's been users who've returned machines umpteen times, and left wondering why they're having issues.

Hint: Its a software/firmware issue.

Read the blurry text post:
Blurry Text

Read the defrag post:
Defrag Problem

Contribute some benchmarks here:
Surface Pro 2017 Benchmarks (and Anomalies)

And trust me, if you've been through each generation of this device, each with their own unique problems - you're bound to get grumpy.

Like I wrote earlier...I'd use a Mac if I could.

These machines are endless trouble.
 
Too many old school nerds/geeks and IT people try to do old school ways of handling new technology. I always teach my IT people to provision and manage new systems - just say no to destructive imaging and "Fat" Images...

And honestly - IT Professionals don't know better than the OEMs on these modern mobile devices.

As hopeless as the machines are, their users are too, apparently!

You're replying to your own "idea" of what's going on and drawing conclusions about an "old school" guy and even offering gratuitous advice based on your entirely mistaken understanding of the situation.

First, take your advice - all of it - and shove it, its useless.

Next, put your skin in the game by doing your own research. That means, you first have to *read* what's been shared.

Is that a novel concept?

Reading...you do it all the time. Maybe I must write *understand* instead of read, would that help get the point across better?

I know, understanding new and novel issues can be a challenge. Feel free to quit any time, and do so before you have shared any advice!!!

Say, I do need some of *your* advice:

How do you set up a fanboy forum like this and get so many like minded people together?

I could use my own for sure.
 
I just don't see why someone would bother messing about with a fresh install of windows. This isn't some Acer computer chock a' block full of bloatware. That's one of the reasons that I love surface products. The worst you'll experience is an advert for candy crush in the start menu.

Just to make sure I'm getting the point across:

1. I did not do a fresh install.

2. I imaged the existing OS image before the first boot (or rather, at the first boot - but from an external USB device, so the hard drive boot image never ran, keeping it clean).

3. I then used the PC normally. I can reset it any time to factory fresh condition I want now, thanks to my image.

Yes, its a very strange concept for you guys admittedly...is that a crime?
 
Last edited:
Well my conclusion is that's your problem. You had a pure factory state, the way Microsoft intended it for the Surface, when you opened the box. I'm guessing something in your OEM image is not just right, driver wise, for the Surface. I can see possibly doing an image if you bought some no name device that had a lot of junkware on it, but you bought a Surface from Microsoft. Don't you think maybe they know best how to prepare it?

No, your problem is you're dispensing advice before even understanding what the problem is; and then even getting offended at nothing other than your own misapprehension of the problem!!!
 
No, your problem is you're dispensing advice before even understanding what the problem is; and then even getting offended at nothing other than your own misapprehension of the problem!!!

You are right, I don't understand all these problems that are unique to you. I won't dispense any more advice to you, so best of luck.
 
Last edited:
Please can people calm down and not try and make things personal. This is a forum for civil and friendly conversation. Otherwise action will be taken.
 
I love your positive attitude!

There's been users who've returned machines umpteen times, and left wondering why they're having issues.

Hint: Its a software/firmware issue.

Read the blurry text post:
Blurry Text

Read the defrag post:
Defrag Problem

Contribute some benchmarks here:
Surface Pro 2017 Benchmarks (and Anomalies)

And trust me, if you've been through each generation of this device, each with their own unique problems - you're bound to get grumpy.

Like I wrote earlier...I'd use a Mac if I could.

These machines are endless trouble.

You are seriously butt hurt!

Sounds like Surface isn't for you. If you cannot use Mac, how about a different brand of Windows computer?
 
Status
Not open for further replies.
Back
Top