BSOD SYSTEM_SERVICE_EXCEPTION 0x0000003b in this two days...

people999999 · 27 May 2014

Dear All, I have been using this computer fine before, recently I change an CPU from athlon x2 4000+ to phentom x4 9750 and a display card from Onboard video to HD6450.

And the BSODs comes up since that, I thought maybe due to the graphic drivers of the new video card at first. So I tried to remove everything from AMD/ATI and using back my onboard video now (By the way during the uninstall process, few bsods occured too). I am thinking to swap back to my old cpu too, but just that heatsink is so hard to remove and also I am out of the heatsink paste on hands.

So now I am just using my new cpu as a new components. But today BSODs occured again, Could you guys please advise if there any possible way to fix my problem ? Thanks a lot.

Arc · 28 May 2014

Hi people999999.

Your BSODs are stop 0x3B. A not properly updated system may cause it very frequently. So make it sure at first that your windows ir properly up-to-date.

It may be caused by memory problems, too. 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.

HP OEM on Gigabyte

_________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88000e0437e, fffff8800b3b1b50, 0}

Probably caused by : fltmgr.sys ( fltmgr!FltpAllocateIrpCtrl+4e )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88000e0437e, Address of the instruction which caused the bugcheck
Arg3: fffff8800b3b1b50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
fltmgr!FltpAllocateIrpCtrl+4e
fffff880`00e0437e 8b8670030000    mov     eax,dword ptr [rsi+370h]

CONTEXT:  fffff8800b3b1b50 -- (.cxr 0xfffff8800b3b1b50;r)
rax=fffffa80061a9cb0 rbx=fffffa8007d965f0 rcx=fffffa80061a9b60
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000003
rip=fffff88000e0437e rsp=fffff8800b3b2530 rbp=fffff8800b3b2560
 r8=fffffa8007d965f0  r9=fffff8800b3b2610 r10=fffffa800630a800
r11=fffff8800b3b2640 r12=0000000000000001 r13=fffffa8007d965f0
r14=0000000000000000 r15=fffff8800b3b2610
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
fltmgr!FltpAllocateIrpCtrl+0x4e:
fffff880`00e0437e 8b8670030000    mov     eax,dword ptr [rsi+370h] ds:002b:00000000`00000370=????????
Last set context:
rax=fffffa80061a9cb0 rbx=fffffa8007d965f0 rcx=fffffa80061a9b60
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000003
rip=fffff88000e0437e rsp=fffff8800b3b2530 rbp=fffff8800b3b2560
 r8=fffffa8007d965f0  r9=fffff8800b3b2610 r10=fffffa800630a800
r11=fffff8800b3b2640 r12=0000000000000001 r13=fffffa8007d965f0
r14=0000000000000000 r15=fffff8800b3b2610
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
fltmgr!FltpAllocateIrpCtrl+0x4e:
fffff880`00e0437e 8b8670030000    mov     eax,dword ptr [rsi+370h] ds:002b:00000000`00000370=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88000e0437e

STACK_TEXT:  
fffff880`0b3b2530 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpAllocateIrpCtrl+0x4e


FOLLOWUP_IP: 
fltmgr!FltpAllocateIrpCtrl+4e
fffff880`00e0437e 8b8670030000    mov     eax,dword ptr [rsi+370h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  fltmgr!FltpAllocateIrpCtrl+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME:  fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7929c

IMAGE_VERSION:  6.1.7601.17514

STACK_COMMAND:  .cxr 0xfffff8800b3b1b50 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!FltpAllocateIrpCtrl+4e

BUCKET_ID:  X64_0x3B_fltmgr!FltpAllocateIrpCtrl+4e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_fltmgr!fltpallocateirpctrl+4e

FAILURE_ID_HASH:  {234bac55-0e4c-b5f0-aee1-d98cd2e9e2f7}

Followup: MachineOwner
---------

people999999 · 28 May 2014

Thanks for reply Arc....Just finished the Memtest86+ test for whole night...it looks fine without any error. So Now I am going to check the drivers issue. I think I got all the windoes update installed, but for my mb drivers, as my mb is kindly quite old..its GA-MA78GM-S2H..do I need to install the most updated SB drivers from AMD ? Also I checked other BSOD posts in this forum yesterday, some said the DaemonTools has BSOD issue in win7 and receommended to remove that, So I am gonna to have a try to uninstall that.

Anyway, does 3b error code has a chance due to the defective hardware like CPU ? As actually I haven't installed anything new software/drivers recently...so wondering if my new replaced CPU has some problems.....

Arc · 29 May 2014

A stop 0x3B is caused by three reasons mainly. One is physical memory failure. Another one is misbehaving device driver. And the third one is failing system services. A not properly updated system causes it.

Daemon tools cause BSODs, but not a 0x3B usually. And, any other hardware does not contribute to a stop 0x3B usually, too.

Let us know the result of driver verifier.

But, a counterfeit windows installation does not take the updates properly, and their always remains a chance of stop 0x3B BSODs, despite of all actions.

At this point, you should install windows using an original installation media and activate it using a legit activation key.

people999999 · 29 May 2014

Thanks for ur reply. I have much more understanding the 3b code right now.
I have installed the AMD chipset driver & uninstalled the Daemon Tools plus removed the SPTD driver by the duplexsecure installer, also turn on the driver verifier as well. And now almost two hours gone, my computer not yet have the BSOD appears, just a little bit sluggish though. I will keep turn on DV for whole day to see, if no problem at all, I will add back the HD6450 PCIe card for a test too.

Thedoctor44 · 29 May 2014

He means your Windows installation is counterfeit, you must re-install your OS with a genuine license.