That blue screen we encountered saying: “Your PC ran into a problem and needed to restart. We are just collecting some error info, and then you can restart.” is a System Service Exception error.
We might have often seen an event viewer screen for bug check 0x0000003B BSOD screen in Windows 10 and Windows 7, after which our PC won’t start.
Don’t worry; in this article, we are offering you seven fixes that you can use to answer your question about the blue screen event viewer issue.
Know that it occurs due to corrupted system files, incorrect registry configuration, faulty driver, or bad memory module.
You must have a question: What is the Exception exactly? And Why does it occur?
That’s why, before we look at the possible fixes in which the code for bugcheck was 0x0000003b 0x00000000c0000005, let us first understand System Service Exception code and its causes in Microsoft Windows 10.
What is the System Service Exception BSOD code?
System Service Exception is an exception that occurs when the system is executing a system service routine or thread that transitions from non-privileged code to privileged code.
A blue colored screen saying that the computer has rebooted from a bugcheck and a dump was saved in C drive reflects the System Service Exception.
This exception creates a C Windows memory .dmp or dump files with a memory .dmp report id and event log.
The professionals use this windows memory .dmp report saved in C windows to resolve the issue.
Parameters for System Service Exception are:
| Parameter | Description |
| 1 | It symbolizes the exception that has caused the bug check to occur. |
| 2 | It gives the instruction address responsible for the bug check |
| 3 | This is the address where the context record of the exception that caused the bug check is. |
| 4 | 0 (Zero) |
There are various arguments in the System Service Exception code such as 0x00000000c0000005, fffff802328375b0, ffff9c0a746c2330, and 0x0000000000000000. A dump might be created to help you or the professionals solve the issue on your system.
Argument 1: 0x00000000c0000005 – If the bugcheck was 0x0000003b 0x00000000c0000005 then 0x00000000c0000005 is the argument which implies the exception code responsible for the bugcheck.
Argument 2: fffff802328375b0 – This is the instruction address responsible for the bugcheck.
Argument 3: ffff9c0a746c2330 – This is the context record address of the exception.
Argument 4: 0x0000000000000000 – Zero.
C Windows memory dump file
When you see that windows blue screen, it creates a memory dump file or crash dump files containing information about the latest computer memory, which we use to diagnose and analyze the problem.
There are several types of memory dumps such as Complete memory dump, Kernel memory dump, small memory dump, and automatic memory dump, created by our machine to contain information about the crash at that particular time.
By default, Windows use automatic memory dump to help developers resolve the cause of the error caused due to installed hardware, driver, etc.
Causes for System Service Exception code BSOD
This exception code indicates that the executing code gave an exception, and the thread below it was a system thread.
Parameter 1 returned by the exception contains exception information described in NTSTATUS values. The codes for an exception are stored in a Windows Driver Kit header file called nstatus.h.
Other than the 0x0000003B error, other common exceptions are:
0x80000003: Status_Breakpoint – This indicates a breakpoint (or assert) that the system encountered because of the absence of kernel debugger.
0xC0000005: STATUS_ACCESS_VIOLATION – This indicates a memory access violation defined by parameter 4 of the bug check. It is the address that the driver had attempted to access.
Now that you have information about this Microsoft issue, let us help you answer this issue.
Solutions for Windows 10
Exception BSOD “The bug check was 0x0000003b (0x00000000c0000005, 0xfffff80003ac7077, 0xfffff880ba6de50, 0x0000000000000000). A dump was created for the bug check.”
A blue screen with the same or similar message has appeared in front of us many times when we have installed a new device driver, system service, or hardware.
Before you try any of the troubleshooting steps given below, use the following solutions:
- Update the new driver or remove the new device driver, service, or new hardware and restart the system. It might solve this problem.
- If you cannot start windows 10 normally and the system is frequently restarting, try to perform System Repair from Advanced Options. This will run a diagnostic check and fix problems such as missing corrupt files, incompatible drivers, poor configuration settings, problematic update installation, etc.
After the above steps, restart your system and check if we can answer your BSOD error question.
If the problem persists, follow the below fixes after booting your system in safe mode to determine what caused your system to crash and fix it.
1. Check Faulty Device Driver
Before going to hardware, first, you must check for device drivers that might be faulty. The most common issue behind the “Your computer has rebooted from a bugcheck” blue screen message.
These drivers will be marked with a yellow exclamation next to them in the device driver manager.
Follow the steps to resolve this issue:
- Press the Windows icon and “X” key simultaneously on your keyboard and click on the device manager to check the driver.
- Click on the faulty driver and right-click on it.
- Click either uninstall or update the driver.
- Restart the system to implement the driver changes.
You can later install the latest and compatible driver by downloading it from your computer manufacturer’s driver website.
2. Repair Corrupted Files with SFC Utility
Other than drivers, faulty system files sometimes cause the computer to face this error.
System files and drivers are an integral part of our Windows 10 Operating System to run smoothly. The operating system misbehaves if these files or drivers are corrupted or go missing.
This is one of the causes of the System Service Exceptions in Windows 10 BSOD error.
To fix this issue, you can use the SFC utility to scan the system by following the following steps:
- Search “cmd’ in the Windows search bar.
- Command Prompt option will be visible. Right-click on it. Choose “Run as administrator.”
- Run the command: DISM /online /cleanup-image /restorehealth by pressing the Enter key.
- Next run command: sfc/scannow by pressing the Enter key.
This will start scanning the system for any missing or corrupted files and then restore the system.
For example, if the SFC or System File Checker finds any protected files overwritten by incorrect files, it will extract those files from system backup, called dllcache, and then replace them with the correct ones.
Once the scanning is 100% completed, restart your system to let the changes take effect.
3. Check Bed Memory Modules
Corrupt system files, faulty drivers, and bed memory modules are mostly responsible for the BSOD blue screen errors.
You must be very careful when setting up RAM in the system because any RAM issue, be it from malfunctioning or incorrect setup, can cause BSOD errors or even render the computer unable to boot.
To check the hardware, follow the below steps:
- As a safety precaution, power off your computer by unplugging it from the power source.
- Open the system and search for the RAM sticks.
- Remove all the Ram sticks and try to turn on the computer by inserting each stick.
- If any of them is faulty, the system won’t turn on. Replace it with a new stick.
4. Run CHKDSK
You can also use this option to check the system for any errors by the below steps:
- Search “cmd’ in the Windows search bar.
- Command Prompt option will be visible. Right-click on it. Choose “Run as administrator.”
- Run the command: chkdsk /r by pressing the Enter key.
This might take time, but it will scan your system for errors and fix any issues that might occur.
Do not forget to restart your system once the scanning and fixing are completed.
5. Disable Fast Startup and Hibernate
Sometimes good can also be bad.
The hybrid shutdown feature or the fast startup feature of Windows 10 is no different.
This feature can cause BSOD error when the system wakes up from sleep mode, and thus you will have to disable the hibernation and fast startup feature in settings to get rid of this problem.
Follow the steps to do the same:
- In the search bar, search “Control Panel” and open it.
- Search “Power Options,” open it, and click on the “Choose what power buttons do” option from the window’s left side.
- Click on “Change settings are currently unavailable” and then click on “Turn on fast startup under “Shutdown settings.”
Restart the system. This fix will solve the blue screen problem if caused by the new windows feature hibernate and fast startup.
6. Run Memory Diagnostic Tool
You can use the Windows inbuilt memory diagnostic tool to identify if the blue screen occurs due to memory errors.
Follow the below steps to perform a Memory diagnostic:
- Type “Memory” in the search bar and open the Windows Memory Diagnostic tool.
- Click Restart Now and check for the option of the problem.
Windows will then restart and start diagnosing the system’s memory.
This procedure might take some time, but you must wait for the process to complete 100%. Try to keep the system plugged in so the process can continue uninterrupted.
7. Disable Google Update Services
Sometimes, an error is caused when the system runs into a problem due to google update services. You will have to disable them to fix this problem.
Follow the below steps to disable it:
- Simultaneously press the Windows icon and “R” key on the keyboard.
- Enter msconfig in the Run dialog and then press enter.
- In the System Configurations Window, go to the Services tab and scroll down to Google Update Services.
- Disable both of them and click apply and then click OK.
Restart windows to allow the changes to take effect.
In this post, we tried to answer your question and provide you with information to solve this issue for your machine due to faulty drivers, hardware, system file, etc.
However, After you test all the above methods, if you are still unable to resolve this bug check, you can seek expert help by sharing the location where the C windows memory .dmp file or dump was saved.
This Windows memory .dmp report saved in C windows will contain a memory .dmp report id used to resolve the bug check in windows 7 and above.
The fixes here do not require you to check the C windows minidump and apply it to Windows 7 and above.
