-   Slackware (
-   -   BSOD Slackware Style (

Grunty 07-08-2004 07:15 AM

BSOD Slackware Style
Slack gave me the creeps just now. All of a sudden the display went distorted until it become all blue. I thought it would recover and give a shell afterwards but no. My CPU screamed. Just like a fire alarm. I restarted my system and did e2fsck as instructed. It seemed all right at first but when i did exactly what im doing(Juk+kppp+desktop customization on KDE) it happened again. Whatever gone wrong when i havent even installed anything not even swaret. Its a 2 week old slack10 installation and this is what happened. I dont think ill be booting slakware for a while. I love my PC more than Slackware. :cry:

keefaz 07-08-2004 07:31 AM

What is your mother board and ram manufacturer ?

Grunty 07-08-2004 09:22 AM

M7VIG REDFOX. About my ram (256 sdr), i dont know. Probably a generic brand. Its pretty old compared to the recent ones.

keefaz 07-08-2004 09:23 AM

;) thanks

bruno buys 07-08-2004 09:28 AM

Indeed, seems like a hw problem, not slack problem.

gbonvehi 07-08-2004 12:20 PM

Maybe you've a temp monitor on the bios and when you're using kde your cpu gets hot and the monitor is warning you that.

Grunty 07-09-2004 12:05 AM

I have a dual boot system and is in the process of switching to Linux completely. I dont think it is related to hardware problem because it never happened to me in Windows even now. I also checked my cpu temp at boot and its in normal level. I bet some hardware compatibility issues is between my machine and slack or KDE or the Linux kernel?I need to try another distro.

Andronik 07-09-2004 12:06 PM

Whatever you are told about -it is hardware problem.

You have biostar board with award bios.

You have overheated cpu and you graphics freezes because of that.
Get some cooling and check your bios cpu related voltage- temp-clock settings.

1: case is alarm as protection:
The siren-like sound is Biostar's CPU Savior technology at work. It is a warning indicating that the CPU cooler was not installed properly (e.g., the cooler was installed backwards or there is no solid contact between the heatsink and the processor).

Reinstall both the processor and the CPU cooler. Don't forget to apply an appropriate amount of thermal grease between the processor and the heatsink.

2: or it is award bios telling that cpu is too hot (overheated)
i think you have second option.

You have "burn baby, burn!!!" option too of course.

Grunty 07-09-2004 05:51 PM

AS ive said, i always check my cpu temp. Coming from a tropical non air conditioned room, my cpu regular temp is at 50deg. Whenever i play graphics intensive games it rises to 53-54. When the crash happened my cpu temp is only at 52deg. And im only connecting to the internet while playing mp3. That wouldnt be a cause of overheating. It may be due to other parameters (voltages, current) but whatever it is, it only happened in slack. AS im still using my system flawlessly in windows xp.
My hardware monitor software in winxp also indicates perfect operation. Sad but it seems i would be using m$ for a while.

320mb 07-10-2004 10:08 AM

I would re-compile the kernel, and make sure that
it is supporting the proper CPU type, Mobo, etc...........

win32sux 07-10-2004 02:52 PM

have you tried re-installing??? and what about another distro???

a compatibility issue won't appear "all of a sudden" after two weeks...

it sounds more like a configuration issue...

All times are GMT -5. The time now is 03:49 PM.