New
#1
BSOD Custom Build. Can't figure out the culprit.
This was my first custom build. Everything has went well for about a month then I received my first BSOD. The PC crashed and upon reboot said Checksum error. This made me believe my MOB battery was bad so I replaced it. This did not fix the problem. I eventually restored to a system image and everything was fine for a day or two. This morning I have had 2 BSOD. Any help would be appreciated.
I have followed the posting instructions, I think.
After checking a few of the other threads, I am going to go ahead and do a few of the beginning suggestions such as SFC scan and disk check. I already have Malwarebytes Pro installed. I have also used ADW.
On Tue 3/4/2014 12:14:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-15444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80010C0380, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 3/4/2014 12:14:54 PM 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: 0x1A (0x41790, 0xFFFFFA80010C0380, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Last edited by Raveiyn; 04 Mar 2014 at 09:12.