Frequent BSOD errors

stutheironman

Reputable
Nov 8, 2015
8
0
4,510
Last night, my in-laws computer started acting up. Since then there have been 4 Blue Screen reboots but all of them are with different error codes.

0x0000003b - SYSTEM_SERVICE_EXCEPTION
0x0000001e - KMODE_EXCEPTION_NOT_HANDLED
0x000000fc - ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
0x0000000a - IRQL_NOT_LESS_OR_EQUAL

All of this stuff is pretty out of my grasp and no idea what is causing the actual problem and wondering if anyone might have an idea on how to fix this. I did try and do a PC reset but unfortunately that's not working either
 
Solution
Did you try to update all your drivers
If no then update all of them and replay whether your problem is solved
If yes then it is better to do a clean install and then install the latest drivers

stutheironman

Reputable
Nov 8, 2015
8
0
4,510



On Sat 12/3/2016 5:23:57 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\120316-21765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8036AC70258, 0xFFFFC68141852F60, 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 Sat 12/3/2016 5:23:57 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!EnterSharedCrit+0x41)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8036AC70258, 0xFFFFC68141852F60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
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 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 12/3/2016 3:50:41 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\120316-24328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xA (0xFFFFCC80DC749F71, 0x2, 0x1, 0xFFFFF80094F6751F)
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.



On Sat 12/3/2016 12:32:38 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\120316-23640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xFC (0xFFFFBF8E36A1B820, 0x800000013C4009E3, 0xFFFFF8035573A870, 0x3)
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.

Hopefully this is what you're looking for

 

stutheironman

Reputable
Nov 8, 2015
8
0
4,510


I was thinking on doing a clean install on the machine but wasn't sure at first if it was a hardware issue or not. I really didn't want to do a new install but looks like it might be necessary if it's this screwed up :(
 

Sudiir12345

Commendable
Mar 3, 2016
28
0
1,540
Did you try to update all your drivers
If no then update all of them and replay whether your problem is solved
If yes then it is better to do a clean install and then install the latest drivers
 
Solution

stutheironman

Reputable
Nov 8, 2015
8
0
4,510


I tried to update all of my drivers including the graphics drivers but the updates failed. I'm currently trying to create a recovery disc and see if I can create a clean install. When doing a PC reset, it also failed. Is the recovery disc going to do the exact same thing as the recovery disc?
 

stutheironman

Reputable
Nov 8, 2015
8
0
4,510


Did a clean install and everything is back to the way it should be now. Thanks for your help man, I appreciate it