Windows 7 - Screen Fuzzy, then Blue Screenlue screen

Hi,

I need help... my Windows 7 is crashing FREQUENTLY. But I haven't found a similar description anywhere. The screen goes fuzzy as if the same image in the different colors but is offset... then bluescreen (also offset) and reboot. I can watch 2 videos on hulu, play a flash game for 30 minutes while listening to winamp, then when I switch to an open word file, it fuzzes (not like this everytime, just an example).

It doesn't seem to be heat related. It can happen within minutes of booting or after two days of running fine.

My device manager lists my monitor as Generic PnP, but the Windows 7 hardware display box shows it (correctly) as an LG L194WT.

All of the critical events are Kernel-Power events.

Other stuff - Windows won't recognize my USB hub. Everything that is plugged in directly is recognized and works (camera, video camera, external HDD), but nothing works through the hub.

This is a clean install (running about 3 weeks). I do have AVG, but only the free version.

MSI Kseries motherboard
Athlon 64XP 4000+
2 gig mem
NVIDIA GeForce 7300
LG L194WT monitor

Any assistance would be appreciated!

Upload Dump Files
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

Attachment 40527

Attachment 40528Thank you, I didn't know how to get the intfo you guys needed.

STOP 0x116 errors. More info on them here: BSOD Index

Basically there's 3 things that are likey to cause this error:
- driver corruption (uninstall the current drivers from Control Panel...Programs...Uninstall a program - then download and install the latest Windows 7 version of your video drivers from here: Drivers - Download NVIDIA Drivers )
- overheating (open up the case and check to see if the fan is working and that there's good air circulation and no dust obstructing the video card - DO NOT stick your fingers in the case).
- failing video card (you'll have to test with another video card)

Drivers loaded from the website with Windows 7 install.

Fan are all blowing and dust free

Anyone recommend a good video card? This one is a few years old.

Can you borrow a video card to test with, or can you buy one that you can return?

I described the most likely reasons for this - but they aren't the only reasons.
For example, low power from the Power Supply could conceivably cause this.
Also a problem with the motherboard, especially with the connection of the video card to it, could cause this.

OK, I dusted off all the parts again. I reseated the card. I also updated the drivers again (maybe I got the wrong ones). I don't have a spare video card.

The card never had any problems with Win XP (there were other issues that caused me to switch).

We'll try this for a bit.

I've included an updated minidump. There were 2 groups of 3 very closely spaced BSODs.

Would you mind terribly telling me they are the same issue? Is there any way I can tell from the event viewer what the stop code is?

Thanks

Attachment 40699

Another point I just thought of. This never happens while I'm playing RiskII (which is at a lower native resolution).

Same STOP codes (0x116)

To view the error numbers, use this free program: BlueScreenView - blue screen of death (STOP error) information.
There are some issues with the diagnostics in the program - so just use it for identifying the STOP code error.

There have been a lot of these sort of errors recently - so I'm leaning towards a compatibility issue with something recently released with Windows Update. But I can't say exactly what's causing it - do you recall installing any Windows Updates (or other updates) recently?