Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Blue Screens galore


  • Please log in to reply

#1
ajhoude77

ajhoude77

    Member

  • Member
  • PipPip
  • 54 posts
Hi, Gang!

My computer is not doing well. I have been getting more and more frequent blue screens over the past few weeks. The codes vary, so I'm not sure what to post in that regard. Sometimes the machine won't boot at all, sometimes it can't find certain boot files, and other times it acts like nothing was wrong in the first place. The past couple days it will lock up pretty much any time I try to use a web browser. Sometimes it just stalls out for a few seconds and goes back to normal, other times it stalls out then gives me the stop screen. I had the guys over in the malware forum check it over first, and malware has been ruled out. I don't know if Windows XP is corrupted or the HDD is going bad, but I also don't really know where to start. Any suggestions?

Thanks!

P.S. Any advice someone can throw at me quickly would be appreciated (even if it's "start shopping")- I don't know how much longer the machine is going to last! :)
  • 0

Advertisements


#2
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

#3
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
I would suspect the RAM first and then hard disk issues.

To test the RAM: Download Memtest from here. Download the first option, unzip the file and burn the ISO file to a CD. For burning the CD download and install BurnCDCC from the links in my signature. It is a very simple program used only for ISO files burning. Boot the computer with the CD and let it run at least one full pass. There should not be any errors (red lines).

If the RAM test does not show anything click My Computer > right-click local disk C: > properties > tools > error checking > check now > check the two boxes > click Start. You may be asked to reboot the computer to enable the test. Please do it and let the process run. The time that the test takes (5 stages) depends on disk size and condition. Do not interrupt the test until it ends.
  • 0

#4
ajhoude77

ajhoude77

    Member

  • Topic Starter
  • Member
  • PipPip
  • 54 posts
Hi!

Thanks for taking some time to help me out. Here's the BSOD.txt stuff. I'll run those tests sometime this weekend.

BSOD.txt=========================
==================================================
Dump File : Mini091009-03.dmp
Crash Time : 9/10/2009 10:14:30 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8052d9fb
Parameter 3 : 0xba1935c4
Parameter 4 : 0x00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+6fc6
File Description : IDE/ATAPI Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091009-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini091009-02.dmp
Crash Time : 9/10/2009 8:56:36 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x80622950
Parameter 2 : 0x00622161
Parameter 3 : 0xf790acc4
Parameter 4 : 0x0000000b
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091009-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini091009-01.dmp
Crash Time : 9/10/2009 5:28:10 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x804ef14c
Parameter 2 : 0x004ef161
Parameter 3 : 0xf790acc4
Parameter 4 : 0x0000000b
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091009-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090909-04.dmp
Crash Time : 9/9/2009 2:38:52 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x804ef0bc
Parameter 2 : 0x004ef161
Parameter 3 : 0xf7906cc4
Parameter 4 : 0x0000000b
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090909-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090909-03.dmp
Crash Time : 9/9/2009 2:31:52 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x804ef0bc
Parameter 2 : 0x004ef161
Parameter 3 : 0xf7912cc4
Parameter 4 : 0x0000000b
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090909-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090909-02.dmp
Crash Time : 9/9/2009 1:08:22 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x804ef0bc
Parameter 2 : 0x004ef161
Parameter 3 : 0xf790acc4
Parameter 4 : 0x0000000b
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090909-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090909-01.dmp
Crash Time : 9/9/2009 10:49:26 AM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x804ef0bc
Parameter 2 : 0x004ef161
Parameter 3 : 0xf7902cc4
Parameter 4 : 0x0000000b
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090909-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090809-01.dmp
Crash Time : 9/8/2009 5:53:46 PM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x100000be
Parameter 1 : 0x804ef0bc
Parameter 2 : 0x004ef161
Parameter 3 : 0xf7902cc4
Parameter 4 : 0x0000000b
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090809-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090509-01.dmp
Crash Time : 9/5/2009 9:51:44 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x804da2c0
Parameter 3 : 0xf719e5c4
Parameter 4 : 0x00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+6fe1
File Description : IDE/ATAPI Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090509-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090309-03.dmp
Crash Time : 9/3/2009 10:49:22 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8052d9fb
Parameter 3 : 0xb9fad5c4
Parameter 4 : 0x00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+40f0
File Description : IDE/ATAPI Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090309-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090309-02.dmp
Crash Time : 9/3/2009 10:32:54 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8052d9fb
Parameter 3 : 0xba12f5c4
Parameter 4 : 0x00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+6fc6
File Description : IDE/ATAPI Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090309-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090309-01.dmp
Crash Time : 9/3/2009 6:36:46 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8052d9fb
Parameter 3 : 0xf714a5c4
Parameter 4 : 0x00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+6fc6
File Description : IDE/ATAPI Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090309-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090209-02.dmp
Crash Time : 9/2/2009 3:21:58 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8052d9fb
Parameter 3 : 0xeb3725c4
Parameter 4 : 0x00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+6fc6
File Description : IDE/ATAPI Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090209-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090209-01.dmp
Crash Time : 9/2/2009 2:15:22 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8052d9fb
Parameter 3 : 0xba0655c4
Parameter 4 : 0x00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+6fc6
File Description : IDE/ATAPI Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090209-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini101608-01.dmp
Crash Time : 10/16/2008 8:05:26 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x82328da8
Parameter 2 : 0x84f95be8
Parameter 3 : 0xf78eacbc
Parameter 4 : 0x00000001
Caused By Driver : ati2mtag.sys
Caused By Address : ati2mtag.sys+5e418
File Description : ATI Radeon WindowsNT Miniport Driver
Product Name : ATI Radeon WindowsNT Miniport Driver
Company : ATI Technologies Inc.
File Version : 6.14.10.6755
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101608-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini031308-01.dmp
Crash Time : 3/13/2008 5:30:08 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0xe2e96f20
Parameter 3 : 0xe2e97560
Parameter 4 : 0x0cc80005
Caused By Driver : VIDEOPRT.SYS
Caused By Address : VIDEOPRT.SYS+1b3e
File Description : Video Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini031308-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini010908-01.dmp
Crash Time : 1/9/2008 12:39:54 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0x80000003
Parameter 2 : 0xee65f55a
Parameter 3 : 0xbaab4ed0
Parameter 4 : 0x00000000
Caused By Driver : RtkHDAud.sys
Caused By Address : RtkHDAud.sys+6655b
File Description : Realtek® High Definition Audio Function Driver
Product Name : Realtek® High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)
Company : Realtek Semiconductor Corp.
File Version : 5.10.00.5273 built by: WinDDK
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini010908-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini121307-01.dmp
Crash Time : 12/13/2007 9:45:46 AM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x85034bc8
Parameter 2 : 0x84eb8230
Parameter 3 : 0xf78eecbc
Parameter 4 : 0x00000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+8f4f
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121307-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100207-01.dmp
Crash Time : 10/2/2007 11:55:34 AM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x84e9dda8
Parameter 2 : 0x851bd738
Parameter 3 : 0xf78f6cbc
Parameter 4 : 0x00000001
Caused By Driver : ati2mtag.sys
Caused By Address : ati2mtag.sys+5e418
File Description : ATI Radeon WindowsNT Miniport Driver
Product Name : ATI Radeon WindowsNT Miniport Driver
Company : ATI Technologies Inc.
File Version : 6.14.10.6755
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini100207-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini083007-02.dmp
Crash Time : 8/30/2007 4:25:22 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x852adda8
Parameter 2 : 0x851ad358
Parameter 3 : 0xf78facbc
Parameter 4 : 0x00000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+8f4f
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini083007-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini083007-01.dmp
Crash Time : 8/30/2007 4:21:30 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x824c7020
Parameter 2 : 0x85092840
Parameter 3 : 0x851fbbb8
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+19a19
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini083007-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================
  • 0

#5
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
The problem here is, that the latest error listed is from September of last year, so not much of a use.

Make sure, your settings are correct...

1. Click Start, point to Settings, and then click Control Panel (Start>Control Panel in Vista).
2. Double-click System.
3. Click (Advanced system settings link in Vista, then --->)the Advanced tab, and then click Settings under Startup and Recovery.
4. Make sure, there is a checkmark in Write an event to the system log.
5. In the Write debugging information list, click Small memory dump (64k) (128K in Windows 7).
  • 0

#6
ajhoude77

ajhoude77

    Member

  • Topic Starter
  • Member
  • PipPip
  • 54 posts
Yeah, I noticed that there weren't any recent crash reports. I was going to ask if that was unusual, but I wasn't sure I'd have enough time to type it out before it crashed again! :) I'm working on my wife's computer now. :)

I tried to run memtest, but it's stopping after a few seconds. It gets to 1% complete and about 90% on the next test section and says "an unexpected error occurred, stopping CPU0" or something like that. It dumps out a bunch of codes all over the bottom of the screen, etc. I ran it several times with the same result, except sometimes the entire machine refuses to boot at all. I don't know if that's related to bad RAM or what, but here's what happens. I start it, the post screen comes up, then the speaker beeps twice and shows an error screen. Since I don't really know what I'm looking at, I don't know what would be important on that screen. I did see a message about a fixed disk error on there, and the HDD name gets all garbled looking with a lot of apostrophes in it. I can go to the setup from that error screen, and in the boot menu only the garbled HDD name shows up, no CD drive or anything else. When it boots normally and I enter the setup, the HDD name is normal and the CD drive shows up like it's supposed to.

New RAM sounds like the first step, anyway. If you agree, I'll get some and post back here when I get it installed.

Thanks!
  • 0

#7
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
Your descriptions indicate to a faulty RAM or to something even more severe, like faulty CPU or motherboard. There is still a chance that the hard drive is faulty. The cheapest way to find out is to replace the RAM and hope for the best.

Before repacing the RAM however, please reset the BIOS. This is done by disconnecting the power cord and taking the CMOS battery out for 10 minutes. After reinstallation you will probably get a checksome error which will not show again after settint time and date in the BIOS.

Edited by The Skeptic, 04 July 2010 - 09:44 AM.

  • 0

#8
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
I assume, you're running memtest from bootable CD?
  • 0

#9
ajhoude77

ajhoude77

    Member

  • Topic Starter
  • Member
  • PipPip
  • 54 posts
Yes, I ran memtest from the bootable CD, at least when it would boot past the post. I'll get some new memory and see what happens. I won't be devastated if this thing can't be salvaged easily. One of the mouse keys broke and the power cable doesn't connect all that well anymore. It's getting pretty tired overall, and it was a hand-me-down from my wife after she got her new Dell. :) Having to shop around for something new wouldn't be ALL bad. :)

Thanks for the help guys- I'll post back here in a few days after the RAM arrives.
  • 0

#10
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
From your description, I doubt, we're dealing here with bad RAM, but since you already ordered it....
The Skeptic may be right:

Your descriptions indicate [...] or to something even more severe, like faulty CPU or motherboard


  • 0

#11
ajhoude77

ajhoude77

    Member

  • Topic Starter
  • Member
  • PipPip
  • 54 posts
I haven't ordered anything yet, so let me know if I should try something else before I do.

Thanks!
  • 0

#12
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
If we're dealing here with CPU, or mobo issues (very possible), there is really not much, we can do here.
  • 0

#13
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
A professional lab would have replacement RAM modules and CPUs which allow it to replace components and diagnose a problem by trial and error. Obviously you don't have these.

There are few options available to you:

1: Take a RAM module of the same type from a working computer and place it in the broken one. This will tell you if the problem is with the RAM or not.
2: Buy a new module and risk losing your money if the problem is not with the RAM. RAM modules are not expensive (compared to other components). If the new component fail then your problem is either with the CPU or motherboard. To judge which of the two, you must replace the CPU and if the computer fails after RAM and CPU replacement then the problem is probably with the motherboard.
3: Take the computer to a professional lab, let them diagnose it for you and then make a decision of how you want to proceed.

There are really no shortcuts. Had I been in your position I would buy new RAM. The reason is that it's the cheapest item and the one that fails much more often.
  • 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