Hello, Lately I've been having an issue where the Display will go black but the system is still on and fine, It doesn't go fully complete black like its off and It's entirely random but it seems to have more chance of happening if the brightness is up to 100. It's annoying because the only method I have to dealing with this is to either Windows Key + F7 to toggle the display off or shutting down the brightness to 0.
I have no idea why or how it's doing this but I've also noticed my latency and DPC is high despite it causing no more problems after I updated my sound driver (Used to do the whole static, buzzing or outright lag jump sometimes). I'm just wondering if the two may be connected since I'm not well versed in this as others.
It should be noted the laptop has windows 7 by default but I use a windows 10 disc I created before I restored to factory default settings to fix the issue. And this all started after I used a third party *automatic* driver updater to update drivers that went horribly wrong and no doubt made updates for drivers not customized for this specific laptop and forced me to uninstall most drivers. But as far as I can tell this issue only started emerging a few weeks ago and despite a restore to factory default settings now persists here too.
It could also be a failing Black-light but I wouldn't think under these circumstances it would have this type of behavior.
Things I've Tried:
Uninstalling the drivers (works for a couple of hours before going straight back to 0)
Update Bios
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:22:26 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: THEBEAST
OS version: Windows 10 , 10.0, build: 15063 (x64)
Hardware: G550JK, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Logical processors: 8
Processor groups: 1
RAM: 16267 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2394 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): 11106.121838
Average measured interrupt to process latency (µs): 5.919706
Highest measured interrupt to DPC latency (µs): 11103.555926
Average measured interrupt to DPC latency (µs): 2.673769
_________________________________________________________________________________________________________
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): 341.944862
Driver with highest ISR routine execution time: i8042prt.sys - i8042 Port Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0.040737
Driver with highest ISR total time: i8042prt.sys - i8042 Port Driver, Microsoft Corporation
Total time spent in ISRs (%) 0.055182
ISR count (execution time <250 µs): 570685
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 12
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
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): 7927.783208
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Highest reported total DPC routine time (%): 0.058435
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0.196451
DPC count (execution time <250 µs): 6688004
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 3690
DPC count (execution time 1000-1999 µs): 1995
DPC count (execution time 2000-3999 µs): 288
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.
Process with highest pagefault count: none
Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 53.846678
CPU 0 ISR highest execution time (µs): 341.944862
CPU 0 ISR total execution time (s): 5.796559
CPU 0 ISR count: 558495
CPU 0 DPC highest execution time (µs): 7927.783208
CPU 0 DPC total execution time (s): 15.712113
CPU 0 DPC count: 6108410
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 22.218854
CPU 1 ISR highest execution time (µs): 159.209273
CPU 1 ISR total execution time (s): 0.134370
CPU 1 ISR count: 11042
CPU 1 DPC highest execution time (µs): 4401.115288
CPU 1 DPC total execution time (s): 1.025769
CPU 1 DPC count: 69378
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 16.819745
CPU 2 ISR highest execution time (µs): 39.585213
CPU 2 ISR total execution time (s): 0.012867
CPU 2 ISR count: 1066
CPU 2 DPC highest execution time (µs): 5155.962406
CPU 2 DPC total execution time (s): 0.967299
CPU 2 DPC count: 124780
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 20.589657
CPU 3 ISR highest execution time (µs): 22.675439
CPU 3 ISR total execution time (s): 0.000593
CPU 3 ISR count: 72
CPU 3 DPC highest execution time (µs): 4748.444862
CPU 3 DPC total execution time (s): 0.433331
CPU 3 DPC count: 37339
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 16.407915
CPU 4 ISR highest execution time (µs): 7.765664
CPU 4 ISR total execution time (s): 0.000126
CPU 4 ISR count: 22
CPU 4 DPC highest execution time (µs): 3427.984962
CPU 4 DPC total execution time (s): 0.997073
CPU 4 DPC count: 127458
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 18.783719
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): 3998.578947
CPU 5 DPC total execution time (s): 0.493066
CPU 5 DPC count: 31636
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 18.319421
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): 3137.904762
CPU 6 DPC total execution time (s): 0.821969
CPU 6 DPC count: 113096
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 21.373284
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): 5152.829574
CPU 7 DPC total execution time (s): 0.712067
CPU 7 DPC count: 81925
_________________________________________________________________________________________________________
Since this issue started occurring after a period of time, and since a factory reset did not help, I would suspect a hardware issue. It's possible the connection between your display and motherboard is failing. This can be due to a wire that has a break in it that sometimes results in a short, or it can be due to the connector becoming loose between the motherboard and cable. It could also be dust interfering with the connection. See first if cleaning the system of dust has any effect:
Dxdiag shows G550JK.203, whereas your laptop webpage says there's BIOS 205 2014/11/05 (read the manual for how to update the bios).
Did you install Version V1.0.0039 of ATK (see your laptop support webpage)?
By chance, are you using a ps/2 external keyboard or mouse?
Has Sysnative Forums helped you? Please consider donating to help us support the site!
