[SOLVED] NVMe become slower after startup

[atjeng666]

Hello everyone,

I have Kingston 512GB (i dunno what type) and WD Black SN750 1TB on my laptop.
My laptop is acer nitro 5 ryzen 7, it have 2 m.2 nvme slot and 1 sata hdd

If I check on crytaldiskmark in the beginning of my startup the speed is normal.
Kingston (2800/1500) & WD (3400/3000)
but after I try it one more time speed is drop.
Kingston (1700/800) & WD (1400/1300)

Im not sure if this case is normal or any problem with the software/nvme temp
The startup temp is 55-59, and the second attempt is 62-64

 

[Ralston18]

Use Task Manager and Reliability History to observe what the system is doing. Use both tools but only one tool at a time.

Look before running crystal disk mark and then again afterwards.

My thought is that some other process is getting launched after the laptop has been on for a few minutes.

Look in Task Manager > Startup

Also Task Scheduler. Look for some trigger that launches another process.

Another tool to help is Process Explorer (Microsoft, free):

https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

Overall objective is to discover what changes between the startup and the second test.

 

[atjeng666]

nothing change on the task manager or resource monitor
But i try to add my nvme a heatsink and make it cooler. the result is my speed back to normal. it still a slight drop about 100MBps but its ok.
I'm not sure if the problem is the composite temp. but now its normal.

Thanks for your suggestion btw

Use Task Manager and Reliability History to observe what the system is doing. Use both tools but only one tool at a time.

Look before running crystal disk mark and then again afterwards.

My thought is that some other process is getting launched after the laptop has been on for a few minutes.

Look in Task Manager > Startup

Also Task Scheduler. Look for some trigger that launches another process.

Another tool to help is Process Explorer (Microsoft, free):

https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

Overall objective is to discover what changes between the startup and the second test.