Quote:
Originally Posted by PostStrata
EDIT: to clear any misunderstanding... My pc Completely Freezes... nothing works, nothing moves.. I have to hold the power button to shut it off. I only get the Freezing. I never got an error popup or anything along those lines. Just freezing here.
I have the same exact problem, except I think my problem is more escalated than yours as my PC freezes on startup(on the password screen even) also in safe mode... so I'm assuming its a windows Drivers issue or a registry issue.
I also use Sc2 and Livestream Procaster... but so does my brother(the pc I'm using right now to post this).
At first I would notice windows about to freeze while playing SC2(doing the machine gun sound thing) for a split second then it would go back to normal. I have only streamed once and have not attempted to stream video again.
My specs:
Intel(R) Core(TM) i7 CPU 950 @ 3.10GHz (4 CPUs, 8 Threads via HyperThreading)
Memory: OCZ 6 GB RAM
Hard Drive: Western Digital 7200 RPM 1 TB HDD
Video Card: EVGA Nvidia GeForce 460 SE 1 GB
Sound: Integrated Realtek ALC889
OS: Windows 7 Ultimate 64-bit
Motherboard: GIGABYTE X58A-UD3R
Computer Case: HAF 932
Mouse: Razer Imperator
Power Settings: High Performance
Msconfig: All startup services are off except windows startup service.
And I still freeze at startup in the Windows Welcome Screen.
Everything is default settings with the latest updates and Drivers. I can get into Safe mode before it freezes after 5 min but in regular mode it freezes instantly at startup. This doesn't happen to my brother and he has the same exact specs as me except he has an ATI Radeon HD 5770 1 GB and a standard Dynex optical mouse and a G15 keyboard. my brother also has Livestream procaster and SC2, and he also streams constantly.
My assumptions:
- SC2 screwed up our registry somehow, although probably unlikely
- My mouse driver is causing this... although the machine gun sound (almost freezing of my PC) happened before I even got my mouse. I also had a standard(windows Drivers) optical mouse before the Razer one.
- Livestream could have screwed up the Registry... more likely than SC2 causing this.
- Our case is causing the Problem.... if thats even possible... lol
-???
I'll let you know if anything works. Then perhaps we can game on SC2 :P
|
EDIT: I actually wrote this first and it never made it to you for some reason. I went ahead and sent it since it could be the cause but at this time I am not certain if this has not been handled with newer PCs. This came up on a unit which had a few years on it. I did not include that part in my writing and I should have, it is important. I am going to try a BIOS clear to see if this will resolve the problem on my end, if so all the better but no gurantee on that.
The problem is your case? That made me chuckle

we all know
it had to be Santa going down the chimney that caused your system to mildly overheat. 
(Dont get mad

Im just playing along with you here.)
Over the holidays I got involved in a one on one with the developer of Real Temp, an online, downloadable, highly respected, widely used PC temperature monitoring program.
The conversation we had delt with a bug I found on a windows PC (which the Real Temp Author found first) which has carried over to many temperature monitoring programs. As it turns out Real Temp seems to be free of this bug as they have worked around it. Most other temp monitoring programs have not done this yet.
As the conversation went on the problem potential for processors which utilize HYPER THREADING developed and were noted as potentially using the wrong core to process some of the threads. This could create locks in programs if this indeed is occuring. This could be why you are seeing what you see. At this point I can not say for sure.
The problem I discovered occurs when the BIOS assigns an APIC ID other than 0123 for a quad core and anything other than a sequential number series for other CPUs. When the APIC ID is not in sequence programs selecting core 1 of a processor for example may actually select core 2 , 3, etc depending on the number of cores available. The only way to avoid this is to open a core, query it, and see if it is the correct core to select before processing the thread. It is doubtful programs using Hyper Threading are going through the motions to insure they are selecting the correct core to process a thread. The solution is to fix APIC ID so it never goes non sequential.
Presently I am in the process of notifying, Microsoft, Intel, APIC, BIOS manufacturers, and a host of companies who are producing bad results due to landing on an incorrect core.
Note: This may or may not be your problem, at this time it is undetermined how many PC owners are affected by this bug as well as the number of programs processing multiple threads in error as a result. This error may have been submitted and resolved, if so the fix has never made it to me. I update frequently, including BIOS, so it should be resolved if it was handled.