0x0000003b windows server 2012 r2

Картинка с сайта: www.drivereasy.com

If you’re trying boot your computer into Windows but it fails and shows the blue screen,  and you’re seeing this error saying STOP: 0x0000003b, you’re not alone. Many Windows users are reporting it. But the goo news is you can fix it easily by yourself.

2 easy solutions to fix 0x0000003b:

Here are 3 solutions for you to try. You may not need to try them all; just work your way down until you find the one works for you.

1. Update all the available drivers
2. Install the hotfix from Microsoft

You’ll need to be logged into Windows on the problem computer to try any of these solutions. If you can’t log into Windows, power on and off your PC 3 times to perform a hard reboot and restart it in Safe Mode, then try these solutions. 

Solution 1: Update all the available drivers

0x0000003b BSOD error is probably caused by any old or incorrect drivers, especially your corrupted graphics driver. You need to verify that all your devices have the right driver, and update those that don’t. If you’re not comfortable playing around with drivers manually, you can do it automatically with Driver Easy.

Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to be troubled by the wrong driver you would be downloading, and you don’t need to worry about making a mistake when installing. Driver Easy handles it all.

You can update your drivers automatically with either the 7 days free trial or the Pro version of Driver Easy. It takes just 2 clicks, and you get full support and a 30-day money-back guarantee with the Pro version:

1. Download and install Driver Easy.
2. Run Driver Easy and click the Scan Now button. Driver Easy will then scan your computer and detect any problem drivers.
   

   Картинка с сайта: www.drivereasy.com

3. Click the Activate & Update button next to the flagged device to automatically download and install the correct version of this driver.

   Or click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system (You’ll need the Pro version for this – when you select Update All, you’ll get a prompt to upgrade. If you’re not prepared to purchase the Pro version yet, Driver Easy provides a 7-day trial at no cost, granting access to all Pro features like fast downloads and easy installation. No charges will occur until after your 7-day trial period ends.)

   

   Картинка с сайта: www.drivereasy.com

4. Restart your computer for the change to take effect.

Solution 2: Install the hotfix from Microsoft

To help users solve the 0x0000003b BSOD error, Microsoft has released a Hotfix for those who’re on Windows 7 or Windows Server 2008 R2 and using some IEEE 1394 device.

For more concrete information or to download the Hotfix, please go to Microsoft website.

Readers help support Windows Report. We may get a commission if you buy through our links.

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

There are many annoying problems that are affecting current Windows users, which are on Windows 7, 8 and 8.1 and we try to cover the latest updates that are fixing various issues. Today we’re covering the 0x3B error.

As you have probably been affected, the 0x3B Stop error occurs randomly when you log on a computer that is running Windows 8.1 or Windows Server 2012 R2. Now, via the Windows Update functionality, this has been solved, so you just need to make sure that you have update rollup 2984006 installed and running on your machines.

READ MORE: Skype App for Windows 8, Windows 10 Now Lets you Edit or Delete Messages, Adds Notifications

0x3B error gets fixed with recent Windows Update

The above-mentioned stop error indicates a SYSTEM_SERVICE_EXCEPTION issue. Thus, the parameters in this Stop error message vary, depending on the configuration of the computer. Microsoft also mentions that not all 0x0000003B Stop errors are caused by this issue. The cause is the following:

This issue occurs because there is a race condition between two threads during the logon process.

The update applies to Windows Server 2012 R2 versions, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1 and Windows RT 8.1. Leave your comment below and let us know if this has solved your problems.

Download hotfix for 0X3B error

You can also fix this problem by installing Microsoft’s hotfix for this issue that they launched then. Here is how to perform this action:

1. Go on this link (Microsoft Support link)
2. Click on ‘Hotfix Download Available’
3. Install the hotfix on your Windows PC
4. After it is installed – restart your PC

Here it is, the only thing you have to do is to check if the problem still persists. Let us know in the comment section if this fix helped your case.

READ ALSO: Surface RT Tablets to be Discontinued this Year, Death is the Only Solution

Radu Tyrsina has been a Windows fan ever since he got his first PC, a Pentium III (a monster at that time).

For most of the kids of his age, the Internet was an amazing way to play and communicate with others, but he was deeply impressed by the flow of information and how easily you can find anything on the web.

Prior to founding Windows Report, this particular curiosity about digital content enabled him to grow a number of sites that helped hundreds of millions reach faster the answer they’re looking for.

Blue screen Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
Server reboots after connecting via meshcentral to the desktop and logging in.
See minidump below.

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users******\Downloads\061021-10265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Edition build lab: 14393.4283.amd64fre.rs1_release.210303-1802
Machine Name:
Kernel base = 0xfffff800c087e000 PsLoadedModuleList = 0xfffff800c0b820a0
Debug session time: Thu Jun 10 10:34:52.039 2021 (UTC — 4:00)
System Uptime: 20 days 22:59:41.516
Loading Kernel Symbols
………………………………………………………
……………………………………………………….
………………………………
Loading User Symbols
Loading unloaded module list
………………………………………..
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800c09db2f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffab0180bb8f00=000000000000003b
2: kd> !analyze -v

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

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3483

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 29003

Key  : Analysis.Init.CPU.mSec
Value: 2374

Key  : Analysis.Init.Elapsed.mSec
Value: 56426

Key  : Analysis.Memory.CommitPeak.Mb
Value: 81

Key  : WER.OS.Branch
Value: rs1_release

Key  : WER.OS.Timestamp
Value: 2021-03-03T18:02:00Z

Key  : WER.OS.Version
Value: 10.0.14393.4283

VIRTUAL_MACHINE: HyperV

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff941497ae9d8

BUGCHECK_P3: ffffab0180bb97e0

BUGCHECK_P4: 0

CONTEXT: ffffab0180bb97e0 — (.cxr 0xffffab0180bb97e0)
rax=fffff907801e0330 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000200 rsi=0000000000000000 rdi=fffff907801e02e0
rip=fffff941497ae9d8 rsp=ffffab0180bba1d0 rbp=ffffab0180bba320
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000003 r12=0000000000000100 r13=0000000000000001
r14=fffff907801e0330 r15=fffff907801e02e0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
win32kbase!RawInputManagerObjectCreateKernelHandle+0x18:
fffff941497ae9d8 83790401 cmp dword ptr [rcx+4],1 ds:002b:0000000000000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MeshAgent.exe

STACK_TEXT:
ffffab0180bba1d0 fffff941495d7722 : 0000000000000001 ffffffffffffffff 0000000000000000 0000000000000008 : win32kbase!RawInputManagerObjectCreateKernelHandle+0x18
ffffab0180bba220 fffff941495d5d74 : 0000000000000000 0000000000000100 ffffab0180bba3e4 0000000000be705e : win32kfull!CreatePseudoDigitizerDevice+0x86
ffffab0180bba380 fffff941495d5cb0 : fffff90781bc8010 0000000000000100 0000000000000001 0000000000989680 : win32kfull!InitializeTouchInjectionWithQDCData+0x9c
ffffab0180bba3c0 fffff941496177b7 : 0000000000000001 ffffab0180bba4c0 0000000000000004 0000000000000100 : win32kfull!InitializeTouchInjection+0x4c
ffffab0180bba410 fffff800c09eae03 : ffff948fa1c63080 0000000000000000 0000000000000020 0000000000000000 : win32kfull!NtUserInitializeTouchInjection+0x47
ffffab0180bba440 00007ffd8a598a04 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
000000fb5d7fd098 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd`8a598a04

SYMBOL_NAME: win32kbase!RawInputManagerObjectCreateKernelHandle+18

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

IMAGE_VERSION: 10.0.14393.4283

STACK_COMMAND: .cxr 0xffffab0180bb97e0 ; kb

BUCKET_ID_FUNC_OFFSET: 18

FAILURE_BUCKET_ID: 0x3B_c0000005_win32kbase!RawInputManagerObjectCreateKernelHandle

OS_VERSION: 10.0.14393.4283

BUILDLAB_STR: rs1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ccc3339b-992c-3b1f-10f4-29873219b5e2}

Followup: MachineOwner