Jump to content

Rewil

Member
  • Posts

    2
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well it automaticaly checks what was wrong, then just my PC resets and everything works fine till next time. But it's like that all the time. Which PC part can make problems like that? Well reinstalling my OS is the last thing I want to check. I will try checking my ram tho, good thing to start, but as I said, it's really hard for me to check if it's making problems, because these BSOD are appearing totally randomly... Now, I didn't make any changes because I was out of home for a while, went back, wanted to check some games again I nearly always had problems with - FH4 - played like 30 min, zero problems, new COD:WZ BR also no problems, and yesterday I had a BSOD only on my brower open. It's really hard for me to "force" BSOD. No idea how many days I need to wait and say "hey it's RAM which was broken, thanks guys" because also as I said I can work normally on my PC for a week or even more without any problems and then bum, two problems day after day. Any idea how I could check it better instead of just using my PC regurally? Sorry for my English.
  2. Hello. I've a very big problem with BSOD. I have it for like a half year, and finally I can't stand it. I tried a lot of stuff I found on the web. Noone works. Here are the info I got from the WhoCrashed app. Crashes are totally random, as you can see I can work on my PC for a week and don't get any BSOD, and then I can get it everyday or even twice a day. It happens when only my browser is open, or while I play some games, totally random stuff, PC just restarts, checks for problem and it works again till next BSOD. Can anyone help me, please? I don't know what can I do with that. On Fri 10.04.2020 00:03:54 your computer crashed or a problem was reported (Same date, two errors, weird) crash dump file: C:\Windows\Minidump\041020-6781-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380) Bugcheck code: 0xA (0xFFFF8580007A1180, 0x2, 0x0, 0xFFFFF80634AE5DA7) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 10.04.2020 00:03:54 your computer crashed or a problem was reported (Same date, two errors, weird) crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: win32kbase.sys (win32kbase!NtDCompositionCommitChannel+0xACF) Bugcheck code: 0xA (0xFFFF8580007A1180, 0x2, 0x0, 0xFFFFF80634AE5DA7) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\win32kbase.sys product: System operacyjny Microsoft® Windows® company: Microsoft Corporation description: Podstawowy sterownik jądra Win32k Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sat 04.04.2020 22:50:32 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\040420-8921-01.dmp This was probably caused by the following module: ntfs.sys (0xFFFFF80441A698ED) Bugcheck code: 0x34 (0x51359, 0xFFFFF98C1B3FC5E8, 0xFFFFF98C1B3FBE30, 0xFFFFF80441A698ED) Error: CACHE_MANAGER file path: C:\Windows\system32\drivers\ntfs.sys product: System operacyjny Microsoft® Windows® company: Microsoft Corporation description: Sterownik systemu plików NT Bug check description: This indicates that a problem occurred in the file system's cache manager. The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK. On Fri 03.04.2020 02:29:24 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\040320-8015-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380) Bugcheck code: 0xA (0x96285D60, 0x2, 0x0, 0xFFFFF8042C900F3B) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sat 28.03.2020 21:58:15 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\032820-7015-01.dmp This was probably caused by the following module: win32kbase.sys (0xFFFFC891FE0B9400) Bugcheck code: 0x3B (0xC0000005, 0xFFFFC891FE0B9400, 0xFFFFFC81BE40B1D0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32kbase.sys product: System operacyjny Microsoft® Windows® company: Microsoft Corporation description: Podstawowy sterownik jądra Win32k Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sat 28.03.2020 14:54:02 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\032820-6484-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80508DE734F, 0xFFFFA78149F168A0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. My Setup is: GTX 1070 from Gigabyte Ryzen 2600 B450-A PRO 2x8 GB of RAM from HyperX and 2x8 RAM from Goodram.
×