Windows XPPost your Windows XP related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
A year ago I put together a computer from parts off newegg. I would get the occasional BSOD, but recently they've really picked up and it has become a real pain. I've generated two memory dumps. I'll post both dumps below.
Last edited by nsmithy; 6th January 2007 at 03:32.
Didn't find the information you thought to find? Check out these Similar Threads
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri Jan 5 09:40:11.968 2007 (GMT-5)
System Uptime: 0 days 6:02:57.563
WARNING: Process directory table base 0AF80720 doesn't match CR3 002F5000
WARNING: Process directory table base 0AF80720 doesn't match CR3 002F5000
Loading Kernel Symbols
........................................................................... ........................................................................
Loading User Symbols
................................................
Loading unloaded module list
...................................
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {4, 80545ff0, b2000000, 70f0f}
Probably caused by : usbehci.sys ( usbehci!EHCI_HardwarePresent+12 )
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000004
Arg2: 80545ff0
Arg3: b2000000
Arg4: 00070f0f
Debugging Details:
------------------
NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.
This error is documented in the following publication:
- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:
MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111
VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.
UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.
EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.
PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.
BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL
This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.
#2:
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri Jan 5 11:54:01.562 2007 (GMT-5)
System Uptime: 0 days 2:09:23.127
WARNING: Process directory table base 0ADC03E0 doesn't match CR3 002F5000
WARNING: Process directory table base 0ADC03E0 doesn't match CR3 002F5000
Loading Kernel Symbols
........................................................................... ......................................................................
Loading User Symbols
......................
Loading unloaded module list
.............
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {4, 80545ff0, b2000000, 70f0f}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ati2cqag.dll -
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
Probably caused by : ati2cqag.dll ( ati2cqag!CMMQS_GetProcAddress+62f7 )
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000004
Arg2: 80545ff0
Arg3: b2000000
Arg4: 00070f0f
Debugging Details:
------------------
NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.
This error is documented in the following publication:
- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:
MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111
VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.
UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.
EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.
PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.
BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL
This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session
TargetInfo::ReadBusData is not available in the current debug session