Blue Screen Error - SYSTEM_SERVICE_EXCEPTION (3b)

original title: IMAGE_NAME:  ntkrnlmp.exe__DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb__STACK_COMMAND:  .cxr 0xfffff88009391cf0 ; kb__FAILURE_BUCKET_ID:  X64_0x3B_nt!IopCheckDeviceAndDriver+74__IMAGE_NAME:  ntkrnlmp.exe__DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb__STACK_COMMAND:  .cxr 0xfffff88009391cf0 ; kb__FAILURE_BUCKET_ID:  X64_0x3B_nt!IopCheckDeviceAndDriver+74__

Hi, i have windows 7, my laptop its been showing me random blue screens, I downloaded a debugger, but I dont know what to do next. Any ideas of what's causing the problem??

Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffda018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800036a4cd4, fffff88009391cf0, 0}

Probably caused by : ntkrnlmp.exe ( nt!IopCheckDeviceAndDriver+74 )

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: fffff800036a4cd4, Address of the instruction which caused the bugcheck
Arg3: fffff88009391cf0, 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:
nt!IopCheckDeviceAndDriver+74
fffff800`036a4cd4 48875500        xchg    rdx,qword ptr [rbp]

CONTEXT:  fffff88009391cf0 -- (.cxr 0xfffff88009391cf0)
rax=0000000000000002 rbx=fffffa80048c6240 rcx=fffff800037fd590
rdx=fffff800037fd590 rsi=fffff800037fce80 rdi=fffffa80048c6200
rip=fffff800036a4cd4 rsp=fffff880093926c0 rbp=33fff800038bc600
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80048c6240
r11=fffff8a0056a8a52 r12=0000000000000000 r13=fffffa8006c77d20
r14=0000000006c77d20 r15=fffffa80041e0010
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!IopCheckDeviceAndDriver+0x74:
fffff800`036a4cd4 48875500        xchg    rdx,qword ptr [rbp] ss:0018:33fff800`038bc600=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800039862c7 to fffff800036a4cd4

STACK_TEXT: 
fffff880`093926c0 fffff800`039862c7 : 00000000`00000000 fffffa80`06c77d20 fffffa80`033ed600 fffffa80`03908010 : nt!IopCheckDeviceAndDriver+0x74
fffff880`09392720 fffff800`0397ca64 : fffffa80`048c6240 00000000`00000000 fffffa80`03908010 00000000`00000001 : nt!IopParseDevice+0xf7
fffff880`093928b0 fffff800`03981b76 : fffffa80`03908010 fffff880`09392a30 00000000`00000040 fffffa80`033ed600 : nt!ObpLookupObjectName+0x585
fffff880`093929b0 fffff800`03988887 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByName+0x306
fffff880`09392a80 fffff800`03992498 : 00000000`01eaf3e8 00000000`c0100080 00000000`00001104 00000000`01eaf3f8 : nt!IopCreateFile+0x2b7
fffff880`09392b20 fffff800`03681853 : 00000000`00000000 fffffa80`06ba8d00 00000000`00001f80 00000000`01eafbe0 : nt!NtCreateFile+0x78
fffff880`09392bb0 00000000`777702aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01eaf368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777702aa


FOLLOWUP_IP:
nt!IopCheckDeviceAndDriver+74
fffff800`036a4cd4 48875500        xchg    rdx,qword ptr [rbp]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!IopCheckDeviceAndDriver+74

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

STACK_COMMAND:  .cxr 0xfffff88009391cf0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!IopCheckDeviceAndDriver+74

BUCKET_ID:  X64_0x3B_nt!IopCheckDeviceAndDriver+74

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

0: kd> lmvm nt
start             end                 module name
fffff800`03612000 fffff800`03bee000   nt         (pdb symbols)          C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Sat Feb 27 10:55:23 2010 (4B88CFEB)
    CheckSum:         00545094
    ImageSize:        005DC000
    File version:     6.1.7600.16539
    Product version:  6.1.7600.16539
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.1.7600.16539
    FileVersion:      6.1.7600.16539 (win7_gdr.100226-1909)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Answer
Answer
Was this the first time you got a bugcheck/bluescreen/BSOD/crash?  Were there any recent changes to the system - any new hardware or software added or updated or removed?  You indicated a "random" bluescreen - do you mean that the bugcheck code varies, or that the BSOD comes up with no warning (which is pretty typical of a bugcheck)?

Can you upload the contents of c:\windows\minidump to your SkyDrive?

General guidance for dealing with bluescreens:

Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

Also consider running SFC /SCANNOW.

It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out  of the dialog.

Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot  completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

Wait for a bugcheck to occur after enabling verifier as described, and then upload it.

If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of  modules for a while, and see how things go. Then try the other modules.

Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're  using the latest BIOS.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated June 13, 2021 Views 8,088 Applies to: