- Dec 30, 2006
- 264
- 0
- 0
So I reformatted my computer a couple of weeks ago and finally got around to getting WoW working again. Played some tonight, noticed my FPS was literally about 25% of where it was before I formatted. We're talking 15 FPS instead of 60+ in crowded areas. So I start messing with settings, checking to make sure drivers are up to date etc. I download some Windows fix having to do with power savings on dual core CPUs and do a reboot. Upon reboot Windows tells me that there's an error in C:\windows\can't remember but it said the file was corrupted. Wonderful, I already know that means I'm looking at another reformat but I keep trying to get into Windows to try and back a few things up. Finally manage to get into Windows in safe mode and move some things around, and I get some type of memory allocation error. Reboots me. Then I get a blue screen trying to log in again. Manual reboot. Random reboots keep occuring while trying to load into windows. Finally get in, finish moving things around, do a system restore just to see if that fixes it. Boots up fine, get into windows, memory allocation error.
I give up and reformat C: in prep for a windows install. Goes fine, then I start installing the files needed to begin installation, and literally every other file it tells me that it can't copy it, and hit enter to retry or f3 to skip. I hit enter, it takes it, moves on and has the same problem. Sometimes I have to try 3 or 4 times on these files. I realize this seems very bad but whatever, I finally get into the Windows install itself, and about 2/3 of the way through it blue screens on me saying Bad_Pool_Caller. I don't know what that means.
Basically, is my computer fried? I've been running an OC on this CPU for over a year, so I guess it's entirely possible it's had it. I reset all bios settings to factory defaults even and things are still messed up. I did try a Bios flash the day before these issues cropped up, but I'm not sure they're related. I don't really know what memory allocation and bad pool caller are referencing. Obviously memory but I don't know if its a memory stick problem or more likely to be CPU/Mobo. I do know when I checked PC health my idle temp was 66 degrees which is way too effing hot, but I've never had shutdown problems related to temp ever since I've had this rig. This all came out of the blue pretty much, so if anyone can help me out here I'd be extremely grateful. I'm pretty much broke atm so I'm not looking forward to someone telling me hardware is shot beyond repair.
I give up and reformat C: in prep for a windows install. Goes fine, then I start installing the files needed to begin installation, and literally every other file it tells me that it can't copy it, and hit enter to retry or f3 to skip. I hit enter, it takes it, moves on and has the same problem. Sometimes I have to try 3 or 4 times on these files. I realize this seems very bad but whatever, I finally get into the Windows install itself, and about 2/3 of the way through it blue screens on me saying Bad_Pool_Caller. I don't know what that means.
Basically, is my computer fried? I've been running an OC on this CPU for over a year, so I guess it's entirely possible it's had it. I reset all bios settings to factory defaults even and things are still messed up. I did try a Bios flash the day before these issues cropped up, but I'm not sure they're related. I don't really know what memory allocation and bad pool caller are referencing. Obviously memory but I don't know if its a memory stick problem or more likely to be CPU/Mobo. I do know when I checked PC health my idle temp was 66 degrees which is way too effing hot, but I've never had shutdown problems related to temp ever since I've had this rig. This all came out of the blue pretty much, so if anyone can help me out here I'd be extremely grateful. I'm pretty much broke atm so I'm not looking forward to someone telling me hardware is shot beyond repair.
