Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1870
  • Last Modified:

PC locking up, sometimes during boot, sometimes later

Greetings.

I have a desktop that has been running well for a couple years. It's a generic. The CD that was shipped with it is labeled "SystemBoard PC133". It has IDE drivers, VGA drivers, sound drivers, LAN drivers, etc. These things are all built into the MOBO. The MOBO itself has a heatsink in the middle of it that says PC400. The MOBO includes a pair of USB ports, but I seem to recall they were USB1.1. The keyboard is standard. The mouse is a Microsoft optical mouse, plugged into the mouse port using the USB adapter that came with the mouse.

The box is set up as a dual-boot, with Windows XP Professional and RedHat 8. The XP is on the main hard drive and Linux is on a second drive, which also contains a large partition shared by both operating systems. There is also a CD drive and a CD burner.

The box has had a modem card in it (never used) and a USB 2.0 card in one of the PCI slots. The "inside" connection there links off to a four-port hub accessible from the front of the box.

There has been an HP610C printer connected to the parallel port on the back for as long as I've had the computer (more or less). Recently (about two weeks ago) I purchased a Samsung ML-1740 printer that I was connecting to this computer via USB. It was most recently plugged into one of the built-in USB ports (off the motherboard).

Thursday evening, the computer decided to lock up while in use (running under Windows). Everything just froze, and Ctrl-Alt-Del was useless. On power-down reboot, it locked up during reboot.

Friday I tried booting and got the following blue screen:

==== BEGIN BLUE SCREEN TEXT ====
A problem has been detected and Windows has been shut down to prevent damaga
to your computer

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use Safe Mode to remove disabled components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical information:
*** STOP: 0x000000D1 (ox00000000, 0x0000000d, 0x00000001, 0xF77X43F7)
*** atapi.sys - Address F77643F7 base at F7762000, DateStamp 3b7d83e5
===== END BLUE SCREEN TEXT =====

I unplugged the printer's USB line, it then booted normally, and I didn't think much more about it. Until it locked up Saturday morning.

I didn't have time to troubleshoot it Saturday. Today I've been racking my brain.

Neither printer is connected. I've pulled out the modem and the USB card. I've disabled the USB support on the MOBO from the BIOS. I've disconnected the CD drives. (They're currently back in the mix.) I've moved my one stick of RAM to the other slot.

It doesn't matter what I do; if I try to boot into Windows I get a message that Windows didn't boot properly, with a menu to boot normally, boot last successful, or boot safe mode. None of these will boot. It will get partway through the boot and start over. Or it will get part way through the boot and hang.

My first inclination is to blame Windows, but Linux is no better here. It boots to the point where I log into Gnome, but after I enter my password before it gives me a desktop, it locks up. Powering down is the only escape. On one such attempt, I got the following screen:

==== BEGIN LINUX ERROR SCREEN TEXT ====
Unable to handle kernel NULL pointer dereference at virtual address 00000000
*pde = 00000000
Oops: 0000
mousedev keybdev hid input ehci-hcd usb-ohci usbcore ext3 jbd
CPU:    0
EIP:    0010: [<00000000>] Not tainted
EFLAGS: 00010046

EIP is at [unresolved] (2.4.18-14)
eax: c137b8e0  ebx: cfed3a20  ecx: c1690d30  edx: ffffffff
esi: c231fe60  edi: 00000000  ebp: 00000001  esp: 40347ecc
ds: 0018  es: 0018  ss: 0018
Process (pid: 0, stackpage=40347000
Stack: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
       00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
       00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Call Trace:

Code: Bad EIP value.
 <0>Kernel panic: Aiee, killing interrupt handler!
 In interrupt handler - not syncing
===== END LINUX ERROR SCREEN TEXT =====

The kicker here is, I can boot from the Windows XP install CD with no problem. But once there, I can't do much. I've tried going into the Recovery Console so I could try to back up files from the "My Documents" directories to the second hard drive, but it doesn't allow me to do that.

Any idea what I should be trying next here?

Thanks.
0
BarryTice
Asked:
BarryTice
  • 10
  • 6
  • 5
  • +3
2 Solutions
 
yehudiCommented:
Hi BarryTice,

Can you still boot in safe mode?

Good Luck!
0
 
cpc2004Commented:
As the problem occurs at Windows and Liux. Most likely it is caused by faulty ram.  Reseat the memory stick to another memory slot.  If it still fails and you have two memory sticks, take out one of the memory stick. Maybe one of the memory stick is faulty.  If you have only one memory stick, borrow one memory stick from your friends if they have spare.
0
 
cpc2004Commented:
STOP: 0x000000D1 (ox00000000, 0x0000000d, 0x00000001, 0xF77X43F7)
The second bugcheck parameter0x0000000d is the hardware device interrupt and it only fails  unless it is hardware error.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
BarryTiceAuthor Commented:
yehudi --

When I try to boot Windows into Safe Mode, it gets as far as Mup.sys and quits.

cpc2004 --

I have only one stick of RAM. I have already tried swapping it over to the other memory slot, and noticed no change. I fear I'll be purchasing new RAM at this rate, but have no guarantee it will help.

What confuses me about this is that it boots fine from the Windows CD. Does the CD boot make use of only the 640K (or whatever it is) that comes standard on the MOBO? With a DOS-like interface, that would make sense.

Thanks for checking in!

-- b.r.t.
0
 
yehudiCommented:
It may be faulty RAM, but I think you would be well advised to fully check out the possibility of a corrupted Hard Drive first.

Tha fact that it will boot from the CDROM sounds encouraging to me.

Did you they doing a repair using the CDROM?  (As I recall, it offers to do a repair twice... the first time, you say no, and say yes the second time.)

Try doing a secondary install to a different directory eg: c:\wXP - or even better, to a different partition if you have one available: D:\Windows

If this works, you will be able to see your Hard Drive, and work out what the problem is.  And probably do what ever disk repairs are needed.

If it does not work - you have lost nothing but a little time.
0
 
BarryTiceAuthor Commented:
yehudi --

It appears to not be faulty RAM. I have swapped RAM in from a different computer (two sticks of 128 MB each rather than the normal 1 stick of 512 MB) and gave the same symptoms.

I have not yet tried repairing using the CD rom because it asks me to insert some floppy disk

The first drive in this box is a 40 GB divided into two 20GB partitions. The first of these partitions has Windows XP on it, and the second has data files.

The second hard drive is a 120 GB with an 80 GB partition available as file space to both Windows and Linux. The remaining 40 GB contains the three Linux partitions (bioot, swap, and main).

Given that Linux is running from the second drive, and that Linux is also not running, that makes me less confident that it may be the hard drive.

I've disabled the modem and NIC on the MOBO, but get the same results. I'll try seeing if I can find some "fix" option on the Windows CD next.

Thanks.

-- b.r.t.
0
 
cpc2004Commented:
The hardware problem may be the cache memory at CPU or M/B.
0
 
BarryTiceAuthor Commented:
OK. I've run the Windows repair, and it didn't help. It booted to a point where it was offering me the opportunity to select how things would be reconfigured. (It said something about the "new look," but when I was about to read it a visiting friend's dog attacked one of my dogs in the next room and I had to run and stop my wife from screaming.)

By the time I got back to the computer, it was rebooting itself again, and part way through that reboot, it rebooted, and part way through that reboot, it rebooted.

So I've now tried rebooting the Linux. It (again) gets to the point where it lets me enter my login and password, but before it ever gives me a Gnome desktop (all I have is the wallpaper), it stops doing anything.

With the Linux, I still have mouse pointer control. I can move the pointer around the screen, though there is nothing to select or click on. Right-clicking has no function either. On the rare occassion I get far enough in Windows to see a mouse pointer, when it locks up the mouse is also dead.

Any thoughts?

-- b.r.t.
0
 
BarryTiceAuthor Commented:
For what it's worth, the BIOS screens say
AMIBIOS SIMPLE SETUP UTILITY - VERSION 1.21.10
(C)2000 American Megatrends, Inc. All Rights Reserved.

It's gotten now to the point where, on Windows boot, it gets about to the Windos splash screen when it briefly flashes a blue screen of death (about 1/4 second, maybe less) before rebooting.
0
 
BarryTiceAuthor Commented:
I've tried an XP install on the second partition of the first hard drive (the drive that already had XP on it). It made it to the same Windows XP "An exciting new look" screen before locking up.

Down the left are five options: "Collecting information", "Dynamic Update", "Preparing installation", Installing Windows", and "Finalizing installation" with images that look like radio buttons to their left. The first three are "selected" (with a green center). The fourth option is in red text. Below them all is the notice "Setup will complete in approximately: 39 minutes" and that time is not changing. There is an unresponsive mouse pointer in the center of the screen, and no seeking noises are coming from the hard drive.

(Sigh.) This isn't looking good.

-- b.r.t.

p.s. Also, at this point I've re-enabled the USB ports and NIC from the BIOS, and reinstalled the modem and USB 2.0 cards.
0
 
nobusCommented:
some things that can help or assist you :

-memory test memtest86+ from     http://www.memtest.org/      
-set your PC NOT to reboot on BSOD : in device manager>advanced tab, click settings in the restart and repair settings section; then uncheck the restart PC automatic in the sytem errors section
-since the error points to atapi.sys, you can test with all cd drives disconnected. if this does not help, i recommend starting with a minimal config :
mobo+cpu, 1 ram stick, 1disk drive, video card, kbd and mouse. This should point you in the right direction

0.
0
 
BarryTiceAuthor Commented:
nobus --

Thanks for the suggestions.

I have downloaded the memtest86+ zip files on another computer and put them to a floppy accordingly. But when I boot that floppy in the afflicted machine, all I get is a series of:
1001
1001
1001
1001
1001
1001
1001
1001
1001
1001

down the left side of the screen. I cannot use the afflicted machine to create the floppy, because the afflicted machine will not boot.

I cannot set the afflicted PC to not reboot on BSOD because I cannot get into the device manager because I cannot get the box to boot.

I have tried this with all CD drives disconnected and it made no difference. I only have 1 RAM stick in (though I have tried it with two smaller sticks from a different box instead). The video card is built into the MOBO. I cannot disconnect the second hard drive because the system is dual-boot, with WinXP on the first drive and Linux on the second, and the GRUB bootloader doesn't seem to play nicely with either drive gone.

Thanks for any additional assistance you may be able to provide!

-- b.r.t.
0
 
nobusCommented:
i would try booting without a disk connected, or with only a cd drive connected (you can put a bootable cd in to test the bootup)
you can also try to test the memory on another PC, if it is compatible, and the other devices, to narrow down the problem.
or you can try one of these :

http://www.recoverybios.com/                              replace bios
http://www.badflash.com/                                 "          "
http://www.amptron.com/documents/Recover.pdf                  recover BIOS
http://www.unicore.com/                              Bios upgrade
0
 
BarryTiceAuthor Commented:
nobus --

Someone on the memtest86+ forum suggested trying a different floppy, and that seemed to work. (Go figure.)

The Memtest is running on the computer now. It's completed 80 passes so far with no errors.

The only CDs I have that automatically boot are my Windows install and some Linux install images I have. I already know that it seems to run fine from the Windows install disk, though that only exercises the computer in DOS/green-screen mode.

I'd track down one of those Linux installations that you can run from a CD, but the only CD burner I have is in the machine I can't get to boot. (Sigh.)

I'll see if the bios links above do me any good.

Thanks.

-- b.r.t.
0
 
nobusCommented:
try it again, it could be your floppy that causes the problems...
0
 
BarryTiceAuthor Commented:
Gah!

I've got this up on a laptop next to where I'm working, and I looked over and saw BSOD on the laptop, too. I was about to panic, thinking I had real problems, when I remembered it's a Linux laptop and the BSOD is a screensaver.

That's not the best thing for an old man's heart...
0
 
nobusCommented:
>>  That's not the best thing for an old man's heart   <<  then use some whisky to kick it into gear again....
0
 
BarryTiceAuthor Commented:
I've tried it with the CDs and floppy disconnected. Same result. It boots  up to about where you see the Windows splash screen, then it reboots (GOTO 10).

So next I reconnected the CDs and floppy and booted the Linux (Fedora Core 1) install CD I have, thinking it would exercise the machine harder than the Windows install seems to.

On first boot, I got as far as:
trying to remount root filesystem read write... done
mounting /tmp as remfs... done
running install...
running /sbin/loader
install exited abnormally -- received signal 11
sending termination signals...done
sending kill signals...done
disabling swap...
unmounting filesystems...
           /proc done
           /dev/pts done
           /temp/ramfs done
you may safely reboot your system

So, I rebooted the system. This time it made it past that, to where it asks if I want to tes t the CD media. I chose not to, and had the Welcome to Fedora core text on the screen. The bottom of the screen showed:
Running anaconda, the Fedora Core system installer - please wait...

when things blew up. The screen ended up with:
Running anaconda, the Fedora Core system installer - please wait...
Traceback (most recent call last):
  File "/usr/bin/anaconda", line 334, in ?
    import dispatch
  File "/usr/lib/anaconda/dispatch.py", line 19, in ?
    from packages import readPackages, checkDependencies, doInstall
  File "/usr/lib/anaconda/packages.py", line 29, in ?
    import fsset
  File "/usr/lib/anaconda/fsset.py", line 21, in ?
    import parted
ImportError: /usr/lib/python2.2/site-packages/partedmodule.so: invalid ELF heade
r
install exited abnormally
sending termination signals...done
sending kill signals...done
disabling swap...
unmounting filesystems...
           /mnt/runtime done
           disabling /dev/loop0
           /proc/bus/usb done
           /proc done
           /dev/pts done
           /tmp/ramfs done
           /mnt/source done
you may safely reboot your system

Now, I have every reason to believe the media is good and the installer works, as I have run it on the laptop on which I'm typing this (last August or September, as I recall). But, for the sake of argument, I tried booting from the CD again and this time had it perform the media check against the CD. It came up with no errors. (Result is PASS it is OK to install from this media)

So I tried to run the installer from it again, and again got "install exited abnormally -- received signal 11.

So I ran it again, and this time got to:
mounting /tmp as ramfs... done
running install...
running /sbin/loader
CPU 0: Machine Check Exception: 0000000000000004
Bank 0: a200000084010400
Kernel panic: CPU context corrupt
In interrupt handler - not syncing

at which point the machine seems to have locked up.

This isn't looking good for the home team, is it?

-- b.r.t.
0
 
nobusCommented:
no you really tried everything.
try testing all devices on another system; if they prove good, you probably have a bad mob or Cpu.
you can try taking out the cpu , and reseat it; or test it on another mobo, if availlable.
0
 
yehudiCommented:
Sorry BarryTice,

I've been off at work.... I see you've had a tough time of it!

I have to agree with nobus' comments above.

Sometimes life sucks... but that does mean that it will get better! :-)
0
 
BarryTiceAuthor Commented:
Heh. That's almost comforting, yahudi! Thanks!

I've contacted tech support for the store where I bought the PC. They had me check the capacitors near the CPU to see if they were flat-top or "domed," and these are domed (unlike the capacitors elsewhere on the board). So, it looks like I'll be getting a new MOBO.

Sometimes life sucks. But I guess with a new MOBO, it will get better!

Thanks for the tips, everyone. I'll keep this open until it's up and running again, then award points accordingly.

-- b.r.t.
0
 
burrcmCommented:
The caps are easy enough to replace - a fine tipped iron and some desoldering ribbon. Saves reinstalling XP too.

Chris B
0
 
yehudiCommented:
IF you are not experienced with soldering - or you have an iron which is not hot enough - it is an excellent way to ruin a PC board.

Far better to get a new board!
0
 
burrcmCommented:
It's ruined already - what's to lose??

Chris B
0
 
yehudiCommented:
What's to lose...

1.  It is obviously still under guarantee... but if he puts a soldering iron on it, then it won't be.
2. If the store doesn't have another of those motherboards, they may replace it with a better one.
0
 
yehudiCommented:
So what has happened with your computer?  Did you get a new m/board?
0
 
cpc2004Commented:
Refer the following problem and it is similar to this problem. Both problem crash with bugcheck code d1 and the failing module is atapi. The culprit is ram.

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21505124.html
Mini072505-06.dmp d1 (0x000059b0, 0x0000000d, 0x00000000, 0xf778bc85) atapi!IdeGetSrbData+f
Mini072605-01.dmp d1 (0x00000060, 0x0000000d, 0x00000000, 0xf778b875) atapi!IdeGetInterruptState+5d
0
 
aanthordCommented:
Did you try running a rebuild from the recovery console?
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 10
  • 6
  • 5
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now