Jump to content

Draysh

Member
  • Posts

    51
  • Joined

  • Last visited

Everything posted by Draysh

  1. Okay, i have applied the default settings and will try to play for a while and see if it's fixed. For now, thank you so much for your help @Yua @adm0n
  2. Oh yeah, i ran that yesterday and it reported no issues These are my settings. Should i just set it to default, off and see if i crash again?
  3. Uhm i just ran the default test i think. This time it seems to have had a "hardware failure" on 3 cores, but the other 3 cores seem to be finishing the test without crashing this time. Results: [Tue Dec 12 15:59:17 2023] FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected running 960K FFT size, consult stress.txt file. FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected running 960K FFT size, consult stress.txt file. FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected running 960K FFT size, consult stress.txt file. [Tue Dec 12 16:04:30 2023] Self-test 960K passed! Self-test 960K passed! Self-test 960K passed! How would i go about running the memory test?
  4. I will try running the test again and see if it happens. For now here are all the entries and dumps i could find. Error from prime95: [Tue Dec 12 15:43:31 2023] FATAL ERROR: Rounding was 0.5, expected less than 0.4 Entry: Lognavn: System Kilde: Microsoft-Windows-Kernel-Power Dato: 12-12-2023 15:44:01 Hændelses-id: 41 Opgavekategori:(63) Niveau: Kritisk Nøgleord: (70368744177664),(2) Bruger: SYSTEM Computer: Draysh Beskrivelse: Systemet har genstartet uden først at lukke korrekt ned. Denne fejl kan skyldes, at systemet er holdt op med at svare, er gået ned, eller at strømmen forsvandt uventet. Hændelses-Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> <EventID>41</EventID> <Version>9</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2023-12-12T14:44:01.5012424Z" /> <EventRecordID>151068</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Draysh</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">80</Data> <Data Name="BugcheckParameter1">0xffffc004748288d0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0xfffff807669b26c9</Data> <Data Name="BugcheckParameter4">0x2</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> <Data Name="BugcheckInfoFromEFI">false</Data> <Data Name="CheckpointStatus">0</Data> <Data Name="CsEntryScenarioInstanceIdV2">0</Data> <Data Name="LongPowerButtonPressDetected">false</Data> <Data Name="LidReliability">false</Data> <Data Name="InputSuppressionState">0</Data> <Data Name="PowerButtonSuppressionState">0</Data> <Data Name="LidState">3</Data> </EventData> </Event> Minidump: 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffc004748288d0, memory referenced. Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE. bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the processor decided the fault was due to a corrupted PTE. bit 4 is set if the fault was due to attempted execute of a no-execute PTE. - ARM64: bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the fault was due to attempted execute of a no-execute PTE. Arg3: fffff807669b26c9, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Type Value: Read Key : Analysis.CPU.mSec Value: 2343 Key : Analysis.Elapsed.mSec Value: 6864 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 421 Key : Analysis.Init.Elapsed.mSec Value: 3891 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : Bugcheck.Code.LegacyAPI Value: 0x50 Key : Failure.Bucket Value: AV_R_(null)_nt!RtlCompressBufferXpressLzStandard Key : Failure.Hash Value: {2eaf1604-dd87-7d64-b274-d3b552f8b4b3} Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: 50 BUGCHECK_P1: ffffc004748288d0 BUGCHECK_P2: 0 BUGCHECK_P3: fffff807669b26c9 BUGCHECK_P4: 2 FILE_IN_CAB: 121223-15593-01.dmp READ_ADDRESS: fffff8076731c468: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse ffffc004748288d0 MM_INTERNAL_CODE: 2 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: MemCompression TRAP_FRAME: ffffd189ab8bf7a0 -- (.trap 0xffffd189ab8bf7a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000002da rbx=0000000000000000 rcx=0000000000000041 rdx=ffffc00425303230 rsi=0000000000000000 rdi=0000000000000000 rip=fffff807669b26c9 rsp=ffffd189ab8bf930 rbp=ffffc00425b286c5 r8=ffffc004748288d0 r9=ffffc00425312f29 r10=ffffc00425b286c5 r11=ffffc00425312f4f r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe nc nt!RtlCompressBufferXpressLzStandard+0x139: fffff807`669b26c9 413808 cmp byte ptr [r8],cl ds:ffffc004`748288d0=?? Resetting default scope STACK_TEXT: ffffd189`ab8bf578 fffff807`66a8152f : 00000000`00000050 ffffc004`748288d0 00000000`00000000 ffffd189`ab8bf7a0 : nt!KeBugCheckEx ffffd189`ab8bf580 fffff807`66853cac : ffffd189`ab8bf978 00000000`00000000 ffffd189`ab8bf739 00000000`00000000 : nt!MiSystemFault+0x23079f ffffd189`ab8bf680 fffff807`66a39529 : 00000000`0000000a fffff807`66bb13a9 ffffc004`25312f29 ffffc004`1f1b5000 : nt!MmAccessFault+0x29c ffffd189`ab8bf7a0 fffff807`669b26c9 : ffffd189`ab8bf958 00000000`00000000 00000000`00000000 00000008`00000003 : nt!KiPageFault+0x369 ffffd189`ab8bf930 fffff807`669b2581 : ffffc004`25312f29 00000000`00000000 ffffc004`25b28070 ffffc004`25311f4f : nt!RtlCompressBufferXpressLzStandard+0x139 ffffd189`ab8bf9e0 fffff807`6697532f : ffffc004`083e5570 fffff807`6687d05a ffffc004`255f9000 ffffc004`2511e930 : nt!RtlCompressBufferXpressLz+0x61 ffffd189`ab8bfa40 fffff807`66bacf8e : ffffc004`083e5500 00000000`255f9070 ffffc004`255f9028 fffff807`66bad163 : nt!RtlCompressBuffer+0x6f ffffd189`ab8bfaa0 fffff807`66aee69b : ffffc004`083e5500 ffffc004`083e5010 ffffc004`083e5500 ffffc004`1bdbd1c0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxProcessEntry+0x92 ffffd189`ab8bfb30 fffff807`669089b7 : ffffffff`fd050f80 ffffc004`20243080 fffff807`669e6ee0 ffffc004`25303000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxWorkerThread+0x1077bb ffffd189`ab8bfbb0 fffff807`66a2d854 : ffff9800`76e51180 ffffc004`20243080 fffff807`66908960 00000000`00000246 : nt!PspSystemThreadStartup+0x57 ffffd189`ab8bfc00 00000000`00000000 : ffffd189`ab8c0000 ffffd189`ab8b9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!RtlCompressBufferXpressLzStandard+139 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.1020 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 139 FAILURE_BUCKET_ID: AV_R_(null)_nt!RtlCompressBufferXpressLzStandard OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {2eaf1604-dd87-7d64-b274-d3b552f8b4b3} Followup: MachineOwner ---------
  5. My psu is 100% evga I'm not entirely sure on the model other than it is 750w and modular. I believe it could be the EVGA SuperNOVA 750 GQ, as the box seems familiar.
  6. I ran the Prime95 test, and it seems my pc blue screened at the excact time the test finished so i think you're on to something Do i have anything from this test i could send to help you finding the problem?
  7. Hardware: Rtx 3070 Ryzen 5600x 16 gb ram, 3600 Mhz There are no other "critical" logs in the event viewer, and i'm not really sure how to see them in cronologial order so to say. It has happened twice now from playing warframe for about 20 minutes. It does not happen when not playing a game. Is there a way i could isolate CPU and GPU to test which might be the culprit?
  8. Update: Seems to be related to a module named amdppm. Not really sure what this means, but does not seem to be a psu issue? SYMBOL_NAME: amdppm!C1Idle+11 MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys IMAGE_VERSION: 10.0.23424.1000 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 11 FAILURE_BUCKET_ID: AV_X_(null)_BAD_IP_amdppm!C1Idle OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {df263a6a-9f2c-df2d-c5c7-6325390ff21b} Followup: MachineOwner ---------
  9. My pc has started shutting off seemingly under load. I have no idea how to translate this wall of text into what the problem actually is. My current guess is the psu, but if one you knows what the issue is, please let me know. Thanks in advance! Lognavn: System Kilde: Microsoft-Windows-Kernel-Power Dato: 12-12-2023 15:02:32 Hændelses-id: 41 Opgavekategori:(63) Niveau: Kritisk Nøgleord: (70368744177664),(2) Bruger: SYSTEM Computer: Draysh Beskrivelse: Systemet har genstartet uden først at lukke korrekt ned. Denne fejl kan skyldes, at systemet er holdt op med at svare, er gået ned, eller at strømmen forsvandt uventet. Hændelses-Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> <EventID>41</EventID> <Version>9</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2023-12-12T14:02:32.6649960Z" /> <EventRecordID>150934</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Draysh</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">80</Data> <Data Name="BugcheckParameter1">0xfffff906ad24c372</Data> <Data Name="BugcheckParameter2">0x10</Data> <Data Name="BugcheckParameter3">0xfffff906ad24c372</Data> <Data Name="BugcheckParameter4">0x2</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> <Data Name="BugcheckInfoFromEFI">false</Data> <Data Name="CheckpointStatus">0</Data> <Data Name="CsEntryScenarioInstanceIdV2">0</Data> <Data Name="LongPowerButtonPressDetected">false</Data> <Data Name="LidReliability">false</Data> <Data Name="InputSuppressionState">0</Data> <Data Name="PowerButtonSuppressionState">0</Data> <Data Name="LidState">3</Data> </EventData> </Event>
  10. Hi. When i rearrange my desktop icons to a square in the bottom left corner, they split into two groups and it's almost like the screen is in two halves too. Half of the icons go to the far left of the screen in a line, whereas the other half of the icons go to the left side of the right half of the screen in a cluster. What causes this and how can i fix it? Thanks in advance!
  11. Yeah i tried that but it didn't help. However someone said they had to do it like 5 times. I just hope they'll fix the drivers instead of having everyone reinstall their drivers.
  12. Even with DLSS you get more frames than my 3070. I assume there must be a driver issue or something.
  13. Thanks for your help. I'm not really sure where i get in contact with a professional though. Thanks either way!
  14. Like 2% each. Again, the whole cpu is only at 65%, but i don't know if cyberpunk can actually utilize all the threads.
  15. It's only really discord and steam that takes up some of the cpu.
  16. My psu is 750 watts so i doubt that that is the problem. Also im running a stock cooler on my processor, so i won't be able to get much overclocking out of it i think. Would it most likely be a cpu bottleneck even though it's only running at 65%?
  17. Hey. I recently upgraded from a 1070 ti to a 3070 so i can play cyberpunk. Cpu: 2600x Ram: 16gb 2666mhz For some reason the cpu sits at 65% and gpu at 20% (even weirder is that cyberpunk is at 0% and nvidia container is at 19%) Could this be a ram speed issue or what is going on? Thanks in advance
  18. Ahh okay. I've done that and it's the excact same result.
  19. Just tried that and i believe the issue persists, however i'm unable to check my fps without the nvidia overlay.
  20. That would be nvidia container using 13.3 and my desktop using 11.3 i guess.
  21. Yeah it should support 4400 mhz according to their website.
  22. Yeah that's what i thought as well. I guess the only way to find out is to upgrade my ram and see what happens.
  23. Hi. I just recieved my rtx 3070 and replaced my 1070ti. My current specs are: ryzen 5 2600x 16 gb 2666mhz ram rtx 3070 Intel 660p nvme ssd For some reason WoW only runs at 50 fps and does not seem to utilize my pc even if there is perfomance left to use. Am i being bottlenecked or what is going on? I included an image of my joblist so you can see the percantages of each parts usage. Thanks in advance :)
  24. I currently have a 2600x. I'm worried that it will bottleneck the 3080 at 1080p and i'm wondering if i should either go for a 1440p, a new processor or if it will work just fine. Does anyone know how bad the bottleneck will be with a 2600x? (I know no one knows for sure, but maybe an estimate?) Thanks in advance!
  25. After closing all razer processes it seems to have fixed it. Altough i do not know what causes the issue in razer synapse.
×