	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.0

BSOD (Blue Screen of Death) 0x1000008e - How to debug?

Asked by gocomputer in Debugging Software for Development, Windows XP Operating System, General Computer Systems

Tags: BSOD, Blue Screen Of Death, 0x1000008e, Debug

Hi,

I've received two BSODs, one yesterday and one today (13th & 14th Jan 09) the error code is as follows;

0x1000008e (0xc0000005, 0x8052e797, 0xb5671750, 0x00000000) - Occured on 14th Jan
0x1000008e (0xc0000005, 0x805afee6, 0xa9615bdc, 0x00000000) - Occured on 13th Jan

When it occured for the first time yesterday I reboote my machine and my RAID 5 array said it had failed. I set the array to "REBUILD" and when I booted back into the desktop everything appeared as normal. RAID 5 array seemed fully intact with all data present. So on that basis it does not seem as if one of the drives has completely failed.

I didn't think that a hard drive failure in a RAID array would cause a BSOD. Its worthwhile mentioning that my system drive is independent to my RAID array. 1x 500gb system drive and 4x 500gb RAID 5 array.

Today the error occured again and I have no idea what the problem is. (?)

I am a novice when it comes to using Windows Debugging Tools but to the best of my ability I think I have analyzed one of the Minidump files and the output is as follows;

--- THIS ANALYSIS IS FROM THE 14th of January Mini Dump File ---

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8052e797, The address that the exception occurred at
Arg3: b5671750, Trap Frame
Arg4: 00000000

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!RtlInitUnicodeString+1b
8052e797 f266af repne scas word ptr es:[edi]

TRAP_FRAME: b5671750 -- (.trap 0xffffffffb5671750)
ErrCode = 00000000
eax=00000000 ebx=abd10e2e ecx=ffffffea edx=b56717f4 esi=0007f624 edi=0269f000
eip=8052e797 esp=b56717c4 ebp=b5671820 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!RtlInitUnicodeString+0x1b:
8052e797 f266af repne scas word ptr es:[edi]
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 8054162c to 8052e797

STACK_TEXT:
b5671820 8054162c 00000ad0 00000000 00000000 nt!RtlInitUnicodeString+0x1b
b5671820 80530023 00000ad0 00000000 00000000 nt!KiFastCallEntry+0xfc
00000000 00000000 00000000 00000000 00000000 nt!RtlIpv4StringToAddressW+0x1c3

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiFastCallEntry+fc
8054162c 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiFastCallEntry+fc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

FAILURE_BUCKET_ID: 0x8E_nt!KiFastCallEntry+fc

BUCKET_ID: 0x8E_nt!KiFastCallEntry+fc

Followup: MachineOwner

--- THIS ANALYSIS IS FROM THE 13th of January Mini Dump File ---

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 805afee6, The address that the exception occurred at
Arg3: a9615bdc, Trap Frame
Arg4: 00000000

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!MmDeleteTeb+2e
805afee6 f6472702 test byte ptr [edi+27h],2

TRAP_FRAME: a9615bdc -- (.trap 0xffffffffa9615bdc)
ErrCode = 00000000
eax=00000000 ebx=89481110 ecx=0007ffdd edx=8948113c esi=89481020 edi=00000000
eip=805afee6 esp=a9615c50 ebp=a9615c64 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MmDeleteTeb+0x2e:
805afee6 f6472702 test byte ptr [edi+27h],2 ds:0023:00000027=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: Power Article R

LAST_CONTROL_TRANSFER: from 805d2608 to 805afee6

STACK_TEXT:
a9615c64 805d2608 89481020 7ffdd000 8959d200 nt!MmDeleteTeb+0x2e
a9615d08 805d28d4 00000000 8959d200 00000000 nt!PspExitThread+0x576
a9615d28 805d2aaf 8959d200 00000000 a9615d64 nt!PspTerminateThreadByPointer+0x52
a9615d54 8054162c 00000000 00000000 0012f5d8 nt!NtTerminateProcess+0x105
a9615d54 7c90e4f4 00000000 00000000 0012f5d8 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f5d8 00000000 00000000 00000000 00000000 0x7c90e4f4

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmDeleteTeb+2e
805afee6 f6472702 test byte ptr [edi+27h],2

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MmDeleteTeb+2e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x8E_nt!MmDeleteTeb+2e

BUCKET_ID: 0x8E_nt!MmDeleteTeb+2e

Followup: MachineOwner

----

Thank you for your help.

View the Solution FREE for 30 Days

20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. jcgriff29,800
2. chris_bot...6,000
3. roman24,600
4. abel4,500
5. duncan_roe4,000
5. madprogr...4,000
7. epasquier3,000
8. emoreau2,500
8. meverest2,500
8. jkr2,500
8. ragi00172,500
8. TechSoEasy2,500
8. apresto2,500
8. doades2,500
15. nobus2,400
16. MrClyfar2,000
16. Jbamaral2,000
16. locke_a2,000
16. t0t02,000
16. Sethi2,000
16. rg202,000
16. joinaunion2,000
16. oBdA2,000
16. gtokas2,000
16. McKnife2,000
16. nsr812,000
16. Snarf00012,000
16. mwvisa12,000
16. dericstone2,000
16. TeraByte...2,000
16. p_davis2,000
16. David-Ho...2,000
16. Ray_Pas...2,000
16. EMB012,000
16. Gary_Th...2,000
16. Jones9112,000
16. oklit2,000
16. treeandrew2,000
16. hathehariken2,000
16. pcelba2,000
16. Aleksei_...2,000
16. leakim9712,000

1. jcgriff29,800
2. jkr8,500
3. chris_bot...6,000
4. roman24,600
5. abel4,500
6. Dhaest4,000
6. sunnycoder4,000
6. duncan_roe4,000
6. madprogr...4,000
10. meverest3,500
11. MrClyfar3,000
11. epasquier3,000
13. emoreau2,800
14. ragi00172,500
14. TechSoEasy2,500
14. apresto2,500
14. jgordos2,500
14. doades2,500
19. nobus2,400
20. Qlemo2,150
21. Jbamaral2,000
21. dbrunton2,000
21. locke_a2,000
21. ericpete2,000
21. t0t02,000
21. Sethi2,000
21. rg202,000
21. logudotcom2,000
21. joinaunion2,000
21. oBdA2,000
21. mrGreen2,000
21. twoboats2,000
21. basicinsti...2,000
21. johnb67672,000
21. scrathcyboy2,000
21. gtokas2,000
21. pmascari2,000
21. dampsey2,000
21. McKnife2,000
21. nsr812,000
21. mtz1of42,000
21. vadimrapp12,000
21. Snarf00012,000
21. mwvisa12,000
21. evilrix2,000
21. ororiole2,000
21. dericstone2,000
21. TeraByte...2,000
21. p_davis2,000
21. David-Ho...2,000
21. Ray_Pas...2,000
21. MrHusy2,000
21. pcsmitpra2,000
21. slam692,000
21. EMB012,000
21. Gary_Th...2,000
21. paulsolov2,000
21. Jones9112,000
21. oklit2,000
21. treeandrew2,000
21. hathehariken2,000
21. pcelba2,000
21. Aleksei_...2,000
21. leakim9712,000

BSOD (Blue Screen of Death) 0x1000008e - How to debug?

Asked by gocomputer in Debugging Software for Development, Windows XP Operating System, General Computer Systems

Tags: BSOD, Blue Screen Of Death, 0x1000008e, Debug

About this solution