BSOD SYSTEM_SERVICE_EXCEPTION CmBatt.sys

Well, another BSOD. Here are the dumps. This must be due to heating again I guess ( I know my bad ).

Hi aritra2116.

A SYSTEM_SERVICE_EXCEPTION BSOD is basically a memory failure. Either it is the RAM that is failing or some driver is passing bad info to the memory.

But I am not getting any hint of a failing CmBatt.sys in the rash dump.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

I got another BSOD. This time 0x1e. I guess this could mean multiple things. I'll get back with memtest86+ and DV.

Okay I am finally back with memtest86+. Was away for a day due to school and stuff. It found no errors. (Screenshot below). I guess now DV would find out what is really causing the problem if we're lucky. Question : Should I also enable verifier for all Microsoft drivers too rather than just the non - Microsoft ones?

Sorry to bump the thread like this, but I have a question above that I asked. I know I should be patient.

Hi Aritra.

Sorry that I was not able to come online for a few days. Now I am back as usual (at least I hope so).

While running DV, you should not verify the drivers provided by Microsoft, Macrovision, Brother and "unknown".

Run Driver Verifier on all the other drivers.

Okay, here are the new dumps but you have to note that this was another BSOD I got after the first one and before enabling DV. I haven't got a BSOD yet while running DV, but I should say that I didn't get the whole lot of time to stress the computer and also, get time to even work on it so my routine is pretty tight nowadays. This BSOD might give some other clues. I'd try to get a BSOD with DV ASAP. If I don't get one, I'd try to turn off DV and see if I get more BSODs. Right now, I'd like to focus on this dump attached.

Hi Aritra.

Sorry to say it, but the zip contains only one crash dump that we have checked earlier, the stop 0x3B one.

Attachment 327482

May be the DV is causing BSODs too quicker to be recorded?

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver (SynTPEnh usually).
5. Apply > OK
6. Accept then restart.

Nor let DV run again. Hopefully this time it will be able to produce a crash dump.

Arc said:

Hi Aritra.

Sorry to say it, but the zip contains only one crash dump that we have checked earlier, the stop 0x3B one.

Attachment 327482

May be the DV is causing BSODs too quicker to be recorded?

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver (SynTPEnh usually).
5. Apply > OK
6. Accept then restart.

Nor let DV run again. Hopefully this time it will be able to produce a crash dump.

Oh, my bad then. But as I said before, I did have another BSOD before enabling DV. Maybe the crash dump wasn't collected. I will disable DV for now and do what you follow. I didn't have another BSOD yet after enabling DV.

Hey there Arch, just a little update here. DV found the cause to be the NVidia Driver. I updated it. I will wait and see if I get another BSOD.