Jump to content

This is a little weird

Go to solution Solved by GreezyJeezy,
42 minutes ago, Windows10Home said:

But when I stopped stressing, it went up again

The background task came back on because the CPU usage was low again.

Hey there!

 

I used CpuZ on my laptop which has a Core i3-3110M. It is a **** cpu, but I tried it out.

 

This is a little weird tho, since when I didn't stress the CPU, the disk was at around 70-80%. But when I did stress it, the disk went to 0%. I thought this was weird, because I thought they were like, better when they did it together.

 

I don't really know, but thanks in advance ;)

Windstriker 1.0

Spoiler

CPU: Intel Core i5 6600K

CPU Cooler: NZXT Kraken X61

Motherboard: ASUS Z170-A

Memory: Crucial BallistiX Sport LT DDR4 2400MHz 16gb (2x8GB)

GPU 1: XFX HD 7970 3GB Double Dissipation

GPU 2: Gigabyte HD 7970 3GB Windforce

SSD: HyperX Fury 120GB

HDD: Seagate Barracuda 1TB 7200RPM

Case: Fractal Design Define S

PSU: EVGA SuperNOVA 850 G2

 

 

Old Laptop

Spoiler

CPU: Intel Core i3 3110M

IGPU: Intel HD Graphics 4000

Memory: No-Name DDR3 4GB (1x4GB)

HDD: 443GB

 

Link to comment
Share on other sites

Link to post
Share on other sites

3 minutes ago, dave01978 said:

Was likely a background task that stopped when cpu usage increased

But when I stopped stressing, it went up again

Windstriker 1.0

Spoiler

CPU: Intel Core i5 6600K

CPU Cooler: NZXT Kraken X61

Motherboard: ASUS Z170-A

Memory: Crucial BallistiX Sport LT DDR4 2400MHz 16gb (2x8GB)

GPU 1: XFX HD 7970 3GB Double Dissipation

GPU 2: Gigabyte HD 7970 3GB Windforce

SSD: HyperX Fury 120GB

HDD: Seagate Barracuda 1TB 7200RPM

Case: Fractal Design Define S

PSU: EVGA SuperNOVA 850 G2

 

 

Old Laptop

Spoiler

CPU: Intel Core i3 3110M

IGPU: Intel HD Graphics 4000

Memory: No-Name DDR3 4GB (1x4GB)

HDD: 443GB

 

Link to comment
Share on other sites

Link to post
Share on other sites

42 minutes ago, Windows10Home said:

But when I stopped stressing, it went up again

The background task came back on because the CPU usage was low again.

 

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×