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

Blue Screen Error STOP: 0x0000008E


  • Please log in to reply
10 replies to this topic

#1 Peter Bennett

Peter Bennett

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:49 PM

Posted 17 December 2008 - 02:49 PM

My Dell 8300 occasionally crashes on boot. The fault is intermittant. When it happens I have to pull the power, wait a few seconds and reboot. I may even have to do this twice, before it fully boots.

Here is the error message on the Blue Screen.

STOP: 0x0000008E (0xC0000005, 0x804DA2C0, oxA645B42C, 0x00000000)

The desktop develops and half way through it crashes. As I said it's intermittant. Once it fully boots it's perfect.

I think it's clean. Latest version on Norton Internet Security, SuperAntiSpyware, Spybot and SpywareBlaster are installed, fully updated, and the machine is regularly scanned.

Any help would be much appreciated.

Thanks,

PeterB
PeterB

BC AdBot (Login to Remove)

 


#2 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:49 AM

Posted 17 December 2008 - 04:20 PM

Check your devices in Device Manager (Start > Run > type "devmgmt.msc" (without the quotes) and press Enter). Look for any "!", "?" or "X" symbols.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#3 Peter Bennett

Peter Bennett
  • Topic Starter

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:49 PM

Posted 17 December 2008 - 06:04 PM

Dear Budapest,

I've checked the Device Manager, and expanded all of the devices and I don't have any of the symbols ("!", "?" or "X" ) next to any of the devices.

Many thanks,

PeterB
PeterB

#4 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:49 AM

Posted 17 December 2008 - 06:09 PM

You might want to run through the steps given here:

http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#5 Peter Bennett

Peter Bennett
  • Topic Starter

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:49 PM

Posted 18 December 2008 - 05:22 AM

Thank you. I'll go through these instructions and report back.

PeterB
PeterB

#6 Peter Bennett

Peter Bennett
  • Topic Starter

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:49 PM

Posted 18 December 2008 - 05:44 PM

Dear Budapest,

I've followed the instructions and used the Debugging Tool. I analysied the last mini dump, which was Mini121708-01.dmp. I had many dump files! Here is the report:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini121708-01.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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Dec 17 18:53:06.937 2008 (GMT+0)
System Uptime: 0 days 0:02:05.515
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 804da2c0, a645b42c, 0}

*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : VolSnap.sys ( VolSnap!VolSnapCreate+24 )

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

1: 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: 804da2c0, The address that the exception occurred at
Arg3: a645b42c, 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
804da2c0 66f2af repne scas word ptr es:[edi]

TRAP_FRAME: a645b42c -- (.trap 0xffffffffa645b42c)
ErrCode = 00000000
eax=00000000 ebx=804da2a5 ecx=ffffffff edx=a645b4c0 esi=a645b530 edi=00000a44
eip=804da2c0 esp=a645b4a0 ebp=00000a44 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:
804da2c0 66f2af repne scas word ptr es:[edi]
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: Playlist.exe

LAST_CONTROL_TRANSFER: from 805510a2 to 804da2c0

STACK_TEXT:
a645b578 805510a2 00000000 00000020 889083f8 nt!RtlInitUnicodeString+0x1b
a645b600 804e13d9 8b4a1998 889082b0 88908414 nt!ExAllocatePoolWithTag+0x3bc
a645b658 804e13d9 8b498d20 889082b0 8b4c4710 nt!IopfCallDriver+0x31
a645b668 f7619462 8b4b3a48 804e13d9 8b4b3d80 nt!IopfCallDriver+0x31
a645b670 804e13d9 8b4b3d80 889082b0 88908438 VolSnap!VolSnapCreate+0x24
a645b680 baf9ffc1 baf9df58 8b4b3d80 889082b0 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
a645b728 804e13d9 8b4b3918 889082b0 f7ae8a1c snapman+0x17fc1
a645b7b4 804e13d9 8b481d68 889082b0 bafa7638 nt!IopfCallDriver+0x31
a645b840 804e13d9 8b4b2ee8 889082b0 889082b0 nt!IopfCallDriver+0x31
a645b850 8057bbed 8b498c50 888808e4 a645b9e8 nt!IopfCallDriver+0x31
a645b930 8056d03b 8b498c68 00000000 88880840 nt!IopParseDevice+0xa12
a645b9a8 80570358 00000000 a645b9e8 00000240 nt!ObpLookupObjectName+0x53c
a645b9fc 8057c246 00000000 00000000 84e6a800 nt!ObOpenObjectByName+0xea
a645ba78 8057c315 a645bc2c 00100080 a645bbf4 nt!IopCreateFile+0x407
a645bad4 8057c358 a645bc2c 00100080 a645bbf4 nt!IoCreateFile+0x8e
a645bb14 804dd99f a645bc2c 00100080 a645bbf4 nt!NtCreateFile+0x30
a645bb14 804e3577 a645bc2c 00100080 a645bbf4 nt!KiFastCallEntry+0xfc
a645bbb8 80595438 a645bc2c 00100080 a645bbf4 nt!ZwCreateFile+0x11
a645bc24 8059533a e5229190 a645bc6b 00000000 nt!CcPfIsVolumeMounted+0x55
a645bc60 805954d6 a645bc74 8b4b1a44 0000000c nt!CcPfOpenVolumesForPrefetch+0x7c
a645bc8c 805956a6 e5223000 00080000 8888bda0 nt!CcPfPrefetchScenario+0x5e
a645bd08 8058bea1 8888bda0 e1de7650 00000000 nt!CcPfBeginAppLaunch+0x158
a645bd50 804ec6d9 00000000 7c8106f5 00000001 nt!PspUserThreadStartup+0xeb
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
VolSnap!VolSnapCreate+24
f7619462 eb15 jmp VolSnap!VolSnapCreate+0x3b (f7619479)

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: VolSnap!VolSnapCreate+24

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: VolSnap

IMAGE_NAME: VolSnap.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 480253bc

FAILURE_BUCKET_ID: 0x8E_VolSnap!VolSnapCreate+24

BUCKET_ID: 0x8E_VolSnap!VolSnapCreate+24

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

Many thanks,

PeterB
PeterB

#7 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:49 AM

Posted 18 December 2008 - 05:53 PM

Try running the System File Checker (SFC).

How to Use SFC.EXE to Repair System Files
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#8 Peter Bennett

Peter Bennett
  • Topic Starter

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:49 PM

Posted 19 December 2008 - 10:44 AM

Dear Budapest,

I ran SFC.EXE as instructed. "Please wait while Windows verifies that all protected Windows files are intact and in their original versions". The utility found nothing amiss.

Even though nothing appeared to be changed as a result of the scan, I still ran Windows Update. The were no updated - as expected.

Regarding the post from Curios, I'd already thought of that and ran a Dell diagnostic tool that checked RAM. There is 2GB in the machine. It found nothing wrong with RAM. The scan / report showed no errors.

Regards,

PeterB
PeterB

#9 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:49 AM

Posted 19 December 2008 - 03:06 PM

Is there a Dell diagnostic test for the hard drive? If so, run that.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#10 Peter Bennett

Peter Bennett
  • Topic Starter

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:49 PM

Posted 20 December 2008 - 09:39 AM

Dear Budapest,

I ran Dell Diagnostice on the primary HD. I got no errors. Here's the report:
---------------------------------------------------------------------------------------

Primary SATA
Drive 0: ST3120026AS - Pass

Secondary SATA
Drive 0: No device

Primary IDE
Drive 0: IOMEGA ZIP 250 ATAPI - Diagnostics not supported
Drive 1: No device

Secondary IDE
Drive 0: CCR-848 - Diagnostics not supported
Drive 1: _NEC DVD+RW ND-1100A - Diagnostics not supported

Test complete, Press <ENTER> to reboot.

---------------------------------------------------------------------------------------
By the way when I switched the machine on this morning it crashed ( Blue Screen) on boot. I pulled the power, waited 10 seconds and rebooted. The machine booted as normal.

The machine has the latest BIOS A07.

After running the test I pressed <ENTER> to reboot. I had to kill the powere about 4 or 5 times. On each occasion the machine crashed and generated a blue screen. It goes through the boot sequence; the desktop develops, Norton Internet Security appears in the system tray, a USP device appears - which is an external HD, and the network icon appears. It continues to chug along and then crashes.

It booted OK on the 6th attempt. Is it something that trying to load on startup, maybe in the wrong sequence? Just a thought, but I really haven't a clue. I've attached a Spybot System Startup Report which might throw some light on the issue.

Regards,

PeterB

Attached Files


PeterB

#11 hamluis

hamluis

    Moderator


  • Moderator
  • 55,249 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:49 PM

Posted 20 December 2008 - 11:41 AM

<<FAILURE_BUCKET_ID: 0x8E_VolSnap!VolSnapCreate+24>>

One suggested approach: http://www.errorforum.com/microsoft-window...ng-boot-up.html

From what I see...I think I'd just do a repair install of XP because it's easy for me :thumbsup:.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users