Random BSOD/Restart While Streaming Video

[dpm5049]

Hello, I've tried to read a bunch of older posts on similar issues to mine but haven't been able to find a solution. I built my pc about a month ago and have been getting some random bsod/restarts while streaming videos, but the problem only happens when I go to full screen (i can stream in a window forever). Also, it may crash after a few seconds of full screen streaming or may be fine for a few days of 2-4 hours per day. It has crashed with videos from Netflix, Youtube, and Megavideo. Also, sometimes I got a bsod and sometimes just a restart. When i got a bsod it was usually a 0x0...3b error. I saw some suggestions to try memtest86+ and did find that one of my sticks of ram would get 1/2 errors on test3 (sometimes in 2 passes sometimes not until 30/40 passes). The remaining stick seems to be fine, ran 11 hours and 28 full passes with no problems. When I took out the bad ram stick I got fewer errors, often just 1/2 per week vs. 1/2 per day but the problem persists and now I often dont get the bsod just a restart. The other main solution was to try older drivers but I have installed/uninstalled a bunch of versions of ati's drivers and always had the same problem. I attached the files from the sticky as well as the actual dump files (only rarely does it ever actually make one). The 9_06 dump file is from after the ram was removed (i think), the 9_04 is with both sticks. I would really appreciate any info you guys could provide.

AMD Phenom II X4 955 (3.2 GHz) - No Overclock
Gigabyte 880GMA-UD2H
4 GB (2x2GB) G.Skill Ripjaws DDR3 1600 (9-9-9-24-2T)
WD Caviar Blue SATA 750 GB 7200 RPM
Antec 430W PSU
LG Blu-Ray Drive, DVD-RW

 

[usasma]

Lot's of little things in the reports, but nothing that really stands out.

Your power supply is very low power, please ensure that everything possible is disconnected. Disconnect the power to your CD/DVD drive while we're testing.
Although I'm not a power supply expert, I'd have to wonder if it's a part of the problem.

Please update your Razer drivers as they are from 2006 and are a known cause of problems.

Please uninstall the Catalyst Control Center using Control Panel...Programs...Uninstall a program. If you need the program, install the latest version AFTER we're finished troubleshooting.

Please remove your USB 3.0 device and uninstall the drivers. I've read recently of instabilities with these drivers. As mentioned before, feel free to reinstall this AFTER we're finished troubleshooting

Please download new drivers for both your wired and wireless devices:

Realtek PCIe GBE Family Controller
RangeMax Next Wireless PCI Adapter

Uninstall the current drivers, then install the freshly downloaded drivers.

Should the BSOD's continue, please run Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 12:08:43.047 2010 (UTC - 4:00)
System Uptime: 0 days 2:08:56.655
BugCheck 1E, {ffffffffc0000005, fffff880072e3730, 0, 0}
Probably caused by : tcpip.sys ( tcpip!TcpPreValidatedReceive+67 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep  4 11:18:46.559 2010 (UTC - 4:00)
System Uptime: 0 days 0:11:31.777
BugCheck 3B, {c0000005, fffff80003383d6c, fffff8800725b120, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iexplore.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/FONT]

 

[dpm5049]

I uninstalled the catalyst software, removed the USB 3.0 driver and device from that port (it was my razer copperhead mouse but that is 2.0). I also removed and uninstalled all the razer drivers and software since i couldn't find updated drivers. The updated driver for the wireless is a broadcom 802.11n driver but it makes the card not work so i had to keep using either a rangemax driver or older broadcom one. As for the power supply, 430W should be way more than enough more my system with no graphics card or sound card. The newegg calculator recommends about 320W for my system. After doing all this i still got the system to crash, but now and this is what has done recently as well is it just freezes the screen and emits an annoying buzz from the speakers. Although, I was able to watch a 90 min netflix movie with no issue. When i got it to freeze again, i restarted and ran driver verifier as per your instructions. While streaming an NFL game, I got it to freeze again after about 1-2 mins and then I manually restarted it, but this time while loading windows i got a quick bsod (all i caught was a .....D5 for the error). When it restarted the 2nd time it loaded no problem. There were two dmp files in the minidump folder tho, so I have attached those. Hopefully these will lead to the problem. Thanks for the help so far.

 

[usasma]

One of the dump files is of size 0 - not of any use. But the other is a Verifier Enabled 0xD5.

It blames your Realtek Audio device. The most likely cause is the drivers, but it's possible that the device itself is broken. Replacing the drivers will tell us if it's the drivers or the device.

To do so, please...
- download the latest audio drivers for your system and OS from the Realtek website: Realtek
- uninstall the currently installed sound/audio drivers
- install the freshly downloaded drivers
- monitor for further BSOD's

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 22:42:07.803 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:17.036
BugCheck D5, {fffff98003536d60, 0, fffff88005aef34e, 0}
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+cf34e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]

 

[dpm5049]

Hi, I installed the latest Realtek drivers and everything seemed to be going well. Was streaming video with Verifier running for several hours. Then I got cocky and plugged in my Razer Copperhead --> instant crash as soon as it tried to install the driver. Driver Verifier does not like it all, it wont even boot to windows. It restarted several times, and I did see a Realtek bsod during one of the restarts. I was eventually able to get into safe mode and turn Verifier off. I got 6 bsod's total, but 2 were 0 kb, so I just uploaded the 4 with values. I have since uninstalled all the razer stuff and streaming has been working with Verifier running for an hour or two. I will keep checking tomorrow but figured you could check out the dump files to confirm razer or realtek or possibly realtek doesn't like it when razer is installed idk. I've also noticed my Netgear WN311b wireless N pci adapter is running slow lately sometimes down to 1.0 mbps (it has known win7x64 issues, but if you've heard of any decent fixes, let me know).

 

[usasma]

There is no need to keep Verifier running. In most cases we don't even run Verifier unless you have a BSOD that shows that it may help.

These show 2 different causes - your Audio card drivers and your Copperhead drivers. I wonder if there's a hardware issue with your audio card (and suggest trying another card). I know that there are some issues with the Razer drivers - so I'd keep my eye open for the latest drivers from the Razer website (yours are from 2009) also.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:36:34.471 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:19.094
BugCheck D5, {fffff98003356d60, 0, fffff88005b8fef6, 0}
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+d9ef6 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 21:03:10.412 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:17.035
BugCheck D5, {fffff98004e52d60, 0, fffff880059aaef6, 0}
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+d9ef6 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 20:57:56.876 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:47.499
BugCheck CD, {fffff9800de41000, 0, fffff800030804fa, 0}
*** WARNING: Unable to verify timestamp for copperhd.sys
*** ERROR: Module load completed but symbols could not be loaded for copperhd.sys
Probably caused by : copperhd.sys ( copperhd+16c9 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xCD
PROCESS_NAME:  razerhid.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 20:56:29.939 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:54.562
BugCheck CD, {fffff9800ee63000, 0, fffff800030804fa, 0}
*** WARNING: Unable to verify timestamp for copperhd.sys
*** ERROR: Module load completed but symbols could not be loaded for copperhd.sys
Probably caused by : copperhd.sys ( copperhd+16c9 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xCD
PROCESS_NAME:  razerhid.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]

 

[dpm5049]

I was running the system today and got a couple more errors. The latest one is from the realtek driver and I'm not sure about the first one. I just have integrated sound now but if both of these turn out to be realtek, I guess I need to try and get a sound card to determine the integrated audio is the problem. Do you have any recommendations on a cheap win7 x64 sound card. I just have basic computer speakers and dont plan on doing anything above a low-midrange 2.1 system anytime soon.

I also just checked the bios version and I currently have V2, there is currently a V3 and V4 update. I have not flashed the BIOS in a mobo before and am wondering if it is a recommended action to see if it helps this problem.

 

[usasma]

TURN DRIVER VERIFIER OFF NOW!!!
It will continue to generate BSOD's until you turn it off!!!
Do that BEFORE following the suggestions below.

*****************************************************

Disable the sound card in the BIOS and see if that stops the BSOD's.
Check to see if the drivers still load (easiest is an MSINFO32 report)
I don't know anything about sound cards - so I'd suggest checking reviews at places like Toms Hardware.

As for the BIOS, read the documentation on the updates. If it doesn't match a problem that you're having, then it's not necessary to update it. But, there are times when it's prudent to do this anyway - and that's usually when you're having issues that aren't solvable in other ways.

BIOS flashes are easy:
- Easy to do
- Easy to screw up and turn your motherboard into a brick

Should you choose to do it, follow the directions exactly. Triple check everything and then perform a dry run through in you mind before starting. Don't do it during times you're likely to lose power, and don't let any kids or animals in the room with you when doing it.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 18:26:02.521 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:17.128
BugCheck D5, {fffff98006dfad60, 0, fffff88005967ef6, 0}
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+d9ef6 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 16:02:14.564 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:19.798
BugCheck D5, {fffff98006df8d60, 0, fffff88005798ef6, 0}
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+d9ef6 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]

 

[dpm5049]

I turned verifier off, but the reason I was running it is that without it, the screen just freezes but doesn't give any information. I updated the BIOS to V4 since it was very easy and pretty safe for my mobo (dual bios so it has a backup) and gigabyte had a simple windows program that did it. I've been streaming more video to test the system and got it to freeze again this morning. I'm going to give disabling the sound a try and will report back.

 

[dpm5049]

I disabled the onboard sound in BIOS and then ran msinfo32 and the drivers weren't listed in any of the places i checked, system drivers or loaded modules, and the device isn't listed under sound anymore either. I do still have a realtek hdmi sound driver tho. I was streaming video for about 5 mins and the screen froze/went to lines of random color. I restarted the computer and found a minidump file (driver verifier was off). I have uploaded it and am curious to see what the cause is now. Thanks for you're help.

 

[usasma]

This is another Driver Verifier memory dump file and it blames your video card drivers. It occurred at 11:14am your time.

First, rename the Realtek HDMI sound driver from RtHDMIVX.sys to RtHDMIVX.BAK and reboot. Then check to make sure it hasn't spawned another instance of itself. Then try the streaming again to see if it causes another BSOD.

I'd also update your video drivers from the ATI website and then try this free video stress test:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Too much weird behavior in this. Please run SFC.EXE /SCANNOW from an Elevated (Run as administrator) Command Prompt. Let us know what it says when it's done.

Beyond that, I'd suggest preparing for a reinstall of Windows by backing up your stuff. Once that's done, re-enable your sound card and install Windows, all Windows Updates, and an antivirus (and that's ALL). Then test to see if you have problems with it that way. If not, then start adding your programs slowly - and keep an eye out for the bad behavior.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 11:14:00.908 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:07.516
BugCheck C4, {91, 2, fffffa8003999aa0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+62c90 )
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  plugin-contain[/font]

 

[dpm5049]

I renamed the driver file and uninstalled the sound card drivers, but still saw some of them in the drivers folder in windows/system32 so I deleted them. I also disabled the onboard audio in BIOS. Windows 7 still picks up some kind of HD audio tho and installs a device but without the rtk drivers that were giving me problems. I uninstall this but it re-downloads the drivers at every restart. Also, I still had the issue of it freezing while streaming with the audio disabled and after I got and installed a dedicated sound card which reviews state works well with win7 x64. I haven't been able to get an actual bsod recently tho, only freezes. Even with driver verifier I get nothing. I should be a getting a graphics card this Thursday to try out and see if that fixes it. I'd like to try the card before I re-install windows7 AGAIN.

I ran the sfc.exe/scannow and it returned that windows found no integrity violations.

I ran furmark for about a half hour at 1920x1080 and had no problems, there is no temp sensor to log the temp on the onboard graphics tho. Also, it only ran at like 4 fps (i suppose thats to be expected with just an integrated hd4250 w/ 250mb shared memory). 30 mins didn't seem like very long, but I was going by feel on the temperature and it seemed to level off at a point where on the heatsink it was uncomfortable to hold your finger there for more than 5 seconds.

Do you have suggestions as to how to keep this hd audio device from reinstalling everytime?

 

[dpm5049]

I just remembered the integrated graphics can do sound through hdmi and i thinks thats what the device is it is but I'm not sure.

 

[usasma]

Wait for the new video card.
Disable all the onboard stuff - then ensure that the drivers for the onboard stuff is removed/renamed.
Then install the drivers for the discreet sound and video cards.

We can work with freezes, but they're not as easy as what we're doing now.
Freeze diagnostics involves watching Task Manager for issues (and Process Explorer). We can also create dump files for freezes, but first we've gotta see what process is freezing.

This is how to do the Task Manager thing. But in this case you're just looking for anything out of the ordinary when the system freezes:

Task Manager:
Also, you can monitor the system for excessive resource consumption. To do this, open up Task Manager by right clicking on the Task Bar.
Then select the Processes tab.
Then select the "Show processes from all users" button (in the lower left)
Then select the View menu item, then select "Select columns"
In the Select columns window, place checkmarks next to I/O Reads and I/O Other.
Click OK to accept the changes.
Resize the Task Manager window so you can see the most of the columns.
Wait for the system to freeze.
Look at all of the columns to see if there's anything that looks excessively high - if so, let us know the Image name of the process.
FWIW - System Idle Process is supposed to have high CPU readings - anything else with high CPU readings is an issue.

 

[dpm5049]

I have to be in Full Screen view for the system to freeze so I can't look at the task manager at the same time.

 

[usasma]

Probably video - but that isn't enough to buy a new video card!
Note the time (from the system clock) that you go into Full Screen, then time the length of time it takes to freeze. Use this to determine the time that it froze at - and look that up in the event viewer.

Or, let us know the time and do this:

Event Viewer Log Files
Please provide us with copies of these 2 logfiles:
- Go to Start and type in "eventvwr.msc" (without the quotes and press Enter
- Expand the Windows Logs category by clicking on the arrow/+ sign to it's left
- Right click on the Application log and select "Save all events as" and name it Application
- Then, right click on the System log and select "Save all events as" and name it System
- Zip up the log files and upload/attach them with your next post.

NOTE: If the log files are too big to upload to the forums, please upload them to a free file hosting service - I recommend Windows Live SkyDrive - http://skydrive.live.com Then post the link to it in your topic.

 

[dpm5049]

Unfortunately I'm back even with the new (used) video card. I got a Sapphire Radeon HD 3870 but still got the freezing issue. I then did a format and re-install of windows 7. I only installed firefox and left the drivers as whatever windows found online. This still resulted in a freeze. I then updated the ati driver to the latest version and still got the problem. Next, I updated to Realtek audio drivers (I took out the pci sound card since it didn't help last time). Now I get a bsod with a 1E code. I have attached the dump file but don't really know where to go from here. All i can think that's left is a hardware issue with the Mobo or RAM. I tested the RAM tho the last two nights for about 8 hours each on memtest86+ and got no errors. I also ran Prime95 blend and furmark and had no issues with the either.

 

[usasma]

OK, let's go back to basics. Please run these free diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 23 11:59:54.102 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:30.787
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02a9fb74 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[dpm5049]

I've run memtest86+ for over 10 hours and had no errors. I also ran the WD hard drive extended test with no errors. However, I decided to try under-clocking my ram from 1600 to 1333 and that actually seems to have fixed the problem. 1333 is the default for the mobo, but in the BIOS it had the multiplier to enable 1600 (which is what the ram is rated at). Since the modification, I have been streaming video for about 12 hours with no problems at all. I even let it run overnight and it was still fine in the morning. Hopefully this continues, and if not, I'll be back on here.

I never got any memtest86+ errors with the 1600 setting, so I am not sure if the problem is with the RAM or the Mobo or a compatibility issue between them, but there is no noticeable performance difference in the two settings.

 

[usasma]

I never had any RAM issues with my P6T Deluxe mobo (and never even looked at the RAM settings).
I did have BSOD's when sleep/hibernating - fixed that with a P6T Deluxe V2 mobo.