View Full Version : Screen won't boot...crash? Please help!
yooniecorn
04-04-2006, 05:04 PM
Hi everyone,
Computer: Dell Inspiron 1100 (old, I know)
OS: Windows XP Home ed.
Problem:
Okay, here's where it gets complicated.
I kept getting alerts saying that I should delete files to clear space on my HD, because it was almost full..everyday I'd delete a few files to stay in the "safety zone" since I was too lazy to convert some of that stuff to cds or dvds or some kind of external HD device.
One day, the whole thing just crashed..things were running fine, until a blue screen suddenly came up saying something about memory, the system32 file, and inserting the Windows XP disc to repair..
I didn't have the disk on me, so I turned the unit off.
A week later, when I got the disk in the mail (my cousin had borrowed it)...I turned it on, and inserted the disk...only to find that the screen didn't boot.
I could hear that it was on and running, but I saw nothing but black. I restarted several times; with no resolve.
What should I do? I am familiar with troubleshooting, and I'm not afraid to get messy in the hardware if I have to, but this one really stumps me!
Does this seem like an OS problem or a hardware problem? HD problem perhaps?
I checked all of the plugs carefully - none were loose. It's definately not a battery problem, since it is plugged into the outlet with an adapter.
Any help or feedback would be greatly appreciated!
Sylvander
04-04-2006, 09:51 PM
See if these help...
Sylvander’s Diagnostic Flowcharts
Download a copy of my diagnostic flowcharts from here
www.erniek.eclipse.co.uk/downloads/sylvanderdiags.zip
and print them to leaf through.
Begin on the STARTUP chart.
Do you hear any single short beep?
yooniecorn
04-06-2006, 01:56 AM
No, it sounds like it is functioning normally, except during the first 10 seconds that I boot it, I hear a soft but unusual "rrrrrrr"...and then it ceases.
I tried hooking up an external CRT yesterday, with no resolve, so I've ruled out any LCD problems on the laptop itself.
I will take a look through the .zip file, thanks!
Sylvander
04-06-2006, 04:41 AM
I know nothing about laptops, but on the assumption that they work in a similar way to desktop PC's...
No beep = no successful completion of the POST.
Is the POST even running? Any signs of that?
That "rrrrrrr" may be the sign of a faulty fan.
When My CPU's fan began to get old and noisy I the PC becan to develop an intermittent failure to complete the POST [I think it was shorting the PSU].
I replaced the fan and problem was fixed and never returned.
See...
-----------------------------------------------
NO POST, NO BEEP, NO VIDEO
www.pcguide.com/vb/showthread.php?t=39685
-----------------------------------------------
yooniecorn
04-07-2006, 09:51 PM
Thank you, Sylvander for all of your help :p
Hm, let's see.
I do not hear any beeps whatsoever when I try to boot it, so there is no successful completion of the POST.
One of the following three things happens now:
1. It sounds like it is booting properly, except no beep, then I hear a loud "rrrr", and feel the left front side of the laptop vibrating violently, then it ceases into silence after about 10-15 seconds.
2. It sounds like it is booting properly, no beep though, and then I hear a continual "chug, chug, chug" dragging sound every 2 (approx.) seconds.
3. It turns itself off within a few seconds of me turning it on. :confused:
As before, in all of these situations, the screen does not load at all.
I read the thread you suggested and saw your comment mentioning about the possibility that the RAM could be keeping it from completing the POST... and I highly think this could be the case, seeing as the last blue screen I saw before all went awry said something about the memory.
Would it be a good idea to jump right to the step you suggested? (removing all RAM and trying to restart to see if the POST runs)
Sylvander
04-08-2006, 07:23 AM
"saw your comment mentioning about the possibility that the RAM could be keeping it from completing the POST"
If memory serves, that's not what I was thinking or what I meant.
The reason for booting with the RAM removed is to see if the POST is running or not.
If you get memory warning beeps [RAM tests failing] it means that the POST is definitely running and testing ok, which is a very good sign.
Then you would know that not only is the POST running, but that it gets so far as to test the RAM, and the failure to complete the POST comes after the RAM tests.
Here's that part of a generic Phoenix BIOS POST that comes after the RAM tests and up to the first display.
Your POST may differ from this, but hopefully it's similar.
Code_Beeps_POST Routine Description
20h 1-3-1-1 Test DRAM refresh
22h 1-3-1-3 Test 8742 Keyboard Controller
24h Set ES segment register to 4 GB
28h Auto size DRAM
29h Initialize POST Memory Manager
2Ah Clear 512 kB base RAM
2Ch 1-3-4-1 RAM failure on address line xxxx*
2Eh 1-3-4-3 RAM failure on data bits xxxx* of low byte of
memory bus
2Fh Enable cache before system BIOS shadow
32h Test CPU bus-clock frequency
33h Initialize Phoenix Dispatch Manager
36h Warm start shut down
38h Shadow system BIOS ROM
3Ah Auto size cache
3Ch Advanced configuration of chipset registers
3Dh Load alternate registers with CMOS values
41h Initialize extended memory for RomPilot
42h Initialize interrupt vectors
45h POST device initialization
46h 2-1-2-3 Check ROM copyright notice
47h Initialize I20 support
48h Check video configuration against CMOS
49h Initialize PCI bus and devices
4Ah Initialize all video adapters in system
4Bh QuietBoot start (optional)
4Ch Shadow video BIOS ROM
4Eh Display BIOS copyright notice
"Would it be a good idea to jump right to the step you suggested?"
Yes, it might let you know that POST is running and getting so far as to find a memory test failure.
"the last blue screen I saw before all went awry said something about the memory."
That was probably the POST finding a memory error and displaying a warning about it.
"in all of these situations, the screen does not load at all"
Try to find the source of these unusual noises.
If you don't have a Stethoscope hand, just use a [(sound conducting) wooden, plastic or metal?] rod. Place one end against your ear and the other end against the casing near the source.
Any moving parts located near the front left?
Where is the "chug, chug, chug" originating?
yooniecorn
04-14-2008, 11:56 PM
For anyone who may find this thread of use in the future, it ended up being an overheating problem. One of two fans had gone, and the unit overheated, causing both the CPU, and the videocard to fail. Replacing these parts cost more than buying new...so I built a brand-new PC instead. :D
Sylvander
04-15-2008, 03:20 AM
Thanks for reporting back. :)
vBulletin v3.6.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.