- Dec 6, 2017
- 10
- 0
- 510
I have recently built a new PC with a fresh installation of windows but receive seemingly random and untriggered BSODs. I have run all tests (DISM, chkdsk, sfc, etc.) and returned no errors. I also ran the built-in memory check in windows. After that had completed, I received a message saying that there is an issue. I also ran the memtest86 for good measure, and it returned 3 errors on test 8 alone, after running for ~3 hours. I know it passed the first test with no errors, and then on the second loop, errors were found.
After researching, I think it may be defective RAM. What else can I do to make sure this is the case before I may waste time and money replacing them? I noticed that when gaming, the crash hasn't happened yet, only when the PC is idle or not doing much (Google Chrome etc.)
I used 'WhoCrashed' to decipher the Minidumps and this is the return of the most common Blue Screen:
On Mon 11/12/2017 11:21:48 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121117-7812-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80E46F45494)
Bugcheck code: 0x109 (0xA39FEED89E08B8B8, 0xB3B6FB5EF089B973, 0xFFFFF80E46F45494, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard 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.
After researching, I think it may be defective RAM. What else can I do to make sure this is the case before I may waste time and money replacing them? I noticed that when gaming, the crash hasn't happened yet, only when the PC is idle or not doing much (Google Chrome etc.)
I used 'WhoCrashed' to decipher the Minidumps and this is the return of the most common Blue Screen:
On Mon 11/12/2017 11:21:48 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121117-7812-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80E46F45494)
Bugcheck code: 0x109 (0xA39FEED89E08B8B8, 0xB3B6FB5EF089B973, 0xFFFFF80E46F45494, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard 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.
Facebook
Twitter
Instagram