Chidge
New member
- May 25, 2023
- 3
Hi, Ive been having BSOD for a while now mainly during the day and not when gaming at night. I have reset windows, I have changed the RAM, Powersupply, Graphics Card. I have updated drivers and scanned what I could. Today it happened again so I thought id give scans another try. I ran sfc scanow and got the error that it could not complete. So I downloaded SFC FIX and it says 'CBS & SFC total detected corruption count: 3' And that some corruptions could not be fixed automatically. Not sure what to do now... Below is my whocrashed dump files
On Thu 25/05/2023 10:30:28 your computer crashed or a problem was reported
On Tue 23/05/2023 09:19:18 your computer crashed or a problem was reported
On Thu 18/05/2023 22:58:35 your computer crashed or a problem was reported
On Fri 12/05/2023 10:52:30 your computer crashed or a problem was reported
On Tue 25/04/2023 14:59:50 your computer crashed or a problem was reported
On Thu 25/05/2023 10:30:28 your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\MEMORY.DMP (Kernel memory dump) |
| Bugcheck code: | 0x1A(0x41792, 0xFFFF8A3FFD05B4B0, 0x400000000000000, 0x0) |
| Bugcheck name: | MEMORY_MANAGEMENT |
| Bug check description: | This indicates that a severe memory management error occurred. |
| Analysis: | A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption. This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues |
On Tue 23/05/2023 09:19:18 your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\052323-14250-01.dmp (Minidump) |
| Bugcheck code: | 0x1000007E(0xFFFFFFFFC0000005, 0xFFFFF804636C2876, 0xFFFFBA8361F09298, 0xFFFFBA8361F08AD0) |
| Bugcheck name: | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M |
| Driver or module in which error occurred: | Ntfs.sys (Ntfs+0x132876) |
| File path: | C:\WINDOWS\System32\Drivers\Ntfs.sys |
| Description: | NT File System Driver |
| Product: | Microsoft® Windows® Operating System |
| Company: | Microsoft Corporation |
| Bug check description: | This indicates that a system thread generated an exception which the error handler did not catch. |
| Analysis: | This is likely a software problem which means that it was probably caused by a bug in a driver. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues 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 to check your drive(s) for errors. |
On Thu 18/05/2023 22:58:35 your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\051823-20312-01.dmp (Minidump) |
| Bugcheck code: | 0x3B(0xC0000005, 0xFFFFF8021989F318, 0xFFFFC50857C3DC70, 0x0) |
| Bugcheck name: | SYSTEM_SERVICE_EXCEPTION |
| Bug check description: | This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. |
| Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver. |
On Fri 12/05/2023 10:52:30 your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\051223-16921-01.dmp (Minidump) |
| Bugcheck code: | 0x3B(0xC0000005, 0xFFFFF8035E09F318, 0xFFFFDC0486A45C20, 0x0) |
| Bugcheck name: | SYSTEM_SERVICE_EXCEPTION |
| Bug check description: | This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. |
| Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver. |
On Tue 25/04/2023 14:59:50 your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\042523-25000-01.dmp (Minidump) |
| Bugcheck code: | 0x12B(0xFFFFFFFFC00002C4, 0x8ED, 0x1D464256C40, 0xFFFF890123661000) |
| Bugcheck name: | FAULTY_HARDWARE_CORRUPTED_PAGE |
| Bug check description: | This bug check indicates that a single-bit error was found in this page. This is a hardware memory error. |
| Analysis: | This is possibly a software problem. This is likely a case of memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues |
Last edited by a moderator:
