Windows error 0x000000B8, 184

Detailed Error Information

ATTEMPTED_SWITCH_FROM_DPC[1]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0xB8: ATTEMPTED_SWITCH_FROM_DPC.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][3]
DescriptionThe default facility code.[2][3]
Error Code184 (0x00b8)

Possible solutions

3

parsing assembly code in perl

perl
parsing

Without code, my guess is that you're not escaping the dollar sign. Thus you are asking for it to match the end of the line, and then '0x28'.

In any regex, /\$0x(\p{XDigit}+)/ should capture '28' out of that string.

answered on Stack Overflow Aug 6, 2010 by Axeman
2

VirtualChannelInit stucks

c++
windows
rdp
virtual-channel

pVirtualChannelInit should be a valid pointer (to code). 0x00000004 is not, hence the access violation

Your problem may be caused by improper structure packing/alignment at compile time.

Use a debugger to figure out the correct alignment, by inspecting the memory pointed to by the PCHANNEL_ENTRY_POINTS pEntryPoints parameter passed to your VirtualChannelEntry implementation. The structure starts with 2 32 bits values, followed by 4 function pointers. The first field is a size field (value depends on bitness, 32 bits:0x0018, or 64:0x0028), the second one should be 0x00001.

Then, use #pragma pack push/pop (MSVC compiler) around the inclusion of the header defining the CHANNEL_ENTRY_POINTS structure to force the correct alignment at compile time.

answered on Stack Overflow Aug 30, 2016 by manuell • edited Aug 30, 2016 by manuell
1

parsing assembly code in perl

perl
parsing

If your input of the following format always:

instruction_address operand $stack_size,register

you can do:

$a = '0000000000033a1b subq $0x28,%rsp';
$a =~s/^.*?\$(.*?),.*$/\1/;
print $a; # prints 0x28
answered on Stack Overflow Aug 6, 2010 by codaddict
0

obexftp -l fails, return code 81

android
linux
bluetooth
obex
obexftp

After continuing to try many different things, I realized that is was more than likely the Android device having the issue. The solution is that the Android device needs to have an FTP Service running in order to utilize obexftp -l or obexfs. I achieved this by installing ES File Explorer on the Android device and selecting 'bluetooth' under the 'Network' tab. This opens an Obex FTP path on Bluetooth channel 20. The code below now functions; as well as obexfs.

obexftp -b D4:63:C6:XX:XX:XX -B 20 -U none -l
answered on Stack Overflow Jan 1, 2018 by scott

Comments

Leave a comment

(plain text only)

Sources

  1. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx
  3. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0