|
This thread is locked; no one can reply to it. |
1
2
|
Annoying BSOD |
type568
Member #8,381
March 2007
|
{"name":"601425","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/8\/3\/83e6d9a06f510f14afb513375e044e6a.jpg","w":1280,"h":960,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/8\/3\/83e6d9a06f510f14afb513375e044e6a"} As the thread name says, a BSOD.. However, while playing Starcraft(the old one), I'm getting BSODs from time to time. Without any clue, what may the reason be.. Recently I decided to try some game on Allegro, and ended up with the same. Actually, it wasn't immediately a BSOD. It was a freeze.. Then after a good bunch of key hits, it crashed(same with with Starcraft). I assume it's a PC freeze, and then BSOD due to keyboard input overflow- which wouldn't be possible without a freeze- as it's extremely light task to process the keyhits, or increase the buffer or whatsoever.. Well, not while frozen. One more fact about my system: The graphics card was extremely hot, even while in 2D mode, which is a nonsense.. So I decided to chill it down a bit- I decreased the clocks about 2 times below it's default 2d mode, and didn't notice any performance difference but did get at least 10 degrees Celsius temperature decrease. The reason I don't think it's the cause is the fact that it runs fine in safe mode, at low resolutions as well.. And anyways, the lighter the task- the easier should it be for the card.. Besides, graphics related BSODs usually identify the faulty driver(which didn't happen here).. I'm sort of out of ideas what's the cause is.. And it's quite annoying for me, as I don't consider myself a hardware newbie nor did I have any kind of the problem for recent years..
|
Bob Keane
Member #7,342
June 2006
|
I had trouble installing a network printer in my room due to temperature issues. The computer ran okay but would not install the printer. Is it hot in your room as well? <edit> For fun, can you save the screen as a screen saver? By reading this sig, I, the reader, agree to render my soul to Bob Keane. I, the reader, understand this is a legally binding contract and freely render my soul. |
type568
Member #8,381
March 2007
|
Bob Keane said: Is it hot in your room as well? +28C
|
Thomas Fjellstrom
Member #476
June 2000
|
That's weird. I don't see a BSOD error code, least not a normal one -- |
Matthew Leverton
Supreme Loser
January 1999
|
Why did you write your allegro.cc password on the top of your monitor? |
kenmasters1976
Member #8,794
July 2007
|
I just recently had my machine BSOD'ing quite often. I tracked the cause down to my wireless USB adapter and had to replace it. I also saw that BSOD a while ago last time my HDD crashed. The BSOD was almost identical to the one in your pic, so I'd say it's definitely a hardware issue.
|
GullRaDriel
Member #3,861
September 2003
|
A stop 01E is commonly hardware failure. Most of the time it's a memory who's in fault. Try to keep only one at a time and reboot. Edit: A good thing is also to test your memory with memtest i.e "Code is like shit - it only smells if it is not yours" |
BAF
Member #2,981
December 2002
|
Memtest is much more convenient than pulling random sticks and waiting for a crash. It's more definitive as well. |
Arthur Kalliokoski
Second in Command
February 2005
|
Maybe the old Starcraft is using something that the other games don't, I remember playing the Tomb Raider II demo on a Pentium MMX 233 and it's the only program I had that would trip the thermal sensor to slow the cpu way down. I think TR was using MMX heavily along with the integer registers at the same time. They all watch too much MSNBC... they get ideas. |
Elverion
Member #6,239
September 2005
|
I've found your problem: You're using Windows. But seriously, looks like a driver problem. Try reinstalling any applicable drivers. If that doesn't help, reinstall Windows. -- |
Hard Rock
Member #1,547
September 2001
|
Starcraft II is known to cause heating issues, if you google you'll find some complaints. I don't know what the exact details are though. Why don't you revert to stock speeds and see if that fixes your crashes rather then try to guess if its something else? _________________________________________________ |
type568
Member #8,381
March 2007
|
Thomas Fjellstrom said: That's weird. I don't see a BSOD error code, least not a normal one This is Microsoft. Matthew Leverton said: Why did you write your allegro.cc password on the top of your monitor? Now how dare you name my password out loud?! I trusted my password to your system, and you say it out loud?! I have problems with remembering these letters, so what?! kenmasters1976 said: I just recently had my machine BSOD'ing quite often. I tracked the cause down to my wireless USB adapter and had to replace it. I also saw that BSOD a while ago last time my HDD crashed. The BSOD was almost identical to the one in your pic, so I'd say it's definitely a hardware issue.
Erm, I must note that all Win7 BSODs look quite similar.. GullRaDriel said: A stop 01E is commonly hardware failure. Most of the time it's a memory who's in fault. Try to keep only one at a time and reboot. Edit: A good thing is also to test your memory with memtest i.e Are there any tests can be done without burning stuff and booting it? Elverion said: I've found your problem: You're using Windows. But seriously, looks like a driver problem. Try reinstalling any applicable drivers. If that doesn't help, reinstall Windows. Sounds good, I'll update my graphic card driver. Hard Rock said: Starcraft II is known to cause heating issues, if you google you'll find some complaints. I don't know what the exact details are though. Why don't you revert to stock speeds and see if that fixes your crashes rather then try to guess if its something else? Any modern game with intense graphics challenges a well performing system's cooling system.. It's normal IMO. P.S: The reason I do not want to revert settings back to stock, is as follows: 1) I do not like the idea of having voltage of my CPU auto-adjusted, jumping high above any imaginable normal. So reverting everything back, is a huge chunk of work which is likely not to come out useful.. I'd like to avoid it. I'll update drivers asap, but I may not know soon if it was any useful.. I'd like to really find out what the problem is, not just fix it. P.P.S: GullRaDriel said: A stop 01E is commonly hardware failure. Could you link me somewhere I could get some well compiled information regarding the topic? Thanks..
|
Arthur Kalliokoski
Second in Command
February 2005
|
type568 said: Could you link me somewhere I could get some well compiled information regarding the topic? They all watch too much MSNBC... they get ideas. |
type568
Member #8,381
March 2007
|
Thanks, crap though: Quote:
These errors may be caused by one or more of the following: And if in three words- any low level application, e.g. that 256color emulation at 640 x 480, antivirus- easily(evil Kaspersky), driver also easily.. Jeez. Append: driver updated.. Cute fact the software is 2 days old
|
BAF
Member #2,981
December 2002
|
type568 said: Erm, I must note that all Win7 BSODs look quite similar.. What? How many Win 7 BSODs have you gotten? 99% of the time, they are hardware or driver related. Backward compatibility is a software issue, and everything's walled off pretty well now so user-space software shouldn't be causing a BSOD. Quote: 1) I do not like the idea of having voltage of my CPU auto-adjusted, jumping high above any imaginable normal. Quote: So reverting everything back, is a huge chunk of work which is likely not to come out useful.. I'd like to avoid it. I'll update drivers asap, but I may not know soon if it was any useful.. It's called troubleshooting, this is part of finding out what the problem is. Reverting settings back is very easy, just restore the BIOS to default settings. It's restoring your OC settings that's a pain. type568 said: Thanks, crap though: But that's what causes BSODs... |
type568
Member #8,381
March 2007
|
BAF said: What? How many Win 7 BSODs have you gotten? 99% of the time, they are hardware or driver related. Backward compatibility is a software issue, and everything's walled off pretty well now so user-space software shouldn't be causing a BSOD. They're all blue with white letters on'em Quote:
By default CPU voltage is automatically set by the motherboard which has very strange methods to identify the needed voltage so that I've had it outputting much higher values than I could imagine risking while I OC. Quote: It's called troubleshooting, this is part of finding out what the problem is. Reverting settings back is very easy, just restore the BIOS to default settings. It's restoring your OC settings that's a pain. I almost agree, although I doubt my system would boot with everything on default settings.. But yes, it wouldn't be too much pain to reset it & fix voltage- I agree. Quote: But that's what causes BSODs.. Erm. Guess you're right sir. Append:
|
MiquelFire
Member #3,110
January 2003
|
I got a BSOD in Win7 64-bit. God, the size of them numbers! Process Explorer caused it. (something I was doing hardware related of all things...) --- |
Arthur Kalliokoski
Second in Command
February 2005
|
type568 said: 2) There's a huge number of settings in BIOS related with 2x clocks, 3x voltages and a countless number of other settings(especially memory stuff), and I found the "BIOS Profile" failing once, which forced me to restore all settings manually, which wasn't much of fun.. When I was busy with the adjustments, I ended up writing setting values down to a notebook. Google for "save cmos to file". You could write it yourself except Windows NT won't let you read/write arbitrary hardware ports without some sort of device driver. They all watch too much MSNBC... they get ideas. |
BAF
Member #2,981
December 2002
|
CPU voltage should be set automatically based on the voltage the CPU says it requires. Running at stock clock, the voltage should be perfect. Also, are you sure you don't have hardware problems? Seems very strange that your system wouldn't boot with default settings, at least with regard to cpu clocks/voltage/etc. My system will almost boot on default settings, I just have to change my SATA controllers from RAID/IDE/whatever is default to AHCI mode. |
type568
Member #8,381
March 2007
|
MiquelFire said: I got a BSOD in Win7 64-bit. God, the size of them numbers! Process Explorer caused it. (something I was doing hardware related of all things...) Huh? Arthur Kalliokoski said: Google for "save cmos to file". You could write it yourself except Windows NT won't let you read/write arbitrary hardware ports without some sort of device driver. Well, perhaps an option. BAF said: CPU voltage should be set automatically based on the voltage the CPU says it requires. Running at stock clock, the voltage should be perfect. It's never is though.. At least so I heard a lot, and seen by third party tools measuring voltage- my mobo was overvloting the CPU, not like it has had any real effect on anything. Quote: Also, are you sure you don't have hardware problems? Seems very strange that your system wouldn't boot with default settings, at least with regard to cpu clocks/voltage/etc. My system will almost boot on default settings, I just have to change my SATA controllers from RAID/IDE/whatever is default to AHCI mode. All default voltage & clock settings will boot and most likely work stable, but I'm quite sure it won't find the raid to boot from, unless pointed at it.. Also some devices are disabled I think(e.g. plugged in sound card + stock so one disabled) etc'
|
Thomas Fjellstrom
Member #476
June 2000
|
BAF said: CPU voltage should be set automatically based on the voltage the CPU says it requires. Running at stock clock, the voltage should be perfect.
type568 said: It's never is though.. Yeah, one or two of my mobo's like to have stock auto OC settings. They are usually not FATAL though, but they aren't always stable. So I tend to turn off the stock OC settings, and leave everything at REAL stock settings. -- |
MiquelFire
Member #3,110
January 2003
|
Look at your screenshot (didn't pay much attention to this meself actually), but note how big the *** STOP line is. Seems you're running 64-bit as well. --- |
type568
Member #8,381
March 2007
|
BAF said: Also, are you sure you don't have hardware problems? Seems very strange that your system wouldn't boot with default settings, at least with regard to cpu clocks/voltage/etc. My system will almost boot on default settings, I just have to change my SATA controllers from RAID/IDE/whatever is default to AHCI mode. Certainly, I do.. Win7 Ultimate x64..
|
GullRaDriel
Member #3,861
September 2003
|
The way to know if it's a driver is something like that (afaik): -Activate memory dump (google for it) If it's a program/driver who's causing the bsod, you'll have the name of the faulting componant. Else, it's an hardware failure and you're stuck to what I've already said: manual testing of each memory row. "Code is like shit - it only smells if it is not yours" |
type568
Member #8,381
March 2007
|
Alright.. Downloading debugging tools. I ran Prime95 blend test overnight.. Found error after 2.5hours(that made meh clean the CPU heatsink). But.. If it took over 2 hours of warming up for the CPU/RAM to crash how could it be the reason of a freeze with an extremely light application with everything being cool.. ? I'm damn sure it's something else. Append: A yeh, I've had few more BSODs recently, and one of'em identified it was something USB related(well, mouse & keyboard a connected through USB..)
|
|
1
2
|