Jump to content

KarolisLTS

Member
  • Posts

    10
  • Joined

  • Last visited

Everything posted by KarolisLTS

  1. A little update. I've found out, that HDD isn't the reason for BSOD by disconnecting it for a whole day, but BSOD still occurred. Then I've tried driver verifier and when it crashed, it showed, that amdxata.sys driver is crashing my pc. As far as I know it's AMD's driver and since, I've changed my gpu from AMD RX480 to Nvidia GTX1080 about a year ago, for some reason problem occurred just now. Can I somehow disable or remove that driver since I don't really need AMD drivers, to "fix" the BSOD problem?
  2. But overall, should I change my 4.5 years HDD?
  3. I had the same thought about removing one of the RAM sticks (although they are about one month old), but BSOD happens very unexpectedly, sometimes two days in a row and no BSOD, and sometimes (like yesterday) there were 4 BSODs, so it would be hard to tell if there is or there isn't a problem with RAM. Tbh I can't really leave that idea, that my HDD is causing all this, because of all pc components, viruses and even drivers, it's the only thing, that was misbehaving in the last few months. But on the other hand, I could be totally wrong about that.
  4. I've tried these kind of solutions, but from the experience, nothing seemed to help. And I don't really think it could, because almost every time BSOD strikes, I get different error message.
  5. First one: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192) A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above. Arguments: Arg1: ffff8d8ecd66d080, The address of the thread. Arg2: ffff8d8ec7489d10, The lock address. Arg3: 0000000000000001, The IRQL at which the lock was acquired. Arg4: 0000000000000000, Reserved. Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4686 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 15604 Key : Analysis.Init.CPU.mSec Value: 343 Key : Analysis.Init.Elapsed.mSec Value: 3199 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 192 BUGCHECK_P1: ffff8d8ecd66d080 BUGCHECK_P2: ffff8d8ec7489d10 BUGCHECK_P3: 1 BUGCHECK_P4: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffffd06`b535c9f8 fffff806`62a6058f : 00000000`00000192 ffff8d8e`cd66d080 ffff8d8e`c7489d10 00000000`00000001 : nt!KeBugCheckEx fffffd06`b535ca00 fffff806`5ea65dbc : ffff8d8e`da3aca20 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAcquireCacheAwarePushLockSharedEx+0x14f fffffd06`b535ca40 fffff806`5ea62801 : 00000000`000000fc 00000000`000000fc fffffd06`b535cc00 fffffd06`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x9c fffffd06`b535cb60 fffff806`62a82147 : fffffd06`b535e000 fffff806`64e12e1e fffffd06`b5358000 00000000`00000000 : FLTMGR!FltpPreFsFilterOperation+0x181 fffffd06`b535cc10 fffff806`62b5431b : fffff806`5ea68a20 00000000`00000000 00000000`00000000 fffff806`5ea62680 : nt!FsFilterPerformCallbacks+0xe7 fffffd06`b535cc80 fffff806`62b53ef7 : ffff8d8e`dc42cba0 fffff806`631b1019 00000000`00000000 00000000`00000001 : nt!FsRtlReleaseFileForModWrite+0xef fffffd06`b535cf60 fffff806`62b20b5b : ffff8d8e`d1864ac0 00000000`00000000 ffff9e08`00000000 fffff806`00001000 : nt!MiWriteComplete+0x527 fffffd06`b535d010 fffff806`62a67ce0 : ffff8d8e`cd66d080 ffff8d8e`dc42cc18 ffff8d8e`cd66d6d0 fffff806`62a60c8b : nt!IopCompletePageWrite+0x4b fffffd06`b535d040 fffff806`62bfa110 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`6aa86256 : nt!KiDeliverApc+0x1b0 fffffd06`b535d0f0 fffff806`62a60fc5 : ffff8d8e`cd66d6d0 fffff806`62a60c8b ffff8d8e`cd66d080 ffff9e08`097181b8 : nt!KiApcInterrupt+0x2f0 fffffd06`b535d280 fffff806`62a6007d : ffff8d8e`cd6770a0 00000000`00000000 ffff8d8e`00000000 fffff806`6a9b3d4e : nt!ExReleasePushLockEx+0xe5 fffffd06`b535d2e0 fffff806`5ea63e14 : 00000000`00000000 00000000`00000000 ffff8d8e`d1d651a0 fffff806`5ea63b4c : nt!FsRtlLookupPerStreamContextInternal+0x8d fffffd06`b535d310 fffff806`5ea63c47 : ffff8d8e`cd6928a0 00000000`00000000 fffffd06`b535d4a9 fffffd06`b535d460 : FLTMGR!FltpGetStreamListCtrl+0x64 fffffd06`b535d360 fffff806`64ba2fe8 : 00000000`00000000 ffff8d8e`c7489d10 ffff8d8e`d067d480 ffff8d8e`d25b3ba8 : FLTMGR!FltGetStreamContext+0x27 fffffd06`b535d3b0 fffff806`5ea6608b : 00000000`00000000 00000000`00000000 ffff8d8e`00000000 00000000`00000000 : Wof+0x2fe8 fffffd06`b535d3f0 fffff806`5ea65b37 : fffffd06`b535d600 00000000`00000004 ffff8d8e`d66f8000 00000000`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x36b fffffd06`b535d510 fffff806`5ea64b46 : fffffd06`b535e000 fffffd06`b5358000 00000000`00000000 fffffd06`b535d630 : FLTMGR!FltpPassThroughInternal+0xc7 fffffd06`b535d560 fffff806`5ea648bb : 00000000`00000000 00000000`00000000 00000000`0000000c fffff806`00000000 : FLTMGR!FltpPassThrough+0x1d6 fffffd06`b535d600 fffff806`62a52f55 : ffff8d8e`d82932a0 fffff806`62a52f97 00000000`0000000c 00000000`00000000 : FLTMGR!FltpDispatch+0x8b fffffd06`b535d660 fffff806`62aecc6e : ffff8d8e`d66f8140 ffff8d8e`d82932a0 ffff8d8e`d1d651a0 ffff8d8e`d66f8080 : nt!IofCallDriver+0x55 fffffd06`b535d6a0 fffff806`62b517b1 : 00000000`00025000 ffff8d8e`d1bed570 ffff8d8e`d1d651a0 00000000`00000000 : nt!IoAsynchronousPageWrite+0x136 fffffd06`b535d6f0 fffff806`62bb2abb : fffff806`63450d40 00000000`00000001 ffff8d8e`d66f8070 00000000`00000000 : nt!MiGatherMappedPages+0x495 fffffd06`b535d7b0 fffff806`62b17e85 : ffff8d8e`cd66d080 ffff8d8e`cd66d080 00000000`00000080 000f8067`bcbbbdff : nt!MiMappedPageWriter+0x18b fffffd06`b535dc10 fffff806`62bfd408 : fffff806`5da0b180 ffff8d8e`cd66d080 fffff806`62b17e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55 fffffd06`b535dc60 00000000`00000000 : fffffd06`b535e000 fffffd06`b5358000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: Wof+2fe8 MODULE_NAME: Wof IMAGE_NAME: Wof.sys IMAGE_VERSION: 10.0.19041.870 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 2fe8 FAILURE_BUCKET_ID: 0x192_Wof!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f0bcf48a-9333-fe58-4461-0786b2f11699} Followup: MachineOwner Second one: SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8066f7051b5, Address of the instruction which caused the bugcheck Arg3: fffffd88444c2ad0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3483 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 21120 Key : Analysis.Init.CPU.mSec Value: 327 Key : Analysis.Init.Elapsed.mSec Value: 3549 Key : Analysis.Memory.CommitPeak.Mb Value: 80 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff8066f7051b5 BUGCHECK_P3: fffffd88444c2ad0 BUGCHECK_P4: 0 CONTEXT: fffffd88444c2ad0 -- (.cxr 0xfffffd88444c2ad0) rax=0000000000000208 rbx=ffffe482681e42a0 rcx=0000000000000010 rdx=0000000000000288 rsi=0000000000000010 rdi=0000000000000000 rip=fffff8066f7051b5 rsp=fffffd88444c34d0 rbp=fffffd88444c3629 r8=0000000000000002 r9=0000000000000001 r10=ffffe4826d1bc940 r11=ffffe482681e4388 r12=ffffffffc00000b3 r13=0000000000000000 r14=ffffe48250f06010 r15=ffffe482000001c1 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202 FLTMGR!FltpPassThroughCompletionWorker+0x295: fffff806`6f7051b5 4a8b343e mov rsi,qword ptr [rsi+r15] ds:002b:ffffe482`000001d1=???????????????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: vrserver.exe STACK_TEXT: fffffd88`444c34d0 fffff806`6f7043bc : fffffd88`444be000 fffffd88`444c4000 ffffffff`c00000b3 00000000`00000000 : FLTMGR!FltpPassThroughCompletionWorker+0x295 fffffd88`444c3570 fffff806`70e4885e : ffffe482`00000000 ffffe482`55c4c360 00000000`00000060 fffff806`70e60913 : FLTMGR!FltpPassThroughCompletion+0xc fffffd88`444c35a0 fffff806`70e48727 : 00000000`00000000 00000000`00000002 ffffe482`6d1bc940 ffffe482`6d1bc940 : nt!IopfCompleteRequest+0x11e fffffd88`444c3690 fffff806`7713c871 : ffffe482`55c4a060 00000000`00000000 00000000`00000000 ffffe482`6d1bca58 : nt!IofCompleteRequest+0x17 fffffd88`444c36c0 fffff806`70e52f55 : ffffe482`681e42a0 fffff806`6f704b46 fffffd88`444c4000 fffffd88`444be000 : Npfs!NpFsdFileSystemControl+0x51 fffffd88`444c36f0 fffff806`6f706ccf : ffff8801`bc4ce000 ffffe482`4e87e040 00000000`00000000 00000000`0000018c : nt!IofCallDriver+0x55 fffffd88`444c3730 fffff806`6f73caf4 : fffffd88`444c37c0 00000000`00000000 00000000`00000000 fffff806`7122b471 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f fffffd88`444c37a0 fffff806`70e52f55 : 00000000`00000000 ffffe482`6d1bc940 00000000`00000002 00000000`00000001 : FLTMGR!FltpFsControl+0x104 fffffd88`444c3800 fffff806`711fd928 : fffffd88`444c3b80 ffffe482`6d1bc940 00000000`00000001 00000000`00000000 : nt!IofCallDriver+0x55 fffffd88`444c3840 fffff806`711fd1f5 : 00000000`00000000 fffffd88`444c3b80 00000000`00000000 fffffd88`444c3b80 : nt!IopSynchronousServiceTail+0x1a8 fffffd88`444c38e0 fffff806`712c2716 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5e5 fffffd88`444c3a20 fffff806`710077b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtFsControlFile+0x56 fffffd88`444c3a90 00007fff`4d8ad334 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 00000087`101ff708 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`4d8ad334 SYMBOL_NAME: Npfs!NpFsdFileSystemControl+51 MODULE_NAME: Npfs IMAGE_NAME: Npfs.SYS IMAGE_VERSION: 10.0.19041.1030 STACK_COMMAND: .cxr 0xfffffd88444c2ad0 ; kb BUCKET_ID_FUNC_OFFSET: 51 FAILURE_BUCKET_ID: 0x3B_c0000005_Npfs!NpFsdFileSystemControl OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {344eb83d-02f4-e9e3-668e-2eb20e38005a} Followup: MachineOwner Third one: KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: fffffb08c2022870, Address of the trap frame for the exception that caused the bugcheck Arg3: fffffb08c20227c8, Address of the exception record for the exception that caused the bugcheck Arg4: 0000000000000000, Reserved Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2936 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 7041 Key : Analysis.Init.CPU.mSec Value: 312 Key : Analysis.Init.Elapsed.mSec Value: 1745 Key : Analysis.Memory.CommitPeak.Mb Value: 85 Key : FailFast.Name Value: CORRUPT_LIST_ENTRY Key : FailFast.Type Value: 3 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 139 BUGCHECK_P1: 3 BUGCHECK_P2: fffffb08c2022870 BUGCHECK_P3: fffffb08c20227c8 BUGCHECK_P4: 0 TRAP_FRAME: fffffb08c2022870 -- (.trap 0xfffffb08c2022870) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffa085a5a2a948 rbx=0000000000000000 rcx=0000000000000003 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8043f834e11 rsp=fffffb08c2022a00 rbp=fffffb08c2022a91 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffff780000003b0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe nc nt!KeWaitForSingleObject+0x1d0a21: fffff804`3f834e11 cd29 int 29h Resetting default scope EXCEPTION_RECORD: fffffb08c20227c8 -- (.exr 0xfffffb08c20227c8) ExceptionAddress: fffff8043f834e11 (nt!KeWaitForSingleObject+0x00000000001d0a21) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000003 EXCEPTION_STR: 0xc0000409 BAD_STACK_POINTER: fffffb08c2022548 STACK_TEXT: fffffb08`c2022548 fffff804`3f807d69 : 00000000`00000139 00000000`00000003 fffffb08`c2022870 fffffb08`c20227c8 : nt!KeBugCheckEx fffffb08`c2022550 fffff804`3f808190 : 00000001`ffffffff fffffff6`0000000d 00000000`00000010 00000000`00040246 : nt!KiBugCheckDispatch+0x69 fffffb08`c2022690 fffff804`3f806523 : 00000000`00000000 fffff804`3f91a4b4 00000000`0000000b fffffb08`c20228b8 : nt!KiFastFailDispatch+0xd0 fffffb08`c2022870 fffff804`3f834e11 : ffffffff`ffffffff 00000000`00000004 00000017`946113b4 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x323 fffffb08`c2022a00 fffff804`45652471 : ffffa085`a5a2a940 00000000`00000000 00000000`00000000 ffffa085`b23a1801 : nt!KeWaitForSingleObject+0x1d0a21 fffffb08`c2022af0 fffff804`45652f29 : 00000000`00000010 00000000`00000018 00000000`00000005 fffff804`45657150 : mmcss!CiSchedulerWait+0x2d1 fffffb08`c2022bc0 fffff804`3f717e85 : ffffa085`00000010 ffffa085`a5d10040 00000000`00000080 fffff804`45652d50 : mmcss!CiSchedulerThreadFunction+0x1d9 fffffb08`c2022c10 fffff804`3f7fd408 : ffffbc00`a73c0180 ffffa085`a5d10040 fffff804`3f717e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55 fffffb08`c2022c60 00000000`00000000 : fffffb08`c2023000 fffffb08`c201d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: mmcss!CiSchedulerWait+2d1 MODULE_NAME: mmcss IMAGE_NAME: mmcss.sys IMAGE_VERSION: 10.0.19041.867 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 2d1 FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_STACKPTR_ERROR_mmcss!CiSchedulerWait OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {afd216e0-0f0e-8321-4cb8-a5bfe32f1edc} Followup: MachineOwner
  6. Hello, about two months ago, I started getting various BSOD and almost every time they were different. And they occur almost every day, sometimes even 2-3 times a day (like today). I've tried many fixes and various solutions like memtest86, chkdsk, sfc /scannow, including reinstalling windows, but nothing seems to help. Almost at the same time (around the start of February) I've updated windows and my first BSOD happened. It could've have been a big coincidence as far as I know, because nobody experienced such viscous BSOD streak like I have. Around the time of January and February my (now 4.5 years) HDD Seagate barracuda 3tb (secondary drive) started to make a real nasty noise (like brushing rusty nail through metal) and it lasted about a week and suddenly stopped. I've used CrystalDiskInfo to check SMART and it showed current reallocated sector count 100 and worst 100 too. Buying new one isn't a big deal, but I would like to know if these problems with BSOD and HDD are connected. So my main question is, what could cause these BSOD and is it "necessary" to change HDD into a new one? Attaching dump files040321-31093-01.dmp CPU: Ryzen 5 3600 Motherboard: Asus B450m-a Ram: Corsair Vengeance LPX DDR4 16GB (2x8) 3200MHz CL16 SSD/HDD: Main - Kingston V300 SSD, Seagate Barracuda 3tb HDD, Adata XPG SX8200 PRO M.2 GPU: GTX 1080 PSU: EVGA BQ 650W, 80 PLUS Bronze OS: Windows 10 - 10.0.19042 Build 19042 Bios: American Megatrends Inc. 2202 040321-33328-01.dmp 040321-28937-01.dmp
  7. Btw, I'm using 8gb(2x4) of ram, should I upgrade those to 16gb in the near future (for example with CPU) or it's enough for now?
  8. In the following year, if I'll choose to upgrade, would 6700 or 7700 be good options, or you do have something else in mind?
  9. Mainly playing AAA singleplayers like The Witcher 3, Borderlands 3, RDR2, etc.
  10. Hello, I'm currently using i5 6600(non k) with RX 480 and after 2 years I'm thinking about upgrading my gpu. Had a lot to choose from and I'm thinking about the GTX 1080. Other choice was GTX 1070, but here in my country the price difference between these used GPU's is pretty small, only about 45USD. One of the most troubling thing about upgrading was the CPU bottleneck. I've read a lot of forums about this and similar duos and opinions are very different. Some say it doesn't bottleneck at all, some, that it's even worse after upgrading to higher end GPU like 1080, doesn't matter if the game they are playing is more GPU or CPU demanding. And btw, I don't really have money to upgrade GPU and CPU at the same time. So my questions are, what's your opinion about this duo and is it worth upgrading into this GPU? I would like to play in stable 1080p 60hz, but if it would work I'd like to push the resolution up to 1440p.
×