Frequent random BSODs, 0x0000003b

[ryangd2]

Hello, been getting lots of BSODs lately most often 0x0000003b.
Sometimes it's "IRQL_LESS_THAN_OR_EQUAL", sometimes "SYSTEM_SERVICE_EXCEPTION".

I don't know what triggers them, seems completely random. Sometimes it'll crash while idle, after I come back to it from somewhere else it'd have restarted.

Any help'd be much appreciated.

Edit: Oh almost all have had to do with fltmgr.sys, but one or two times it showed a different .sys file, but I cant rmb which.

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

 

[ryangd2]

I've got my com set up like in that thread, but no dmp files are created in the windows/minidump folder.

 

[Arc]

OK, in that case take a camera snap of the next BSOD screen and let us see it. The onscreen codes will give some information there hopefully.

But, I will suggest you to forget about the setup and merge the registry key as pointed.

 

[ryangd2]

There's the screenshot.

 

[Laith]

The dump is saved. Try to find it. It has not been set to /Windows/MiniDump

 

[Arc]

Two important information are obtained from the screenshot.

First, it says that the crash dump is recorded. May be you ran any disc cleanup tool that deleted those.

Second, it is a stop 0x3B. The probable causes are:

• Mismatch system services, causes for pirated OS install and/or not updating the OS.
• Memory failure.
• Some misbehaving device driver, specially the graphics driver.

Let us check those possibilities.

You can say it better about the first alternative. If anything is there, rectify it.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

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.