Windows 2000 quit booting / Blue Screen, etc!

TimTim Southwest PA Icrontian
edited January 2005 in Hardware
I'm setting up a new computer. DFI / Elite AZ30-TL motherboard, 1 stick of new and tested PC3200 256 MB, A used Duron 1100 CPU, a used hard drive, and little else.

It made it through the 2000 install fine, and I loaded a wide variety of codecs and antivirus software like I always do in this type of job.

Then it starts blue screening on me. It says something about recent hardware / software changes.

Safe mode didn't work either, it just goes to the Blue Screen.

So I pulled out the big gun - my Knoppix 3.6 bootable CD. And that didn't work either!

I'll get the Knoppix penguin, and a bunch of white lines of text.

It says things like:

Oops

CPU: 0

Process swapper (pid: 1, stackpage=cdfc9000)

<0>Kernel panic: Attempted to kill init!
<1>Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c01205f7

<0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

So what could be the source of this failure? Hard drive? It's used, I can get a good tested one tomorrow.

Motherboard? It's new
Memory - new
CPU - used
Power supply - new, but Powmax.

Any ideas here?

I took out the Knoppix CD, and tried booting again in 2000. I get the blue screen and a message: DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Comments

  • ThraxThrax 🐌 Austin, TX Icrontian
    edited January 2005
    DRIVER_IRQL_NOT_LESS_OR_EQUAL has clasically meant two things, in order of frequency:

    1) Bad RAM.
    2) Overheating CPU.

    Memtest that RAM.
  • muddocktormuddocktor
    edited January 2005
    Yep, I was about to say the same thing about the ram. Even though it's new doesn't preclude the possibility of a bad stick. The times I've had Win2K/blue screen problems were caused by bad ram.
  • TimTim Southwest PA Icrontian
    edited January 2005
    This morning I tried reseating the RAM in the same slot and clearing the CMOS jumper. On boot up, the computer POSTs, and runs through its memory test, then 2000 starts loading.

    Then I got the blue screen, saying "Kmode_Exception_Not_Handled"

    Address 804c23e6 base at 80400000, DateStamp 3ee6c002 - ntoskrnl.exe

    It always says on the blue screen to make sure I have adequate disk space, check drivers and video adapters, and BIOS updates. It mentions disabling BIOS memory options like caching or shadowing, which I'm not sure how to do. I assume go into the BIOS screen and adjust something, but what?

    I then tried reseating the RAM in each slot a few times, always with the same result.

    I don't think it'd get this far in the startup sequence if the CPU were bad.

    Could there be any problem with running a stick of PC3200 in a system made for PC1600/PC2100?

    I'm going to try another stick of memory from my main system. This other computer had better not hurt it!
  • TimTim Southwest PA Icrontian
    edited January 2005
    I tried a few more things. I put the stick of RAM in each of the 2 slots, then tried 2 other sticks of PC3200 256 MB Samsung memory in each of the 2 slots, and none would work. I always got the blue screen.

    Then I put in my Barton 2500+ CPU from my main system. It worked, but at only 1460 Mhz instead of its stock 1830 Mhz. I did switch the on board jumper from 100 to 133 FSB when I put it in.

    The computer started up and worked like that.

    Then I put everything back where it came from in both computers.

    This new system got its 100 Duron and original stick of memory back. I reset the jumper to 100 FSB and cleared the CMOS again, as I'd done many times during the parts swapping.

    Now it works. ? Maybe some of the CPU pins were dirty or something, and switching things around cleaned them off? I don't know what else would do this.

    I'm going to try shutting down and restarting the system a few times to see if it keeps working.
Sign In or Register to comment.