My problem is I have a new computer running windows 8 pro, fresh install with all updates applied.  When I try to view private message queue on another machine on the same network in the same domain running either windows server 2008 or windows 7 using the mmc snapin on my windows 8 machine it will bsod my windows 8 machine.  This behavior is repeatable and it can also be repeated from another machine running windows 8 pro.  I have googled this problem and have not found an answer.  I posted on the microsoft community forums and they pointed me here.  I am also providing a link to a zip file with 2 mdp files and the system info for my machine.  If there is a better forum to post this to please let me know.

thanks,

Kent

https://skydrive.live.com/redir?resid=7F52DF95876FD8A9!165&authkey=!AJpcHD1Emhn_WVc

Bubk

I followed you over and suggest you might also want to cross post this in the windows server section if you have not already.

good Luck

zz

The crash is caused by the message queue driver/service:

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 000007fae22140e0, Virtual address for the attempted execute.
Arg2: 7c40000120c6a025, PTE contents.
Arg3: fffff880173025e0, (reserved)
Arg4: 0000000080000005, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  mqsvc.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880173025e0 -- (.trap 0xfffff880173025e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fae21ec950 rbx=0000000000000000 rcx=000000910789a930
rdx=00000091092ce4a8 rsi=0000000000000000 rdi=0000000000000000
rip=000007fae22140e0 rsp=fffff88017302778 rbp=fffff88017302b80
 r8=fffffa8011cbe940  r9=0000000000000521 r10=fffffa800d24ff20
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
000007fa`e22140e0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff803cea03fe9 to fffff803ce872440

STACK_TEXT:  
fffff880`17302408 fffff803`cea03fe9 : 00000000`000000fc 000007fa`e22140e0 7c400001`20c6a025 fffff880`173025e0 : nt!KeBugCheckEx
fffff880`17302410 fffff803`ce92ad9c : fffff880`173025e0 ffff7e17`5f861fcf fffffa80`0d24ff20 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x344b5
fffff880`17302450 fffff803`ce8ac95d : fffff880`17302500 00000000`c0000016 fffffa80`11f1e080 fffffa80`11cbe940 : nt! ?? ::FNODOBFM::`string'+0x3440d
fffff880`173024a0 fffff803`ce86feee : 00000000`00000008 00000000`00000000 00000000`00000000 fffff880`173025e0 : nt!MmAccessFault+0x3ed
fffff880`173025e0 000007fa`e22140e0 : fffff880`0520b297 fffffa80`0d24fef0 00000000`00000000 fffff8a0`03993600 : nt!KiPageFault+0x16e
fffff880`17302778 fffff880`0520b297 : fffffa80`0d24fef0 00000000`00000000 fffff8a0`03993600 fffff980`00000000 : 0x000007fa`e22140e0
fffff880`17302780 fffff880`0520c0d7 : 00000000`00000000 00000091`092ce4a8 00000000`00000000 00000000`00000000 : mqac!ACCreateQueue+0xa77
fffff880`173027f0 fffff803`cec476c7 : fffffa80`11dc0ad0 fffffa80`12d38490 00000000`00000521 00000000`00000000 : mqac!ACDeviceControl+0x62b
fffff880`17302890 fffff803`cec5c8a6 : 00000000`00000000 00000000`00000080 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x7e5
fffff880`17302a20 fffff803`ce871453 : fffff880`17302ad8 00000000`00000000 00000000`00000001 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`17302a90 000007fa`ee642c5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000091`092ce448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fa`ee642c5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mqac!ACCreateQueue+a77
fffff880`0520b297 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  mqac!ACCreateQueue+a77

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mqac

IMAGE_NAME:  mqac.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5010abc2

BUCKET_ID_FUNC_OFFSET:  a77

FAILURE_BUCKET_ID:  0xFC_mqac!ACCreateQueue



    Mapped memory image file: d:\sym\dl\mqac.sys\5010ABC233000\mqac.sys
    Image path: \SystemRoot\system32\drivers\mqac.sys
    Image name: mqac.sys
    Timestamp:        Thu Jul 26 04:30:26 2012 (5010ABC2)
    CheckSum:         0002F0A3
    ImageSize:        00033000
    File version:     6.2.9200.16384
    Product version:  6.2.9200.16384
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.0 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Windows Operating System
    InternalName:     MQAC.SYS
    OriginalFilename: MQAC.SYS
    ProductVersion:   6.2.9200.16384
    FileVersion:      6.2.9200.16384 (win8_rtm.120725-1247)
    FileDescription:  Message Queuing Device Driver

You should call the MS support directly about this issue:

http://support.microsoft.com/contactus/?ln=en-us

Contacted Microsoft support, this is a known bug in Windows 8 and there is a fix in the works due sometime in August

Thanks ZZ and Andre.

• Proposed as answer by ZigZag3143xMVP, Moderator Wednesday, June 26, 2013 3:53 PM
• Marked as answer by Andre.ZieglerMicrosoft community contributor, Editor Wednesday, June 26, 2013 6:54 PM

Bubk

Thanks for the heads up on both forums.  Good Luck

ZZ

this is a known bug in Windows 8 and there is a fix in the works due sometime in August

ok. please post the KB number of the fix if possible when you get the Update in August, so that others can also install this fix.

Hey,

I'm having the same problem. Did Microsoft create this fix? What's the KB number?

Thanks,

Lindsay