Memtests show the RAM is fine. Here is the readout from whocrashed:
On Fri 21.6.2013. 20:38:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800335C728, 0xFFFFF8800335BF80, 0xFFFFF880013395E9)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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.
On Fri 21.6.2013. 19:42:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-16848-01.dmp
This was probably caused by the following module: tdx.sys (tdx+0x15E9C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF880010D3E9C, 0xFFFFF88003377F98, 0xFFFFF880033777F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tdx.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TDI Translation Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 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.
On Fri 21.6.2013. 12:34:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-14445-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002C2FE9F)
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 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.
I almost sure it's a driver issue. I don't know what to do though. I'm not that savvy with these things.
New computer. Here are the specs.
fx 8350
sabertooth 990fx
16gb ram, 1866mhz patriot viper
2x64gb ssd sx900 adata (raid 0)
WD hdd 3tb
msi 770gtx 2 gb
PSU Silencer Mk II Series? 950W
Using avast antivirus.
I did 4 tests with furmark. 2 passed and crashed once.
On Fri 21.6.2013. 20:38:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800335C728, 0xFFFFF8800335BF80, 0xFFFFF880013395E9)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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.
On Fri 21.6.2013. 19:42:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-16848-01.dmp
This was probably caused by the following module: tdx.sys (tdx+0x15E9C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF880010D3E9C, 0xFFFFF88003377F98, 0xFFFFF880033777F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tdx.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TDI Translation Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 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.
On Fri 21.6.2013. 12:34:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-14445-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002C2FE9F)
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 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.
I almost sure it's a driver issue. I don't know what to do though. I'm not that savvy with these things.
New computer. Here are the specs.
fx 8350
sabertooth 990fx
16gb ram, 1866mhz patriot viper
2x64gb ssd sx900 adata (raid 0)
WD hdd 3tb
msi 770gtx 2 gb
PSU Silencer Mk II Series? 950W
Using avast antivirus.
I did 4 tests with furmark. 2 passed and crashed once.
Facebook
Twitter
Instagram