Freeze, Blue Screen, Repeat.

[Nick.]

First, my full computer specs;

OS Name Microsoft® Windows Vista™ Home Basic
Version 6.0.6001 Service Pack 1 Build 6001
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Gigabyte Technology Co., Ltd.
System Model EG31M-S2
System Type X86-based PC
Processor Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, 2999 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. F1, 4/11/2008
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.0.6001.18000"
Installed Physical Memory (RAM) 2.00 GB
Total Physical Memory 2.00 GB
Available Physical Memory 1.05 GB
Total Virtual Memory 4.23 GB
Available Virtual Memory 3.06 GB
Page File Space 2.29 GB
Page File C:\pagefile.sys

FULL account:
Basically one night I was playing a computer game (World of Warcraft to be exact) and my computer suddenly froze with mouse movement. It wasn't uncommon for this to happen, since the exact same thing happens when the internet disconnects for a second. However, this lasted longer. I tried CTRL ALT DLT but it didn't work at all. My mouse then froze. I waited like this for some time before finally pressing the power button on my machine to turn it off, for the first time since I bought it (a few months ago). I turned it back on, and it came up with the error:
Quote:
Verifying DMI Pool Data.........
Boot from CD/DVD:
Press any key to boot from CD/DVD.... (which I can't do because none of the USB ports work during this period for some reason)
A disk read error occurred (once the CD/DVD boot timed out and it tries to boot from system)
Press Ctrl+Alt+Delete to reboot (which again I cannot do, because of keyboard issues)
. After about half an hour of constantly trying to reboot, it finally somehow worked again, and turned on. I was sure it was a miracle, and thought nothing more of it. Later that night however, I happened to be playing the same game again, and the exact same thing happened. I went through the same steps as before, and got it working. I decided to try and uninstall and reinstall WoW (World of Warcraft) in case it was a problem with that. However, when I left my computer to install it for the night, it happened again, this time with a blue screen (that flashed too quickly for me to see) and attempted to reboot. I shut it down for the night, and went to bed. The next morning I tried a system restore to June 5th, which seemed to work wonders. My computer worked fine the rest of the day. WoW resinstalled well, and I even played for a while. This morning however, I turned on my computer and left to have breakfast. When I returned, it was still on the boot screen with some error I conveniently forgot to write down, however it was slightly different than the one before. I rebooted and played a little bit, before it happened yet again. This time it displayed some error about a security log on not operating correctly, which was odd. Again I forgot to write down the exact details.

Any help would be of course be extremely nice. I'm not extremely good with computers, so try to help me out by correcting any of my errors and by telling me if I filled something incorrectly. My computer is rather new, and I'd hate to buy a new one, actually I probably couldn't even afford one, unless warranty kicks in. Thanks a bunch!

~Nick

Oh, by the way, my computer is way better than the minimum or even recommended requirements for World of Warcraft... It should be the reason.
Plus, if it makes a difference I also removed all dust from both of my fans, and moved the computer out of the corner it was in. I also am currently typing this on my Ubuntu operated laptop, as I'm not sure if booting up will further harm my computer.
Thanks again!

[Broni]

Run hard drive diagnostics: http://www.tacktech.com/display.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD, and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, unfortunately, you're out of luck, because Toshiba doesn't provide any diagnostic tool.

[Nick.]

At the moment at reboot all I get is
Verifying DMI Pool Data.........
Boot from CD/DVD:

A disk read error occurred
Press Ctrl+Alt+Delete to reboot (which I cannot do, because all USB ports are shut down during this period)

I tried a few times each time responding in this. So I can't do any diagnostics on my computer. I suppose it's time for a professional, since I can't really do anything on my own w/o being able to log on. Unless anyone could tell me how to get my USB ports to work during boot up so I could boot off my Vista disk and attempt to repair windows...

Thanks for your fast reply though; I wish I had come here sooner when my computer would still log me on.

[Broni]

You don't need Windows access. If you read my reply carefully...

Depending on the program, it'll create bootable floppy, or bootable CD.

[Nick.]

I can't boot up whatsoever;

(which I can't do because none of the USB ports work during this period for some reason)

I can open the boot menu, but after that point all USB ports shut off so I can't use my keyboard to direct it to CD boot.
Do you know how to select CD/DVD boot w/o a keyboard? Or how to make my USB ports work during boot up?

Thanks again for your quick response!
~Nick

[Broni]

Your best option is to get/borrow PS/2 keyboard. It often comes handy.
You can get one at 2nd hand store for a buck, or so.

[Nick.]

Thanks I'll try that out. I'll come back with the results.
At what point should I see a professional about fixing it?
And when should I stop trying to boot it up, in case of worsening it?

[Broni]

Well, if you're up to a challenge type of guy, we'll try to help you out.
If you can't do something, or we'll see, we can't do much more on-line, you'll always have time to spend your money on a professional guy

[Nick.]

OK, well I'm somewhat young so I don't see myself doing much in the way of fixing my computer by hand... More by mouse if possible.
I found a PS/2 Mouse and keyboard lying around, and tried out the CD... Unfortunately it was all gibberish to me .
I couldn't take screenshots, so here are some pictures:

[Broni]

OK, which download did you put on CD?

[Nick.]

Samsung Disk Manager 10.42 (12.30.2003)
Some old BIOSs have a capacity barrier and does not recognize the high capacity HDD. In that case, the Disk Manager will solve the capacity barrier.

- Download Disk Manager for FDD (Direct Link)
- Download Disk Manager for CD-ROM (Direct Link)
- View Additional Information

(First Samsung one -> http://www.tacktech.com/display.cfm?ttid=287#samsung )

[Broni]

The first one is ESTOOL.EXE file. Copy the file to a floppy, and boot from the floppy.
The second one is for creating bootable CD.

[Nick.]

The CD worked I just didnt understand it
What I took pictures of was all that the boot up had to offer in terms of information

[Broni]

That screen gives just some info about your hard drive. I don't see any testing option there.

[Nick.]

Hm, right, I guess it was just an information type deal. I made a new disk with diagnostics (the second one on the list) but I wanted to back everything up and try everything I can before risking the loss of everything on my hard drive. I'll get back to you once I try other things and ac everything up. Thanks again for your help!

[Broni]

Very well.

[Nick.]

Verifying DMI Pool Data.........
Boot from CD/DVD:

A disk read error occurred
Press Ctrl+Alt+Delete to reboot

Ok so that's the most common error I get when trying to boot up... Is it probably a hard drive problem? If so, could it be causing all my problems?

[Broni]

One more time. You need to run HD diagnostics.

[Nick.]

And is there any way to do this without completely erasing everything on your hard drive?

[Broni]

You won't erase anything. You'll test your drive for errors.

Let me explain it to you one more time.
Go here: http://www.tacktech.com/display.cfm?ttid=287#samsung
Download
- Download ES-Tool Bootable CD ISO (Direct Link)
from this section:
ES-Tool (The Drive Diagnostic Utility) v2.12a (03.12.2009)
You'll download estool_CDROM.zip file.
Unzip it by double clicking on it.
Inside, you'll find Image.iso file.
Download ImgBurn: http://www.imgburn.com/
Using ImgBurn, burn Image.iso file to a CD.
Put CD into your CD drive.
Restart computer.
Look for following message:
Press any key to boot from CD
Press some key, and the CD will boot, starting testing process.

[Nick.]

I understood completely, and already did download and burn the ISO, and did already boot from the CD. However, it came up warning that if I tried testing my hard drive it would most likely cause it to be completely cleared.

[Broni]

This is nonsense. No testing tool will erase anything from the hard drive, unless you're selecting some wrong option.

[Nick.]

Excuse me, it says may not will.
But still, very sensible that I would be wary of it.

Or are they just trying to make sure they don't get in trouble if the disk is erased?

[Broni]

they just trying to make sure they don't get in trouble if the disk is erased?

Exactly. The chances are very, very slim.
Being on number of computer boards, I have to yet hear any case, when diagnostic software erased data.
Just in case, you want to sue me , if you're supersensitive about your data, you can always slave the drive in another computer, and back up the data before you run diagnostics.

[Nick.]

Ok, I won't sue you.

Currently everything (DMA, S.M.A.R.T., Spin Down/Up, Simple Surface Scan, Write Verify, Random Surface Scan) has passed, I'm just waiting on the full surface scan which is pretty long. I'll get back to you when it's finished.

[Broni]

Fair enough

[Nick.]

OK, the full scan passed. Everything was fine and passed.
What should be done next?

[Broni]

That's good news.
Do you have Windows CD?

[Nick.]

Yup I do... However I'm not sure of the product key which I believe is required.
How can I find it if I can boot my machine up regularly?

[Broni]

Try Windows repair: http://www.geekstogo.com/forum/How-to-repair-Windows-XP-t138.html

[Nick.]

I booted from the Vista (the guide you gave is for XP ) CD, but my steps didn't follow the guides I found on the Internet...
http://vistahomepremium.windowsreinstall.com/repairstartup/repairstartup.htm
Here for example, it says that after the initial set up screen (with language, etc.) it goes to the installation screen. For me though, it goes to the screen asking for a product key, then license agreement, then it starts downloading.
Help?

[Broni]

I booted from the Vista

Oooops...
Vista repair: http://www.vistax64.com/tutorials/88236-repair-install-vista.html

[Nick.]

I ended up reinstalling Vista, just because I was completely tired of screwing with it...
Evidently it wasn't done with me.
Now it's saying my Ethernet driver cannot install correctly...

[Broni]

Oh boy....
Are you getting the driver from your computer maker site?

[Nick.]

Found the driver, installed it, internet works perfectly now.
So far so good, with everything. I blew out the dust inside my computer casing, which shouldhelp.
Thanks for all your help! I'll be sure to come back if something else goes wrong.

[Broni]

Nice job

[Nick.]

OK, so i checked system memory (via Windows), checked the hard drive(via Samsung checker), blew out all the dust, bought a huge outside fan that keeps the whole room cool, especially the computer, checked multiple times for viruses, and reinstalled Windows...
But I still get the blue screen occasionally when playing WoW.

STOP: 0x000000F4 (0x00000003, 0x36660340, 0x81c48400)

Thanks again for your help!
~Nick

[Nick.]

OK, so this time I got a window:
"Logon process has failed to create the security options dialog
Failure-Security Options
OK"

I pressed OK and my computer froze... I looked it up and it's a common problem related to my firewall, ThreatFire. I just uninstalled it in safe mode, so I hope it will start getting better.

[Nick.]

Again a blue screen, this time when coming back from sleep mode, with the error:
0x000000A0

[Broni]

First of all, disable all power saving features. Nothing, but a pain.

Open Windows Explorer.
Navigate to: C:\Windows\Minidump folder.
If you see any .dmp files, zip all of them, and attach zipped file to your next reply.
Vista users. You may need to copy .dmp files, paste them into some other folder, or desktop, and zip them there.

[Nick.]

There was nothing there
I downloaded SpeedFan to check out temperatures, and my GPU is at 66 degrees C... Not good, right?

[Broni]

Video card can take it.
Post all temperatures.

[Nick.]

GPU 67C
Temp1 34C
Temp2 -2C
Temp3 22C
Temp 0C
Temp 67C
HDO 30C
Core0 44C
Core1 43C

[Broni]

They look OK.

1. Click Start, point to Settings, and then click Control Panel (Start>Control Panel in Vista).
2. Double-click System.
3. Click (Advanced system settings link in Vista, then --->)the Advanced tab, and then click Settings under Startup and Recovery.
4. Make sure, there is a checkmark in Write an event to the system log.
5. In the Write debugging information list, click Small memory dump (64k).

Next time, BSOD happens, you should have some files in Minidump folder.

[Nick.]

It was set as Kernel memory dump... Heres the file. -> http://www.mediafire.com/?dmwl2r7ymy2
If it helps at all these are all my recorded STOP errors.
0x000000F4
0x0000007A
0x000000A0
0xc0000185
0x00000003
0x86660340
0x81c48400

So the GPU heat is nothing too bad?

[Broni]

Where is that file from?
dmp file can't be over 160MB(!) in size.

[Nick.]

From my Windows folder... It said that it would write the kernel dump file there.
MEMORY.dmp

[Broni]

Navigate to: C:\Windows\Minidump folder.
If you see any .dmp files, zip all of them, and attach zipped file to your next reply.

It said

What is "it"?

[Nick.]

My computer
This was from before your instructions...
There hasn't been another BSOD yet, but the last one wrote this .dmp file.
When I checked the windows settings it was kernel dump instead of small memory, which is why its different.

[Broni]

Again, I'll need dmp files from Minidump folder, when next BSOD will happen.

[Nick.]

Blue screened during shutdown, but did not create a file in Minidump, regardless of me making the setting as you told me to.

[Broni]

[Nick.]

Yup, those exact settings. Still Minidump is empty.

[Broni]

Please download VEW and save it to your Desktop: http://images.malwareremoval.com/vino/VEW.exe

Double-click VEW.exe then under Select log to query, select (as appropriate):
Application
System

Under Select type to list, select:
Error

Click the radio button for Number of events
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.

In Notepad, click Edit > Select all then Edit > Copy
Reply to this post, click in the reply window and press Ctrl+V on your keyboard to paste the log.

[Nick.]

Vino's Event Viewer v01 run on Windows Vista
Report run at 17/07/2009 7:59:11 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/07/2009 3:06:59 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 12/07/2009 3:38:36 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 12/07/2009 3:54:11 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program Explorer.EXE version 6.0.6001.18000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Problem Reports and Solutions control panel. Process ID: 6c8 Start Time: 01ca02a20c9707d5 Termination Time: 60000

Log: 'Application' Date/Time: 12/07/2009 3:58:29 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 12/07/2009 6:11:19 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 12/07/2009 6:35:52 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 12/07/2009 4:15:57 PM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 13/07/2009 8:05:20 AM
Type: Error Category: 17
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing.  HRESULT was 800706e5 from line 78 of d:\vistasp1_gdr\com\complus\src\events\tier2\security.cpp.  Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 13/07/2009 5:48:34 PM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 13/07/2009 7:32:38 PM
Type: Error Category: 17
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing.  HRESULT was 80070534 from line 147 of d:\vistasp1_gdr\com\complus\src\events\tier2\security.cpp.  Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 13/07/2009 10:34:10 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application getPlusPlus_Adobe.exe, version 1.6.2.36, time stamp 0x49215c28, faulting module kernel32.dll, version 6.0.6001.18215, time stamp 0x49953395, exception code 0xe06d7363, fault offset 0x000442eb, process id 0xa80, application start time 0x01ca040a097d7750.

Log: 'Application' Date/Time: 14/07/2009 11:21:25 PM
Type: Error Category: 3
Event: 215 Source: ESENT
WinMail (3164) WindowsMail0: The backup has been stopped because it was halted by the client or the connection with the client failed.

Log: 'Application' Date/Time: 14/07/2009 11:22:29 PM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 15/07/2009 2:14:13 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 15/07/2009 2:30:43 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 15/07/2009 4:58:06 AM
Type: Error Category: 0
Event: 8195 Source: Microsoft-Windows-Security-Licensing-SLC
License Activation Scheduler (SLUINotify.dll) failed during automatic activation with error code: 0x8000FFFF

Log: 'Application' Date/Time: 15/07/2009 4:40:51 PM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 15/07/2009 5:13:57 PM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 15/07/2009 6:14:56 PM
Type: Error Category: 16
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing.  HRESULT was 8007043c from line 45 of d:\vistasp1_gdr\com\complus\src\events\tier1\eventsystemobj.cpp.  Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 15/07/2009 6:15:17 PM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/07/2009 3:00:44 AM
Type: Error Category: 0
Event: 15016 Source: Microsoft-Windows-HttpEvent
Unable to initialize the security package Kerberos for server side authentication.  The data field contains the error number.

Log: 'System' Date/Time: 12/07/2009 3:06:39 AM
Type: Error Category: 0
Event: 15016 Source: Microsoft-Windows-HttpEvent
Unable to initialize the security package Kerberos for server side authentication.  The data field contains the error number.

Log: 'System' Date/Time: 12/07/2009 3:37:12 AM
Type: Error Category: 0
Event: 15016 Source: Microsoft-Windows-HttpEvent
Unable to initialize the security package Kerberos for server side authentication.  The data field contains the error number.

Log: 'System' Date/Time: 12/07/2009 3:50:27 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:50:35 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:50:44 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:50:52 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:51:01 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:51:10 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:51:18 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:51:27 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:51:35 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:51:44 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:51:53 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:52:01 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:52:10 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:52:15 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Windows Modules Installer service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 12/07/2009 3:52:18 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:52:27 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

Log: 'System' Date/Time: 12/07/2009 3:52:35 AM
Type: Error Category: 0
Event: 11 Source: cdrom
The driver detected a controller error on \Device\CdRom0.

[Nick.]

Id like to add that my computer has been working well for the past day or two, which is good. Im thinking its over heating because it suddenly started acting up again today- the hottest day where I live in a long while.

[Broni]

We checked temperatures, and they looked OK.

Try this:
Go to control panel and open Administrative tools.
Double click on Services.
Go down to Windows Managament Instrumentation.
Stop this service. along with Security Center.
Exit out of this area to your desktop.
Open Windows Explorer.
Go down to c:\windows\system32\wbem\repository.
Delete the Repository Folder
Go back to Services and restart the WMI program
Then re-boot the computer

[Nick.]

I did it, and so far so good.
I'll get back to you in a couple of days or if it happens again sooner.

[Broni]

I hope, that did it

[Nick.]

Nope, froze and blue screened.
:/
0x000000F4 is the current popular stop error if that makes any difference?

[Broni]

I think, I need good night sleep, because as of now, I'm out of ideas...

[Nick.]

OK, ill wait for an idea.

[Nick.]

Any new ideas?

[Broni]

Not really. We went through so many checks, that I don't have anything else in my sleeve.

[Nick.]

I took out the GPU and cleaned it off... Put it back in, reformatted my internal HDD (all backed up) reinstalled windows, and everything is good as of so far. (2 days )

[Broni]

Thanks for posting back with great news

[Nick.]

OK, so after 17 days, it crashed again. Same error as before,
STOP 0x000000F4
Since I reinstalled Vista it reset to Kernal dump, and I forgot to change it. I did now though.

[Broni]

Post back, if you have any new BSODs. One BSOD is not a tragedy yet.

[Nick.]

2 more today. For some reason, although my crash dump settings are exactly as you said, my computer refuses to create the dump. There isn't even a minidump folder.

[Broni]

Unfortunately, I'm out of ideas. I'm sorry.

[Nick.]

Time to bring it in to a professional?

[Broni]

Probably...