Windows 8 BSOD when getting messages from a message queue that is located on a network computer

Here's the info I get from WinDbg, I hope someone out there can interpret this for me and or point in the right direction

Thank you
Kent
Microsoft (R) Windows debug 6.2.9200.20512 AMD64 Version
Copyright (c) Microsoft Corporation. All rights reserved.
Loading dump file [C:\Windows\MEMORY. DMP]
The Bitmap core dump file: the single kernel address space is available
Symbol search path is: srv * c:\cache* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) free x 64
Product: WinNt, suite: TerminalServer SingleUserTS
By: 9200.16581.amd64fre.win8_gdr.130410 - 1505
Computer name:
Core = 0xfffff802 'e4872000 PsLoadedModuleList = 0xfffff802' e4b3ea20
The debugging session: 15:52:59.484 Thu June 20, 2013 (UTC - 05:00)
System Uptime: 0 days 0:01:57.136
Loading the kernel symbols
...............................................................
................................................................
.................................
Loading user symbols
PEB is paginated on (Peb.Ldr = 000007f7'62ddb018).  Type ".hh dbgerr001" for more details
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************
Use! analyze - v to obtain detailed debugging information.
Verification of error CF, {7fa328240e0, 7ae000011b0c9025, fffff880172d85e0, 80000005}
Probably caused by: mqac.sys (mqac! ACCreateQueue + a77)
Follow-up: MachineOwner
---------
4: kd >
! analyze - v
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (CF)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and usually the current instruction pointer).
When possible, the name of the guilty driver (Unicode string) is printed on
verification error screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 000007fa328240e0, virtual address for the execute attempted.
Arg2: 7ae000011b0c9025, content PTE.
Arg3: fffff880172d85e0, (reserved)
Arg4: 0000000080000005, (reserved)
Debugging information:
------------------
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0XFC
Nom_processus: mqsvc.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880172d85e0-(.trap 0xfffff880172d85e0)
NOTE: The frame trap does contain not all registers.
Some registry values can be set to zero or incorrect.
Rax = 000007fa327fc950 rbx = 0000000000000000 rcx = 00000058b03dad90
RDX = 00000058b17aeb68 rsi = 0000000000000000 rdi = 0000000000000000
RIP = 000007fa328240e0 rsp = fffff880172d8778 rbp = fffff880172d8b80
R8 = fffffa8011f63940 r9 = 0000000000000521 r10 = fffffa8013129dd0
R11 = 0000000000000006 r12 = 0000000000000000 r13 = 0000000000000000
R14 = 0000000000000000 r15 = 0000000000000000
iopl = 0 nv up ei pl nz na po nc
000007fa'328240e0?              ???
Reset the default scope
LAST_CONTROL_TRANSFER: from fffff802e4a5dfe9 to fffff802e48cc440
STACK_TEXT:
"" fffff880 ' 172 8408 fffff802 d ' e4a5dfe9: 00000000 ' 000000 fc 000007fa '328240e0 7ae00001' 1b0c9025 fffff880 ' 172d85e0: nt! KeBugCheckEx
"fffff880 ' 172 d 8410 fffff802 ' e4984d9c: fffff880'172d85e0 ffffd6fb 'da821cdc fffffa80' 13129dd0 00000000' 00000000: nt! : FNODOBFM: 'string' + 0x344b5
"fffff880 ' 172 8450 fffff802 d ' e490695d: fffff880 172 d 8500 00000000' c0000016 fffffa80 '1221d5c0 fffffa80' 11f63940: nt! : FNODOBFM: 'string' + 0x3440d
fffff880 '172d84a0 fffff802' e48c9eee: fffff880 00000000'00000008 00000000'00000000 00000000'00000000 ' 172d85e0: nt! MmAccessFault + 0x3ed
fffff880 '172d85e0 000007fa' 328240e0: fffff880 '04e21297 fffffa80' 13129da0 00000000 00000000' fffff8a0'03707800: nt! KiPageFault + 0x16e
"fffff880 ' 172 d 8778 fffff880 ' 04e21297: fffffa80'13129da0 00000000 00000000' fffff8a0 ' 03707800 fffff980' 00000000: 0x000007fa'328240e0
"fffff880 ' 172 d 8780 fffff880 ' 04e220d7: 00000000'00000000 00000058' 00000000'00000000 00000000'00000000 b17aeb68: mqac! ACCreateQueue + 0xa77
fffff880 '172d87f0 fffff802' e4ca16c7: fffffa80 '120a3ad0 fffffa80' 12ab8560 00000000'00000521 00000000'00000000: mqac! ACDeviceControl + 0x62b
"fffff880 ' 172 8890 fffff802 d ' e4cb68a6: 00000000'00000000 00000000'00000080 00000000'00000000 00000000'00000000: nt! IopXxxControlFile + 0x7e5
fffff880 '172d8a20 fffff802' e48cb453: fffff880'172d8ad8 00000000'00000000 00000000'00000001 00000000'00000000: nt! NtDeviceIoControlFile + 0 x 56
fffff880 '172d8a90 000007fa' 3ec52c5a: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt
! KiSystemServiceCopyEnd + 0x13
00000058' b17aeb08 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x000007fa'3ec52c5a
STACK_COMMAND: kb
FOLLOWUP_IP:
Mqac! ACCreateQueue + a77
fffff880'04e21297 85 c 0 test eax, eax
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: mqac
! ACCreateQueue + a77
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: mqac
Nom_image: mqac.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5010abc2
BUCKET_ID_FUNC_OFFSET: a77
FAILURE_BUCKET_ID: 0xFC_mqac! ACCreateQueue
BUCKET_ID: 0xFC_mqac! ACCreateQueue
Follow-up: MachineOwner
---------

I contacted Microsoft and this is a known bug in Windows 8, there is that a current fix should be available in August 2013

Thank you zz and Linney

Tags: Windows

Similar Questions

Maybe you are looking for