As part of my attempt to debug the problems leading up to last night's post, I uninstalled and physically removed my sound card.
Today I thought that if I'm going to be fighting with my computer I can at least do so with music - so I re-installed the sound card.
And that has given me different errors (although not really new errors).
It appears as if I'm in a bit of a Catch-22. When I have 'verifier' turned on ("Automatically select all drivers
..."), I get a "device driver
attempting to corrupt the system" BSOD.
When I turn 'verifier' off, I get an "uncorrectable hardware" BSOD.
Just to verify, I then turned 'verifier' back on ("Automatically select all drivers..."), and sure enough, I got the "device driver attempting to corrupt the system" BSOD.
I have attached the three dump files that go along with what I just describe.
Files 053010-22198 and -24320 document the "device driver attempting to corrupt the system" BSOD. The particular system program listed is ctoss2k.sys. I should note that I get this BSOD very quickly upon boot up into "normal" windows. I get the black "Starting Windows" screen and then the blue "Welcome" screen, but I only get the "Welcome" screen for about a minute before it goes right into the BSOD.
File 053010-24975 documents the "uncorrectable hardware" BSOD. This error occurred about 3 minutes after complete boot-up into 'normal' Windows. The particulars of this error (as found in reading the dump) are:
OVERLAPPED_MODULE: Address regions for 'CTEXFIFX' and 'CTEXFIFX.SYS' overlap
A couple of other things I should mention:
- I freely admit that I'm in over my head here. I'm not bad in fixing basic errors, but this is pretty much beyond me. I don't really even understand what 'verifier' does. When I was googling previous errors I came across a knowledgeable person who suggested to another person to turn it on. It has really helped, but then again, I'm not exactly sure why.
- I was having the same cycle of errors before (turn on 'verifier' get a 'driver attempting to corrupt' BSOD, turn it off and get an "uncorrectable hardware" BSOD). However, that was with my anti-virus programs. I attempted to reinstall Vipre because it was acting strangely, but when I did I started to get that cycle (the specific file there was sbtis.sys). I uninstalled Vipre and installed AVG but then got right back into the cycle (this time it was avgtdia.sys). I uninstalled AVG and installed Windows Security Essentials and got rid of the cycle but got the 'Machine Check Exception' error that started this thread.
- I've run memtest before with no errors.
- Time and again the errors seem to point to the CPU (and the C states, whatever they are). I'm wondering if I simply need to buy another chip.
- I also wonder if doing a fresh install of Windows 7 might cure this problem. I've noted that the last several things I've tried to install in the last 24 - 36 hours (Vipre, AVG, soundcard) have resulted in the aforementioned cycle of BSODs. I'd rather not reinstall Windows (we all know how time consuming it is) but I'm wondering if that would help. Of course, I'd rather have a pretty good idea that it would help instead of just a guess.
Any/all help is greatly, greatly appreciated!! Attachment 75831