New
#1
BSOD 0x3B and 0x1E
Seems it doesn't matter what I am doing, I will get a BSOD after the computer has ran for a bit. It has crashed while playing flash games, Steam games, and just sitting and idling. I have pulled the computer apart and cleaned any dust in there just in case it was a dust insulated overheating issue. I have checked drivers, reinstalled drivers, reinstalled Windows and I am at my wits end on what to do.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled for your computer.
On Sun 12/29/2013 5:30:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122913-30404-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002AC2AA5, 0xFFFFF88007298700, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
On Sun 12/29/2013 3:41:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122913-25178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F850)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 12/28/2013 7:59:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122813-22152-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x109 (0xA3A039D89844BA20, 0xB3B7465EEAC18C16, 0xFFFFF80002A6E5A0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 12/28/2013 7:56:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122813-22370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xFC (0xFFFFF880088A9800, 0x800000019C344963, 0xFFFFF880088A9600, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.