New
#1
BSOD, (ntoskrnl.exe, ntkrnlmp.exe)
hi, i have been getting a couple of BSOD's when ive been gaming, my monitor would go pink or freeze and ill hear a loud buzzing sound, then i switched to my integrated graphics and its been working fine. but lately, when im watching some series on my dell monitor that i have hooked up to my laptop, ive been getting BSOD's , and i used " WhoCrashed, home edition" to analyze them, my previous crashed were from nvidia kernel driver crashing and recovering.
On Tue 4/15/2014 4:51:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041414-41901-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC40070AB8, 0xFFFFFFFFC000000E, 0x140E2DBE0, 0xFFFFF8800E157000)
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 Tue 4/15/2014 4:51:18 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7A (0xFFFFF6FC40070AB8, 0xFFFFFFFFC000000E, 0x140E2DBE0, 0xFFFFF8800E157000)
Error: KERNEL_DATA_INPAGE_ERROR
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 Sat 3/22/2014 4:46:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032214-29874-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
Thanks for any help