BSOD - ntoskrnl.exe - System Service Exception

mamba238

Distinguished
Oct 16, 2012
110
1
18,695
Hello, I recently had a BSOD. I view it using BlueScreenView and the driver that cause the crash was ntoskrnl.exe. Can anyone help me out with this situation, I don't know where to start.


==================================================
Dump File : 040115-16504-01.dmp
Crash Time : 4/1/2015 6:26:17 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff800`03067f48
Parameter 3 : fffff880`0b675930
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74ec0
File Description : NT Kernel & System
Company : Microsoft Corporation
File Version : 6.1.7601.18741 (win7sp1_gdr.150202-1526)
Processor : x64
Crash Address : ntoskrnl.exe+74ec0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Full Path : C:\Windows\Minidump\040115-16504-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 400,064
==================================================
 
Solution
the suberror code was
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

depending on what you were doing, I would look for:
overclocking related errors, (turn of any overclocking in BIOS, and software overclock for CPU or GPU)
confirm power is good and your fans are spining and the components are not overheating.
-If you were running a 32bit game on steam I have seen people get this error and they were able to "fix" the problem by re installing steam.
the suberror code was
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

depending on what you were doing, I would look for:
overclocking related errors, (turn of any overclocking in BIOS, and software overclock for CPU or GPU)
confirm power is good and your fans are spining and the components are not overheating.
-If you were running a 32bit game on steam I have seen people get this error and they were able to "fix" the problem by re installing steam.
 
Solution