Overclock.net banner
1 - 3 of 3 Posts

·
Registered
Joined
·
1 Posts
Discussion Starter · #1 ·
Hi every1. I'm praying for help bc I can't really play any videogames without a lot of fps drops, I'm gonna add some LatencyMon screenshots, I'm really noob handling with this, tbh, so any help would be extremely appreciated.

SYSTEM INFORMATION
_
Computer name: LAPTOP-0QT6KU95
OS version: Windows 10, 10.0, version 2009, build: 19043 (x64)
Hardware: Predator PH315-51, Acer
BIOS: V1.19
CPU: GenuineIntel Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Logical processors: 12
Processor groups: 1
Processor group size: 12
RAM: 16226 MB total


_
CPU SPEED
_
Reported CPU speed (WMI): 2107 MHz
Reported CPU speed (registry): 2208 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 11413,10
Average measured interrupt to process latency (µs): 7,487504

Highest measured interrupt to DPC latency (µs): 11402,50
Average measured interrupt to DPC latency (µs): 2,363745


_
REPORTED ISRs
_
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 3189,807065
Driver with highest ISR routine execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,010950
Driver with highest ISR total time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,011744

ISR count (execution time <250 µs): 396227
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 5
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 4
ISR count (execution time >=4000 µs): 0


_
REPORTED DPCs
_
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 3811,675725
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total DPC routine time (%): 0,014608
Driver with highest DPC total execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation

Total time spent in DPCs (%) 0,034774

DPC count (execution time <250 µs): 1394287
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 247
DPC count (execution time 1000-2000 µs): 2
DPC count (execution time 2000-4000 µs): 3
DPC count (execution time >=4000 µs): 0


_
REPORTED HARD PAGEFAULTS
_
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: msmpeng.exe

Total number of hard pagefaults 18984
Hard pagefault count of hardest hit process: 5839
Number of processes hit: 105


_
PER CPU DATA
_
CPU 0 Interrupt cycle time (s): 51,879175
CPU 0 ISR highest execution time (µs): 3189,807065
CPU 0 ISR total execution time (s): 4,007879
CPU 0 ISR count: 387985
CPU 0 DPC highest execution time (µs): 3811,675725
CPU 0 DPC total execution time (s): 8,890456
CPU 0 DPC count: 983030
_
CPU 1 Interrupt cycle time (s): 26,406349
CPU 1 ISR highest execution time (µs): 241,884058
CPU 1 ISR total execution time (s): 0,075353
CPU 1 ISR count: 8179
CPU 1 DPC highest execution time (µs): 481,578804
CPU 1 DPC total execution time (s): 0,83110
CPU 1 DPC count: 132420
_
CPU 2 Interrupt cycle time (s): 33,675901
CPU 2 ISR highest execution time (µs): 43,954710
CPU 2 ISR total execution time (s): 0,000589
CPU 2 ISR count: 72
CPU 2 DPC highest execution time (µs): 799,293478
CPU 2 DPC total execution time (s): 0,922825
CPU 2 DPC count: 115719
_
CPU 3 Interrupt cycle time (s): 36,583290
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 213,209239
CPU 3 DPC total execution time (s): 0,042322
CPU 3 DPC count: 6003
_
CPU 4 Interrupt cycle time (s): 28,288015
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 514,348732
CPU 4 DPC total execution time (s): 0,320650
CPU 4 DPC count: 46671
_
CPU 5 Interrupt cycle time (s): 34,653420
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 305,601449
CPU 5 DPC total execution time (s): 0,194306
CPU 5 DPC count: 9308
_
CPU 6 Interrupt cycle time (s): 27,743560
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 2216,548913
CPU 6 DPC total execution time (s): 0,211044
CPU 6 DPC count: 23626
_
CPU 7 Interrupt cycle time (s): 33,355477
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 434,442029
CPU 7 DPC total execution time (s): 0,042396
CPU 7 DPC count: 5705
_
CPU 8 Interrupt cycle time (s): 19,738362
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 785,284420
CPU 8 DPC total execution time (s): 0,290146
CPU 8 DPC count: 32391
_
CPU 9 Interrupt cycle time (s): 27,093894
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 211,931159
CPU 9 DPC total execution time (s): 0,034867
CPU 9 DPC count: 4127
_
CPU 10 Interrupt cycle time (s): 24,356076
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 477,124094
CPU 10 DPC total execution time (s): 0,222615
CPU 10 DPC count: 25688
_
CPU 11 Interrupt cycle time (s): 29,953165
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 422,137681
CPU 11 DPC total execution time (s): 0,089452
CPU 11 DPC count: 9851
_


Rectangle Font Parallel Screenshot Number

Rectangle Font Parallel Pattern Screenshot


Thx in advance to all of u.
 

·
RTX ON FPS OFF
Joined
·
1,004 Posts
Did you try a fresh windows install?

Power mode settings?

Sounds to me like a software bug unless you have done some additional changes. Perhaps there are some background services that are bogging things down? I know a lot of RGB software is akin to throwing a handful of nuts and bolts into your engine in terms of messing things up during gameplay. Not quite sure what to make of this giant wall of text you posted though, perhaps someone with more information can interpret it better. I would start with a clean install and see if the problem persists, then look into potential hardware issues.
 

·
Tank destroyer and a god
Joined
·
2,834 Posts
rerun the tests, for 1 minutes and only after the OS is not doing anything. Amount of hardpage faults indicates there are running processes in the background. LatencyMon has to be used only when there is no activity on the system.

Also its a notebook - there is a lot of powersaving features in play. Numbers on forums like these usually comes from desktops.
 
1 - 3 of 3 Posts
Top