Forum Home
Press F1
 
Thread ID: 36942 2003-08-24 02:39:00 Major problem bk T (215) Press F1
Post ID Timestamp Content User
170068 2003-08-24 05:50:00 Hmm most HSF's have the film covering the thermal compound but who' to say all do.

The P4 generation of chips had an inbuilt thermoregulatory system that would drop the speed and voltage demand of the chip as it overheats - I've never tested it, but it should be pretty self preserving.

Still hard to say what's causing it, if the smell is coming from the PSU then it's a good chance it is the PSU (although new PSU's often have a slight smell as they burn in), however most PSU's have a couple of fans in em so there is a chance the smell has another etiology but the smell is passing through the PSU.

Obviosuly swapping out the PSU seems the most logical, give the hardware vendor a call and see if they'll loan you one for the afternoon or something.

Swapping out the video card should have no ill effect provided normal precautions are taken (i.e. power off etc)
whiskeytangofoxtrot (438)
170069 2003-08-24 05:58:00 if i was u..i'd take it to a computer shop...wouldnt want a burning smell from a computer leading to a burning computer and the house coming down... csinclair83 (200)
170070 2003-08-24 06:13:00 Awwww c'mon where's your sense of adventure :D whiskeytangofoxtrot (438)
170071 2003-08-24 06:16:00 just got to BIOS hardware monitor

MB Temp: 26 C
CPU Temp: 40 C
CPU fan speed: 2616 rpm
Vcore voltage: 1.58V
+3.3V voltage: 3.34V
+5V voltage: 5.18 V
+12V voltage; 12.28v

has been on for about 10 minutes, no smell, nothing.

But unreadable garge after Win XP boots up, I could vaguely guess it is at the welcome screen.


Cheers
bk T (215)
170072 2003-08-24 06:25:00 Does the boot screen display normally?

So you leave it on for 10 mins or so in the BIOS, then boot into Windoze - does the Windows XP boot screen display normally or is that all garbled as well?

Sounds like the Video Drivers might be kaput, or more likely that the refresh rate is set too high for the monitor.

Burning smell might just be the new PC burning in, pretty normal for most machines to emit it for the first couple of days.
whiskeytangofoxtrot (438)
170073 2003-08-24 06:41:00 > Does the boot screen display normally?

The boot screen display normally, OK

> So you leave it on for 10 mins or so in the BIOS,
> then boot into Windoze - does the Windows XP boot
> screen display normally or is that all garbled as
> well?

The XP boot screen display normally until the welcome screen (I think)
> ..... or more
> likely that the refresh rate is set too high for the
> monitor.

This is most likely because his monitor is a brand new 19" and my monitor is a 5+ years old 15" monitor. Will try on his own monitor.

> Burning smell might just be the new PC burning in,
> pretty normal for most machines to emit it for the
> first couple of days.

Hopefully this is the case.


Cheers
bk T (215)
170074 2003-08-24 08:48:00 Well, now, I could boot in SAFE MODE with my old monitor. Can I rule out CPU problem at this stage?

In Safe mode, how do I change to use lower resolution /refresh rate so that I can boot up normally with my old computer? I right-clicked the desktop / properties /settings , and set to 600/800 at 85 refresh rate when I rebooted, still having problem with the display.

How do I change the settings so that the system will keep the new configuration?

Cheers
bk T (215)
170075 2003-08-24 09:35:00 Set the refresh rate at something like 60 - 85 is reasonably high so may still cause problems - once you've booted in on the new monitor and installed definitions for it you should be able to tweak the refresh up quite a bit. whiskeytangofoxtrot (438)
170076 2003-08-24 10:02:00 So it is not possible to re-set the resolution to lower in safe mode? Maybe, reinstall the video driver may reset it back??

Cheers
bk T (215)
170077 2003-08-24 10:09:00 I'm not 100% certain whether lowering the res in safe mode will lower it also in a normal boot up.

Reinstalling the video drivers may do it, booting into VGA mode (is that still an option, I forget??) may be another way around it.

Retrying a driver reinstall sounds like a good plan.
whiskeytangofoxtrot (438)
1 2