Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD Sto error 0x0000008E


  • Please log in to reply
3 replies to this topic

#1 kded

kded

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:38 AM

Posted 01 June 2010 - 01:52 PM

My father in laws computer gets the BSOD after about ten minutes each time he turns it on. I have tried safe mode and it still does it. I even left it waiting to be looged on and it still does it. After restoring system to a previous point it still does it. I have debugged it and will post the file. It is a Toshiba Satellite P205D-S7454. It occured without any updates or downloads. Vista is the OS.

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [I:\Mini060110-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x83803000 PsLoadedModuleList = 0x8391ac70
Debug session time: Tue Jun 1 10:49:02.288 2010 (UTC - 7:00)
System Uptime: 0 days 0:10:55.284
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.........
Unable to load image \??\C:\Windows\system32\NTDOSI412.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NTDOSI412.SYS
*** ERROR: Module load completed but symbols could not be loaded for NTDOSI412.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 838ac092, 8a4a09cc, 0}

Probably caused by : hardware ( NTDOSI412+118b )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* 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: 838ac092, The address that the exception occurred at
Arg3: 8a4a09cc, 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!memcpy+72
838ac092 8a06 mov al,byte ptr [esi]

TRAP_FRAME: 8a4a09cc -- (.trap 0xffffffff8a4a09cc)
ErrCode = 00000000
eax=00000001 ebx=88af09e1 ecx=00001733 edx=00000003 esi=00000000 edi=87664a21
eip=838ac092 esp=8a4a0a40 ebp=8a4a0a48 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!memcpy+0x72:
838ac092 8a06 mov al,byte ptr [esi] ds:0023:00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: fixmapik.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!memcpy+72
838ac092 8a06 mov al,byte ptr [esi]

LAST_CONTROL_TRANSFER: from 83fca18b to 838ac092

STACK_TEXT:
8a4a0a48 83fca18b 87664a21 00000000 00001736 nt!memcpy+0x72
WARNING: Stack unwind information not available. Following frames may be wrong.
8a4a0a5c 83fcaf49 87664a21 00000000 00001736 NTDOSI412+0x118b
8a4a0a78 83fcb7cd 88af0a09 8765c000 876649bd NTDOSI412+0x1f49
8a4a0a94 83fcb906 00000000 8765c000 83fcaee2 NTDOSI412+0x27cd
8a4a0ab4 83fcb7cd 88af09bd 8765c000 87664999 NTDOSI412+0x2906
8a4a0ad0 83fcb8f6 00000000 8765c000 83fcb8c0 NTDOSI412+0x27cd
8a4a0af0 83fcb7cd 88af0999 8765c000 8765c078 NTDOSI412+0x28f6
8a4a0b0c 83fcb8f6 00000001 8765c000 83fcb8c0 NTDOSI412+0x27cd
8a4a0b2c 83fcb7cd 88ae8078 8765c000 8765c054 NTDOSI412+0x28f6
8a4a0b48 83fcb8f6 00000000 8765c000 83fcb8c0 NTDOSI412+0x27cd
8a4a0b68 83fcb7cd 88ae8054 8765c000 8765c010 NTDOSI412+0x28f6
8a4a0b84 83fcb8f6 00000000 8765c000 83fcb8c0 NTDOSI412+0x27cd
8a4a0ba4 83fcbd52 88ae8010 8765c000 8765c000 NTDOSI412+0x28f6
8a4a0bb8 83fcc1ec 88ae8008 8765c000 0000000e NTDOSI412+0x2d52
8a4a0bd4 83fcc986 8762101c 00000003 87621044 NTDOSI412+0x31ec
8a4a0bf0 83fccaa8 8762101c 00000003 87621044 NTDOSI412+0x3986
8a4a0c0c 83fccb52 88a40388 86515008 86515078 NTDOSI412+0x3aa8
8a4a0c2c 838479c6 88a40388 86515008 86515008 NTDOSI412+0x3b52
8a4a0c44 83a49761 938bda40 86515008 86515078 nt!IofCallDriver+0x63
8a4a0c64 83a49f06 88a40388 938bda40 027ff300 nt!IopSynchronousServiceTail+0x1d9
8a4a0d00 83a4afd0 88a40388 86515008 00000000 nt!IopXxxControlFile+0x6b7
8a4a0d34 8384dc7a 000000a0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
8a4a0d34 772b5e74 000000a0 00000000 00000000 nt!KiFastCallEntry+0x12a
027ff1b8 00000000 00000000 00000000 00000000 0x772b5e74


STACK_COMMAND: kb

FOLLOWUP_IP:
NTDOSI412+118b
83fca18b ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NTDOSI412+118b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* 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: 838ac092, The address that the exception occurred at
Arg3: 8a4a09cc, 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!memcpy+72
838ac092 8a06 mov al,byte ptr [esi]

TRAP_FRAME: 8a4a09cc -- (.trap 0xffffffff8a4a09cc)
ErrCode = 00000000
eax=00000001 ebx=88af09e1 ecx=00001733 edx=00000003 esi=00000000 edi=87664a21
eip=838ac092 esp=8a4a0a40 ebp=8a4a0a48 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!memcpy+0x72:
838ac092 8a06 mov al,byte ptr [esi] ds:0023:00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: fixmapik.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!memcpy+72
838ac092 8a06 mov al,byte ptr [esi]

LAST_CONTROL_TRANSFER: from 83fca18b to 838ac092

STACK_TEXT:
8a4a0a48 83fca18b 87664a21 00000000 00001736 nt!memcpy+0x72
WARNING: Stack unwind information not available. Following frames may be wrong.
8a4a0a5c 83fcaf49 87664a21 00000000 00001736 NTDOSI412+0x118b
8a4a0a78 83fcb7cd 88af0a09 8765c000 876649bd NTDOSI412+0x1f49
8a4a0a94 83fcb906 00000000 8765c000 83fcaee2 NTDOSI412+0x27cd
8a4a0ab4 83fcb7cd 88af09bd 8765c000 87664999 NTDOSI412+0x2906
8a4a0ad0 83fcb8f6 00000000 8765c000 83fcb8c0 NTDOSI412+0x27cd
8a4a0af0 83fcb7cd 88af0999 8765c000 8765c078 NTDOSI412+0x28f6
8a4a0b0c 83fcb8f6 00000001 8765c000 83fcb8c0 NTDOSI412+0x27cd
8a4a0b2c 83fcb7cd 88ae8078 8765c000 8765c054 NTDOSI412+0x28f6
8a4a0b48 83fcb8f6 00000000 8765c000 83fcb8c0 NTDOSI412+0x27cd
8a4a0b68 83fcb7cd 88ae8054 8765c000 8765c010 NTDOSI412+0x28f6
8a4a0b84 83fcb8f6 00000000 8765c000 83fcb8c0 NTDOSI412+0x27cd
8a4a0ba4 83fcbd52 88ae8010 8765c000 8765c000 NTDOSI412+0x28f6
8a4a0bb8 83fcc1ec 88ae8008 8765c000 0000000e NTDOSI412+0x2d52
8a4a0bd4 83fcc986 8762101c 00000003 87621044 NTDOSI412+0x31ec
8a4a0bf0 83fccaa8 8762101c 00000003 87621044 NTDOSI412+0x3986
8a4a0c0c 83fccb52 88a40388 86515008 86515078 NTDOSI412+0x3aa8
8a4a0c2c 838479c6 88a40388 86515008 86515008 NTDOSI412+0x3b52
8a4a0c44 83a49761 938bda40 86515008 86515078 nt!IofCallDriver+0x63
8a4a0c64 83a49f06 88a40388 938bda40 027ff300 nt!IopSynchronousServiceTail+0x1d9
8a4a0d00 83a4afd0 88a40388 86515008 00000000 nt!IopXxxControlFile+0x6b7
8a4a0d34 8384dc7a 000000a0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
8a4a0d34 772b5e74 000000a0 00000000 00000000 nt!KiFastCallEntry+0x12a
027ff1b8 00000000 00000000 00000000 00000000 0x772b5e74


STACK_COMMAND: kb

FOLLOWUP_IP:
NTDOSI412+118b
83fca18b ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NTDOSI412+118b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner


Thanks for any help I can get

Hes301

BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:38 AM

Posted 01 June 2010 - 08:16 PM

Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

 


#3 kded

kded
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:38 AM

Posted 05 June 2010 - 11:12 AM

I ran this and it show the same program on all the dumps. I found the program, not using it, and unistalled and now it is running great. Thanks so much.

#4 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:38 AM

Posted 05 June 2010 - 11:16 AM

You're welcome :huh:
What program was it, if I may?

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users