Screen freezes and BSODs

[RageBoXx]

This is very weird problem. I can't figure out what's causing it.

Usually, if I'm watching a Youtube video, and then I open a new tab, and I'm browsing something else while listening to the music my screen would first freeze up. And by freeze up, I don't mean in the usual sense. There would be many, many different coloured and tiny pixels all over the screen. For a little while I could even move my mouse, even though clicking anything doesn't work. And then I would have to restart the PC. That's the first case.

The second case is that I would be using my PC and then it just BSODs.

Now the weird thing is, I can play a graphically intense game - like Crysis, for literally hours, and nothing would happen. No BSODs, no freezes. I could watch full HD movies without this happening as well. It's almost always Youtube, and recently I noticed when I'm using Dreamscene as well.

I was using an XP until like last month. It used to happen on that as well. And then I bought Win7 x64. And it still happens.

Please help! Which part of the PC is causing this? I've attached the dmp file as well.

This is what it said on one of the error reports:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFF88011E00000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF8800F212BB0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1


I've run chkdsk multiple times with no errors. I've run the Windows memory diagnostic tool several times as well, choosing the most intensive options.

I have a single Kingston 800Mhz 2GB DDR2 stick.
450W PSU. Core 2 Duo E7400 Wolfdale 2.8Ghz.
nVidia DDR3 GT250 with 1GB vRam
Win7 x64
Intel DG41RQ MOBO

 

[Route44]

Your issue is memory corruption.


See the link below and follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


Link: https://www.techspot.com/vb/topic62524.html


* Get back to us with the results.


*** If Memtest shows no errors then find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?

 

[RageBoXx]

I let Memtest86+ run for the entire night. It had completed 9 passes.

No errors. So I checked the voltage - it's supposed to be 1.8. And it is 1.8 in my BIOS.
So what could be wrong with it?

 

[Route44]

I reread your minidump and again it says memory corruption. However, re-reading your post where you stated "There would be many, many different coloured and tiny pixels all over the screen."

This sounds like artifacting and can be caused by overheating or a failing video card. And video cards have RAM and it can fail causing BSODs. I am wondering if you have a heat issue or if the fan is only working at certain times.

Still I've never ever seen a minidump file specifically cite memory corruption and have it mean VRAM.

*** Check to see if the card is properly set.

 

[RageBoXx]

Okay. I got a new BSOD. Here's what this one says:


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80020fc4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f187f9c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

FAULTING_IP:
nvlddmkm+112f9c
fffff880`0f187f9c 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02ec5988 fffff880`0fd41ef8 : 00000000`00000116 fffffa80`020fc4e0 fffff880`0f187f9c 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ec5990 fffff880`0fd41c02 : fffff880`0f187f9c fffffa80`020fc4e0 fffffa80`03aecc00 fffffa80`03ad8010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02ec59d0 fffff880`0f00ff07 : fffffa80`020fc4e0 00000000`00000000 fffffa80`03aecc00 fffffa80`03ad8010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02ec5a00 fffff880`0f039b75 : 00000000`ffffffff 00000000`0002146f 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02ec5ae0 fffff880`0f0382bb : 00000000`00000102 00000000`00000000 00000000`0002146f 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02ec5b10 fffff880`0f00b2c6 : ffffffff`ff676980 fffffa80`03ad8010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02ec5bb0 fffff880`0f037e7a : 00000000`00000000 fffffa80`03c27850 00000000`00000080 fffffa80`03ad8010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02ec5cc0 fffff800`03b60a86 : 00000000`fffffc32 fffffa80`03af8060 fffffa80`018c1040 fffffa80`03af8060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02ec5d00 fffff800`03899b06 : fffff800`03a35e80 fffffa80`03af8060 fffff800`03a43c40 fffff880`0123d534 : nt!PspSystemThreadStartup+0x5a
fffff880`02ec5d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+112f9c
fffff880`0f187f9c 4883ec28 sub rsp,28h

SYMBOL_NAME: nvlddmkm+112f9c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c0d6fd7

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner



I did check to see if the video card was set in properly.

 

[Route44]

It could be the video card itself is failing. See this link: http://www.microsoft.com/communitie...012-bd0f-287a5082d1da&lang=en&cr=US&sloc=&p=1

Also, test your Video RAM: http://majorgeeks.com/Video_Memory_Stress_Test__d5896.html

 

[RageBoXx]

Crap, I don't get this. I can play Crysis at 1280x768, with everything on high. But I can't watch a Youtube video without the computer giving me a BSOD.

I downloaded that app. I'll run the tests and post the results here.

Thanks dude!

 

[Route44]

This is sounding more like an internet issue yet much points to your video card plus the memory corruption reads. Interesting combination of error issues indeed.

 

[RageBoXx]

Okay, I ran VMT. And, well. Here's the result:

[6/18/2010 2:58:20 PM] Test started for "Primary Display Driver (NVIDIA GeForce GT 240)"...
Trying 16bpp RGB:565 mode...OK
TEST FAIL (Code: 8876017C)
Trying 16bpp RGB:555 mode...OK
TEST FAIL (Code: 8876017C)
Trying 16bpp BGR:565 mode...NOT SUPPORTED (Code: 80004001)
Trying 32bpp RGB:888 mode...OK
TEST FAIL (Code: 8876017C)
Trying 32bpp BGR:888 mode...NOT SUPPORTED (Code: 80004001)
NO PASS COMPLETED

On top of that, I get a warning message saying that Windows has run out of memory and that I need to close a certain program to continue. And that program is VMT. WTF. I don't get it. How can I have run outta memory. I quit every single application and unneeded service before trying this test. Plus I have 1gb of vRAM.
=S

 

[Route44]

Certain games or programs will cause memory leaks. It has nothing to do with your memoy per se or the amount. If you can try installing your video card in another system and see if you get the same reasults. Aloso, if possible install another card in your system and check the results.

 

[RageBoXx]

I don't have any other cards with me to try 'em out. And all my friends have either netbooks or laptops. And the ones who do have desktops won't be comfy with me trying my card in their rig.

Here's what I tried: I went in safe mode and I opened up two separate windows of Google Chrome. In the first window I opened about 4 tabs of just Youtube videos. In the second window I opened about 6 tabs; myspace, facebook, etc, Then I opened VLC and played a full HD movie. I kept this for about 15 mins, all the while doing stuff with it like minimizing, maximizing, locking the computer, switching user, switching back, etc. And nothing happened. It didn't freeze nor did it BSOD.

What does this mean? Is it something to do with my software then? I'm confused. =S

Thanks for helping me out so far and taking the time mate!

 

[Route44]

Windows 7 and Memory Leaks: http://arstechnica.com/microsoft/ne...ails-windows-7-memory-leaks-hangs-freezes.ars

Again, memory leakage has nothing to with hardware but software.

 

[RageBoXx]

Hokay I'm downloading the hotfix now. Thanks! I'll install, see what happens and post back here.

However, these screen freezes and BSODs were there in my Win XP system as well - the exact same way: usually while watching a youtube video (or sometimes megavideo, etc), lots of tiny pixels all over the screen, and it affects the sound as well (it goes extremely slow) until it just freezes. In the end I'd either restart, or I'd get a BS. And then I got me a copy of Win 7. But it's still the same. Bleugh.

 

[Route44]

Post your latest Blue Screens. It sure seems like you might have more than one issue going on here. What make is your PSU and how much wattage?

Can you link us to your motherboard?