3

I keep getting a blue screen of death (memory parity check error) when trying to watch the olympics online at ctv.ca (silverlight player). I can watch for max 10mins then it goes down.

So to diagnose the problem I ran memtest86 and the test passed with no errors. Then I tried prime95 (blend) for an hour and had no problems. I tried using a couple different RAM modules and that didn't help.

What components are most likely causing the BSOD? What else can I do to figure out what the problem is/solve it? If I need to replace parts, what order should I do it in?

OS: Vista Business 64bit
MB: Asus p5n32e sli plus
RAM: Mushkin Silverline Frostbyte PC-6400 (996557)
CPU: Core 2 Duo E8400
GPU: ATI HD4800

Kells
  • 1,018

6 Answers6

4

Nowadays it happens mostly because of broken hardware or buggy video drivers.

geek
  • 10,674
1

You could use Blue Screen Viewer to find the culprit software or driver

fluxtendu
  • 7,219
1

What browser version are you using with silverlight? Did you recently install a new version of silverlight player? You can also take a look in the silverlight forums and submit a bug if necessary http://forums.silverlight.net/forums/28.aspx. You should try ripping out silverlight and reinstalling it and see if it resolves your issue.

ryanyama
  • 51
0

Make sure to choose the correct memory voltage setting in the BIOS, speaking of which, update the BIOS to the latest version if necessary.

0

A BSOD is definitely a crashing driver. Nothing else can actually stall the kernel. However, getting a BSOD actually is a good thing, since a BSOD means that the kernel actually cought the problem and stored a crashdump somewhere on your system that you can use to find the actual cause of the problem.

Note that while the BSOD was caused by a crashing driver this does not necessarily mean that the driver is faulty. Probably, some other software was just using the driver incorrectly and thereby made it crash. With some digging, this is usually recorded in the crashdump, too.

Reading the crashdump however is rather difficult. Sysinternals has some tool to read crashdumps but honestly, this is not something a non-programmer would want to use. Perhaps someone else can point you to some usable software to that end.

bastibe
  • 3,912
0

You can use tools to examine the MEMORY.DMP file to determine route cause of the crash dump. All you need are the tools & symbols.

http://www.microsoft.com/whdc/devtools/debugging/default.mspx