New
#1
Blue screening / freezing randomly in W7
Ever since I got my computer, the OEM Vista on it was a pain n the butt. It never was stable. That's why I upgraded to Windows Seven Professional. My computer had been running nearly perfectly until recently. Now I'm experiencing quite a bit of freezing and a few bluescreens whenever I play certain games. So far I have not frozen while idle, it always occurs while playing a game. So, because the problem is so random, in an attempt to get all the information someone might need to help me, I'm going to probably give too much information. I've also attached the diagnostic stuff just as this forum asked me to do.
The first blue screen I experienced happened in a game called Cogs. I didn't get any of its details unfortunately.
The second blue screen appeared while playing Portal 2. At the time I brushed it off as an effect of it being really new software. A few updates to the game itself didn't solve the problem. The game would still blue screen (sometimes citing my display drivers or memory management or nothing at all) and sometimes entirely freeze without a blue screen (no response from computer and looping the last 10 milliseconds or so of sound). Finally, I tried running he compatibility diagnostic tool which (the real name of it escapes me at this time) turned on compatibility mode for the executable. It still has the same issue but now it sometimes (maybe half the time) just crashes to my desktop.
Now my computer has frozen several times while playing MineCraft. Only once has it ever blue screened rather than freeze and it definitely caused my display driver to crash.
Next, I recently experienced a bluescreen (display driver crash this time) while playing UT 99. Usually this game is rock solid and never causes issues, but this time after two unexplainable display driver errors in-game, my computer blue screened.
Sometimes I use Skype while playing these games with friends. It crashes (harmlessly in the background) a lot during games like MineCraft, but can go for several hours without issue in a game like Unreal Tournament 99 online. Using Ventrillo instead of Skype has made no difference, and not using either still causes the above blue screens and freezes. It seems my computer's interactions with online software may be to blame, though I can't be certain.
I Googled one of the associated drivers from one of my bluescreens that I had never heard of before. People say that it is a driver for Norton AV which I recently (112 days ago) installed. Some forums also say that Norton causes blue screens in a belated fashin, several weeks after installing it. The fact that Norton actually has a Norton removal tool on their site seems a little tell-tale.
Failing that, the only other software that could be the issue (besides the games themselves) is my SpyBot Search and Destroy (which I love and would really hate to give up).
Lastly, I did investigate a few errors in my Event Viewer. The most troubling were:
- The WD File Management Engine service terminated unexpectedly. It has done this 1 time(s).
This is my external hard drive, but these drivers and software are 100% up to date.
- The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system.
I read on a Microsoft KB article that this is simply an error report they were using to find out why the first 1 MB of memory becomes corrupted upon resuming from sleep mode.
- The Windows Font Cache Service service hung on starting.
I think I just have a lot of fonts, but this happens every boot.
- The driver detected a controller error on \Device\Harddisk3\DR3.
My third drive is bad? I need to pull data off it and remove it anyway as it housed my previous Vista install and I don't want the bad juju from it getting into my system.
- The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.
No idea which drive this is, I wish it would name a letter drive.
- The server {Numbers and letters here} did not register with DCOM within the required timeout.
No idea what this is.
So that's my wall-o-text. Hope this and the diagnostic stuff is enough for someone to lend me a little advice at least.