cancel
Showing results for 
Search instead for 
Did you mean: 

Win10 short freezes. New 9900K+Asus Strix z390-E bios 0702

eth100
Level 7
UPDATE... Kombustor v4 glitches with 4xCPUs threads... on a different computer... need to look more for a reproducible fail....


===============
System always has intermittent short freezes under heavy load. Reproducible using Kombustor and running 32 threads CPU stress... happens faster if also running GPU test (Kombustor).
ROG STRIX Z390-E GAMING BIOS 0702
i9-9900K

Swapped Ram, PSU, multiple GPUs, and integrated GPU (what's running now). Latest Bios. Default bios settings. Reset windows. No errors on memory checks (pulled a ram from a working system to be safe)

Detailed system config and crashes attached. The Kombustor crashes are related to starting HWINFO, also lots of reboots with some system confusion as I was swapping components..

I see a Hardware error at 7:40pm. Looks like its lost in a paging event.
IMAGE_NAME: memory_corruption
BUCKET_ID_FUNC_OFFSET: 3aa
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList

Thinking it's down to the CPU or MB... Thoughts?
13,288 Views
21 REPLIES 21

678HCV wrote:
I have the same issue, short freeze, 2-4 sec, then back to normal, no crashing. No events in Windows logs or anything else. bios 602. i9 9900k, memory 3000 XMP, leaving everything at default doesn't fix it.


I thought my issues were USB, but seems to be entire system now.

I9 9900k g.skill 4166Mhz xi extreme supernova 1300w (new) - oc'd to 5.1Ghz - bios 602

Doesn't matter if system is loaded or not, random 2-5 sec pauses.

BossJ wrote:
I thought you issues were USB, but seems to be entire system now.

I9 9900k g.skill 4166Mhz xi extreme supernova 1300w (new) - oc'd to 5.1Ghz - bios 602

Doesn't matter if system is loaded or not, random 2-5 sec pauses.



Does this happen at optimised defaults (including no XMP @ 2133MHz)? It's difficult to diagnose these things vicariously if not replicable.

You may want to check DPC latency with a tool like latencymon.
13900KS / 8000 CAS36 / ROG APEX Z790 / ROG TUF RTX 4090

BossJ
Level 7
9900k
Maximus Xi Extreme (0602)
G.Skill 2x8 4133Mhz F4-4133C19D-16GTZR
2 1080ti's
970 EVO Pro
2 850 Evo's Raid 0
EVGA 1300 watt PSU (supernova - new)

Also this is a new problem. Ran perfect for first few weeks.

Yes at defaults also

BossJ wrote:
9900k
Maximus Xi Extreme (0602)
G.Skill 2x8 4133Mhz F4-4133C19D-16GTZR
2 1080ti's
970 EVO Pro
2 850 Evo's Raid 0
EVGA 1300 watt PSU (supernova - new)

Also this is a new problem. Ran perfect for first few weeks.

Yes at defaults also


So at defaults includes no XMP, out of the box basic set up? What slots are your sticks in? Did you try using different slots and one stick at a time?
Is virtual memory diabled?
Thanks for adding the PN for your ram kit. These things may seem trivial but go a long way. For example there are 5 different part numbers on the QVL for Gskill 4133 CL19.

Is there any way you can take a video of this and upload to youtube or similar?



“Two things are infinite: the universe and human stupidity, I'm not sure about the former” ~ Albert Einstein

JustinThyme wrote:
So at defaults includes no XMP, out of the box basic set up? What slots are your sticks in? Did you try using different slots and one stick at a time?
Is virtual memory diabled?
Thanks for adding the PN for your ram kit. These things may seem trivial but go a long way. For example there are 5 different part numbers on the QVL for Gskill 4133 CL19.

Is there any way you can take a video of this and upload to youtube or similar?



Yeah I could I guess.. It's just very random... I have no tried different RAM slots, but I have run Mem86 and prime96 and the likes and everything can run for hours, and then BAM - I'm just chillin on the PC and it freezes for 2 - 5 seconds, and BAM it's back to normal. ha!

It's the strangest thing.

Ram are in Slots A2 / B2

BossJ wrote:
Yeah I could I guess.. It's just very random... I have no tried different RAM slots, but I have run Mem86 and prime96 and the likes and everything can run for hours, and then BAM - I'm just chillin on the PC and it freezes for 2 - 5 seconds, and BAM it's back to normal. ha!

It's the strangest thing.

Ram are in Slots A2 / B2


it's same for me, i have try different settings in bios, no effect; ram in A2 B2 or A1 B1 it's same issue;
freeze 1-3 sec and then back to normal too

no event in windows

edit:

my last freeze have generate a report

Version=1
EventType=LiveKernelEvent
EventTime=131930662430712495
ReportType=4
Consent=1
ReportStatus=2049
ReportIdentifier=9f49d5f5-4ff4-4889-a9cc-7d83abb080bf
Wow64Host=34404
NsAppName=LiveKernelEvent
OriginalFilename=WerFault.exe
AppSessionGuid=00000000-0000-0000-0000-000000000000
BootId=13
IsFatal=4294967295
EtwNonCollectReason=1
Response.type=4
Sig[0].Name=Code
Sig[0].Value=117
Sig[1].Name=Paramètre*1
Sig[1].Value=ffffb50790204460
Sig[2].Name=Paramètre*2
Sig[2].Value=fffff8037befce38
Sig[3].Name=Paramètre*3
Sig[3].Value=0
Sig[4].Name=Paramètre*4
Sig[4].Value=32f4
Sig[5].Name=Version du système d’exploitation
Sig[5].Value=10_0_17763
Sig[6].Name=Service Pack
Sig[6].Value=0_0
Sig[7].Name=Produit
Sig[7].Value=256_1
DynamicSig[1].Name=Version du système
DynamicSig[1].Value=10.0.17763.2.0.0.256.48
DynamicSig[2].Name=Identificateur de paramètres régionaux
DynamicSig[2].Value=1036
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17763
OsInfo[3].Key=ubr
OsInfo[3].Value=253
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1036
OsInfo[7].Key=geoid
OsInfo[7].Value=84
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=7089
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.253.17763.0-11.0.105
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16305
OsInfo[19].Key=svolsz
OsInfo[19].Value=930
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180914
OsInfo[22].Key=bldtm
OsInfo[22].Value=1434
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs5_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17763.253.amd64fre.rs5_release.180914-1434
OsInfo[30].Key=buildflightid
OsInfo[30].Value=0C394CC9-3FF2-4C57-B6D4-BD4CCAEC308B.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:2729
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
File[0].CabName=WATCHDOG-20190127-1337.dmp
File[0].Path=WATCHDOG-20190127-1337.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190127-1337.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-89971406-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=\\?\C:\WINDOWS\TEMP\WER-89971406-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WERE81C.tmp.WERInternalMetadata.xml
File[2].Flags=851970
File[2].Type=5
File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE81C.tmp.WERInternalMetadata.xml
File[3].CabName=WERInternalRequest.xml
File[3].Path=WERE82D.tmp.xml
File[3].Flags=851970
File[3].Type=5
File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE82D.tmp.xml
File[4].CabName=memory.csv
File[4].Path=WERE82C.tmp.csv
File[4].Flags=589826
File[4].Type=5
File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE82C.tmp.csv
File[5].CabName=sysinfo.txt
File[5].Path=WERE83C.tmp.txt
File[5].Flags=589826
File[5].Type=5
File[5].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE83C.tmp.txt
File[6].CabName=Report.zip
File[6].Path=Report.zip
File[6].Flags=65536
File[6].Type=11
File[6].Original.Path=\\?\C:\WINDOWS\system32\Report.zip
Ns[0].Name=stopcode
Ns[0].Value=00000117
Ns[1].Name=p1
Ns[1].Value=FFFFB50790204460
Ns[2].Name=p2
Ns[2].Value=FFFFF8037BEFCE38
Ns[3].Name=p3
Ns[3].Value=0000000000000000
Ns[4].Name=p4
Ns[4].Value=00000000000032F4
FriendlyEventName=Erreur matérielle
ConsentKey=LiveKernelEvent
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
ReportDescription=Un problème rencontré avec le matériel a provoqué un dysfonctionnement de Windows. ( trad :A problem with the hardware caused a malfunction of Windows.)
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=528404014

if it helps

i have a solution to fix, work for me, i have found solution on reddit :

https://www.reddit.com/r/techsupport/comments/a07xdw/new_build_freezescrashes_intermittently_for_15/

Go to advanced power settings in windows, ensure hard disk sleep time is set to 0 or never. Restart pc

today 0 freeze 0 crash in 3hours of use

stargate321 wrote:
i have a solution to fix, work for me, i have found solution on reddit :

https://www.reddit.com/r/techsupport/comments/a07xdw/new_build_freezescrashes_intermittently_for_15/

Go to advanced power settings in windows, ensure hard disk sleep time is set to 0 or never. Restart pc

today 0 freeze 0 crash in 3hours of use


so I have performance selected for power plan - doesn't that usually take care of the HDDs from sleeping?

Perhaps not... but I'll check this when I get home.

EDIT: You were right. Mine was set to 20 mins... wow. can't believe I missed that. Hope this fixes it!!

BossJ
Level 7
So since I've changed this no more freezes... At least last night! Great find stargate321... This is a HUGE win!

BossJ wrote:
So since I've changed this no more freezes... At least last night! Great find stargate321... This is a HUGE win!



it's nice to hear