BSOD Everywhere! I tried solving it on my own, i guarantee

[Schnauzer]

Hello,

I'm having this problem with my computer: after some time playing (sometimes watching a video) i get a BSOD. I've googled a little and updated all my drivers, but the problems continues.

I've used WhoCrashed to get this report:

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8H67-V
CPU: GenuineIntel Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4275499008 total
VM: 2147352576, free: 1908056064

And here are the last 10 crashes reports:

Spoiler

On Sun 29/06/2014 19:06:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062914-17331-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF4DC4)
Bugcheck code: 0x7A (0xFFFFF6FC4000A940, 0xFFFFFFFFC000000E, 0x1E770860, 0xFFFFF88001528DC4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 29/06/2014 19:06:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF4DC4)
Bugcheck code: 0x7A (0xFFFFF6FC4000A940, 0xFFFFFFFFC000000E, 0x1E770860, 0xFFFFF88001528DC4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 29/06/2014 06:06:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062914-18564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC40018D78, 0xFFFFFFFFC000000E, 0x938EBBE0, 0xFFFFF880031AF000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 29/06/2014 05:43:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062914-17752-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF0780)
Bugcheck code: 0x7A (0xFFFFF6FC400097D8, 0xFFFFFFFFC000000E, 0x74C8F860, 0xFFFFF880012FB780)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 29/06/2014 03:53:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062914-17160-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Sun 29/06/2014 02:53:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062814-17830-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF0780)
Bugcheck code: 0x7A (0xFFFFF6FC4000A878, 0xFFFFFFFFC000000E, 0x1981F860, 0xFFFFF8800150F780)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 29/06/2014 00:42:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062814-17721-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF0780)
Bugcheck code: 0x7A (0xFFFFF6FC400098B0, 0xFFFFFFFFC000000E, 0x65371860, 0xFFFFF88001316780)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sat 28/06/2014 20:32:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062814-17144-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC4005B458, 0xFFFFFFFFC000000E, 0xC8729BE0, 0xFFFFF8800B68B000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 22/06/2014 21:51:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062214-17986-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x1C4AC)
Bugcheck code: 0x7A (0xFFFFF6FC40008F70, 0xFFFFFFFFC000000E, 0xB59D7860, 0xFFFFF880011EE4AC)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 22/06/2014 09:19:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062214-18236-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80056FAB30, 0xFFFFFA80056FAE10, 0xFFFFF80003596270)
Error: CRITICAL_OBJECT_TERMINATION
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 a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I've also used the System File Checker tool to see if there was any corrupted file on windows, but it was all right. And I tried to see if it was the temperature, I think it was all right too. And my windows in on a SSD.

At last, I was a little lost on the forum, not sure if i asked right. Sorry for my bad english too. Someone knows how to help me? Thanks

 

[helloguy]

You could have a virus or a malware that is effecting your PC. My suggestion would be to get CCleaner and clean your HDD. Also run a full scan of Microsoft Security Essentials just to check if you have any viruses, hope I helped 🙂

 

[johnbl]

basically, the system was unable to load a driver into memory.
it is the same error you would get if you removed your drive from the system while it is running.

- i would unplug the cables from the mother board to the hard drive and plug them in again.
- if that does not help, I would put them on another port on the motherboard.
- if my BIOS supports it, you can enable hotswap for the port the drive is on. (if there is a problem and the port disconnects, it can auto reconnect the drive)

- if you have a solid state drive, there are firmware bugs that can cause this problem. particularly if you have a old OS like windows 7.
(you can boot into BIOS and leave the drive with power for several hours to let the drive fix certain error conditions)

- it can be a bad connection in a circuit