WIndows 7 - Blue Screen - SYSTEM_SERVICE_EXCEPTION (3b)

original title: WIndows 7 - BS - Memory Management Error

I just built this system and installed Windows 7 (64 bit).   I am seeing a number of blue screen issues and I'm not sure if it is hardware or software.    Motherboard BIOS and drivers are fully up to date.  Windows 7 is fully updated.    Three types of blue screen have appeared ,  Memory Management, IRQL, and System Service Exception.   Memory Management is the error most seen.   I am tracking when the errors occur, but so far there is no obvious candidate.  Suspecting bad memory, I ran prime95, which showed failures within seconds to 2 minutes. 

System details

MSI 870A-G54 Motherboard

Corsair XMS dual channel DDR 3 1333MHZ 8G Memory sitcks

AMD Phenom(tm) II X4 Processor 3.2 GHz

 

Below are two of the DMP files. 

 

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 3B, {c0000005, fffff80003117969, fffff880063eddd0, 0}

 

Probably caused by : memory_corruption ( nt!MiObtainSystemVa+6b9 )

 

Followup: MachineOwner

---------

 

1: 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: fffff80003117969, Address of the instruction which caused the bugcheck

Arg3: fffff880063eddd0, 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!MiObtainSystemVa+6b9

fffff800`03117969 0f82a36b0100    jb      nt! ?? ::FNODOBFM::`string'+0xe95c (fffff800`0312e512)

 

CONTEXT:  fffff880063eddd0 -- (.cxr 0xfffff880063eddd0)

rax=000000000000fee1 rbx=00000000ffffffff rcx=000000000000011f

rdx=0000000000000000 rsi=0000000000000000 rdi=000000000000011f

rip=fffff80003117969 rsp=fffff880063ee7a0 rbp=0000000000000006

 r8=0000000000000000  r9=000000000000ffff r10=0000000000000001

r11=0000000000000040 r12=fffff8000328db80 r13=0000000000000000

r14=0000000000010000 r15=000000000000011f

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!MiObtainSystemVa+0x6b9:

fffff800`03117969 0f82a36b0100    jb      nt! ?? ::FNODOBFM::`string'+0xe95c (fffff800`0312e512) [br=0]

Resetting default scope

 

CUSTOMER_CRASH_COUNT:  1

 

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

 

BUGCHECK_STR:  0x3B

 

PROCESS_NAME:  TrustedInstall

 

CURRENT_IRQL:  0

 

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003117969

 

STACK_TEXT: 

fffff880`063ee7a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiObtainSystemVa+0x6b9

 

 

FOLLOWUP_IP:

nt!MiObtainSystemVa+6b9

fffff800`03117969 0f82a36b0100    jb      nt! ?? ::FNODOBFM::`string'+0xe95c (fffff800`0312e512)

 

SYMBOL_STACK_INDEX:  0

 

SYMBOL_NAME:  nt!MiObtainSystemVa+6b9

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: nt

 

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

 

STACK_COMMAND:  .cxr 0xfffff880063eddd0 ; kb

 

IMAGE_NAME:  memory_corruption

 

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiObtainSystemVa+6b9

 

BUCKET_ID:  X64_0x3B_nt!MiObtainSystemVa+6b9

 

 

 

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck A, {9242483, 2, 0, fffff80003610aeb}

 

Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )

 

Followup: MachineOwner

---------

 

2: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0000000009242483, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, bitfield :

            bit 0 : value 0 = read operation, 1 = write operation

            bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff80003610aeb, address which referenced memory

 

Debugging Details:

------------------

 

 

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032d00e8

 0000000009242483

 

CURRENT_IRQL:  2

 

FAULTING_IP:

hal!HalRequestSoftwareInterrupt+5c

fffff800`03610aeb 0fba64242009    bt      dword ptr [rsp+20h],9

 

CUSTOMER_CRASH_COUNT:  1

 

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

 

BUGCHECK_STR:  0xA

 

PROCESS_NAME:  csrss.exe

 

IRP_ADDRESS:  ffffffffffffff88

 

TRAP_FRAME:  fffff8800bb6a3d0 -- (.trap 0xfffff8800bb6a3d0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000080000000 rbx=0000000000000000 rcx=0000000000000200

rdx=000000000004001f rsi=0000000000000000 rdi=0000000000000000

rip=fffff80003610aeb rsp=fffff8800bb6a560 rbp=fffff88003164180

 r8=0000000000000000  r9=fffffa800d7bbbb0 r10=0000000000000001

r11=0000000000000001 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up di ng nz na po nc

hal!HalRequestSoftwareInterrupt+0x5c:

fffff800`03610aeb 0fba64242009    bt      dword ptr [rsp+20h],9 ss:0018:fffff880`0bb6a580=00000246

Resetting default scope

 

LAST_CONTROL_TRANSFER:  from fffff8000309ebe9 to fffff8000309f640

 

STACK_TEXT: 

fffff880`0bb6a288 fffff800`0309ebe9 : 00000000`0000000a 00000000`09242483 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff880`0bb6a290 fffff800`0309d860 : 00000000`00000130 fffffa80`0e50d010 fffffa80`0a17e000 00000000`00000200 : nt!KiBugCheckDispatch+0x69

fffff880`0bb6a3d0 fffff800`03610aeb : fffffa80`0df7e000 fffff800`031cafbd fffff800`03224c00 fffff800`030a3790 : nt!KiPageFault+0x260

fffff880`0bb6a560 fffff800`03091ef3 : fffffa80`0d7bbb60 fffffa80`0e50d088 fffffa80`0df7e140 00000000`00000140 : hal!HalRequestSoftwareInterrupt+0x5c

fffff880`0bb6a590 fffff800`03080d64 : fffffa80`0d7bbb60 00000000`00000001 00000000`00000000 fffffa80`0e50d088 : nt!KiInsertQueueApc+0x243

fffff880`0bb6a5c0 fffff800`030b50bc : fffffa80`0e50d010 00000000`00000000 00000000`00000000 00000000`00000086 : nt!KeInsertQueueApc+0x80

fffff880`0bb6a620 fffff800`03092cf7 : 00000000`00000000 00000000`00000000 00000000`20707200 00000000`00000000 : nt!IopCompleteRequest+0xb8c

fffff880`0bb6a6f0 fffff800`030a4b9d : fffffa80`0d7bbb60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7

fffff880`0bb6a770 fffff800`030a3eaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KiCommitThreadWait+0x3dd

fffff880`0bb6a800 fffff960`001789fc : fffff900`00000002 fffffa80`097b5e00 fffff900`00000001 fffff880`0000000d : nt!KeWaitForMultipleObjects+0x272

fffff880`0bb6aac0 fffff960`00179940 : 00000000`00000000 fffff900`c0153c30 fffff960`003c1560 fffff900`c0153ac0 : win32k!xxxMsgWaitForMultipleObjects+0x108

fffff880`0bb6ab40 fffff960`00134684 : fffffa80`00000001 fffffa80`0000000c fffffa80`0d7bbb60 fffff6fc`4005d9e8 : win32k!xxxDesktopThread+0x254

fffff880`0bb6abc0 fffff960`001b429a : fffffa80`00000001 fffff960`003c1560 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x64

fffff880`0bb6abf0 fffff800`0309e8d3 : fffffa80`0d7bbb60 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36

fffff880`0bb6ac20 000007fe`fd291eda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`01f4fd88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd291eda

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP:

win32k!xxxMsgWaitForMultipleObjects+108

fffff960`001789fc 8bf0            mov     esi,eax

 

SYMBOL_STACK_INDEX:  a

 

SYMBOL_NAME:  win32k!xxxMsgWaitForMultipleObjects+108

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: win32k

 

IMAGE_NAME:  win32k.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  4d2415ea

 

FAILURE_BUCKET_ID:  X64_0xA_win32k!xxxMsgWaitForMultipleObjects+108

 

BUCKET_ID:  X64_0xA_win32k!xxxMsgWaitForMultipleObjects+108

 

 

Question Info


Last updated April 20, 2019 Views 24,313 Applies to:
Answer
Answer

Solution Found!!  There were two issues.   The store installed the RAM in the wrong slots, which caused the random Blue Screens (BS) once or twice a day.   The second issue, the screen going horizontal with white and gray lines was a video card defect.  Moving the RAM to DIMM slots 1 and 2 stopped the BS.   Replacing the video card solved the other issue.  Life is good.    Thank you very much for your assistance.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

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

How satisfied are you with this response?

Thanks for your feedback.