Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD and stop errors


  • Please log in to reply

#1
packersdg

packersdg

    Member

  • Member
  • PipPip
  • 18 posts
I keep getting the BSOD with the following stop errors:
0x0000008E (0xC0000005, 0x8054B51A, 0xA4779394, 0x00000000)


I also just got the error:
0x0000008E (0xC0000005, 0x8054B51A, 0xA38CAB94, 0x00000000)

I have done some research and found that two of these mean:
Stop 0×0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED
and
0xC0000005 Access Violation

I, however, do not know what these mean and have very limited computer knowledge. I use windows xp. I have scanned my computer with the latest version/update of symantec (paid version) and also always have zone alarm running.
The BSOD occurs randomly when I am using my computer, ranging from using mozilla, msword (2003), itunes, using a chess program, etc...

The problem started last night, about 5-7 days after I last installed a windows update so I do not think it is that.

How do I fix this? Is it a hardware problem? Please keep in mind I am not very good with computers in your response (in terms of the language and etc.. used) but I am very good at following directions haha.

Any help is greatly appreciated!
Thanks!!

Edited by packersdg, 13 September 2009 - 03:43 AM.

  • 0

Advertisements


#2
SRX660

SRX660

    motto - Just get-er-done

  • Technician
  • 4,345 posts
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

More than likely you have installed a Microsoft update that conflicts with your hardware. This can cause a delayed reaction simply because you did not use the software until a later date than when it was installed.

If you cannot find where your updates are in the computer Nirsoft has a stand alone program called WinUpdatesList that will let you see what updates were installed and what files were changed. This utility will also let you uninstall a update if needed.

http://www.nirsoft.net/utils/wul.html

If you uninstall the last update that was installed on your computer it may start running correctly.

SRX660
  • 0

#3
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Download BlueScreenView
No installation required.
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.
  • 0

#4
packersdg

packersdg

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
==================================================
Dump File : Mini091309-07.dmp
Crash Time : 9/13/2009 7:51:33 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0x9eedbb94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091309-06.dmp
Crash Time : 9/13/2009 6:48:04 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xa7000b94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091309-05.dmp
Crash Time : 9/13/2009 5:44:54 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xa00edb94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091309-04.dmp
Crash Time : 9/13/2009 4:41:43 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xa4348b94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091309-03.dmp
Crash Time : 9/13/2009 2:25:18 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xa38cab94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091309-02.dmp
Crash Time : 9/13/2009 1:18:50 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xa4779b94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091309-01.dmp
Crash Time : 9/13/2009 12:11:54 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xa5cbcb94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091209-05.dmp
Crash Time : 9/12/2009 11:07:45 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xa8024b94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091209-04.dmp
Crash Time : 9/12/2009 10:05:21 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xaa33cb94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091209-03.dmp
Crash Time : 9/12/2009 4:30:14 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xaca05b94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091209-02.dmp
Crash Time : 9/12/2009 3:27:17 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xad426b94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================

==================================================
Dump File : Mini091209-01.dmp
Crash Time : 9/12/2009 2:07:29 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054b51a
Parameter 3 : 0xaf519b94
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7451a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
==================================================





What now?

Attached Files

  • Attached File  BSOD.txt   15.92KB   97 downloads

  • 0

#5
packersdg

packersdg

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
Also,
SRX660 I did what you said and my last windows update was 4 days before this problem began and well it worked fine for those 4 days. Does that mean that this problem is probably not related to a windows update if it worked fine for 4 days? I would rather not delete things until I know that it is most likely the source of the problem because given my knowledge and luck with computers I am afraid I will a) mess something up or b) it will create another problem haha.


Please let me know.

Thanks,
packersdg
  • 0

#6
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#7
packersdg

packersdg

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
how do I boot from it?
  • 0

#8
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
First of all....

If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

Do you have only 1 stick of RAM?
  • 0

#9
packersdg

packersdg

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
I am using a laptop and do not know. I would imagine that the physical ram test would involve me opening up my laptop which is something I would not trust myself doing haha.
  • 0

#10
packersdg

packersdg

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
and to be exact, I am using a hp pavilion dv 5000 notebook.
  • 0

Advertisements


#11
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
You can try to run memtest, but it won't be as reliable as physical test.
Create memtest CD, put it into your CD drive, restart computer.
At some point, you should see this:
Press any key to boot from CD
  • 0

#12
packersdg

packersdg

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
Sorry but the physical test is not an option for me.

I ran the memtest for 16 passes and no errors were found.

What should I try now?
  • 0

#13
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Hmmm....

Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, unfortunately, you're out of luck, because Toshiba doesn't provide any diagnostic tool.
  • 0

#14
packersdg

packersdg

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts
I have a feeling this is probably a software issue. Is there a way to detect where the software problem is and/or how to fix it?

I will try to the hard drive test, I was just thinking of other possible causes
  • 0

#15
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Judging from your dmp files, I doubt it's software problem.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP