crashing to blue screen

my computer has been resetting it's self about once a month for about a year now after going to a blue screen. The blue screen says something about a serious error and windows must shut down. Problem is it's up for about 2 seconds and then the computer restarts so i can't read it. i have also noticed it says the error is to do with a USB driver or something. when my computer comes back on i tend to get this message(below) from Microsoft although this isn't always the case.
http://oca.microsoft.com/en/response...c8b8f20&SID=10
it tends to restart when playing games or burning DVD's. Once it wouldn't burn a DVD without crashing until i turned hardware acceleration off and then it was fine.
Any ideas people?

Looking at your specs i can't see why CPU heavy processes would give you a BSOD, i suppose you could try testing the RAM....Memtest

Do you have all the latest Windows Updates?

Liam

i have windows update enabled and am up to date. i gave you the link that widows error checking normally gives me but about 30% of the time it tells me to check my memory. Have done this and occasionally it comes up with an error when testing. i will run it again and see if i can give you more info.

ok just ran mem test and all is not fine :) . test one came up with 1 error and then test 5 came up with 4921 error!!! sounds like a hell of a lot to me. but i can't seem to find out any more info than that. so where do i go from here?

Go Here And click "Troubleshooting Memory Errors"


Liam

well the only thing i got out of that was i should run the test a module at a time to see if it is one in particular causing the problems which i will do at another time.
also i read this;
"There are some systems that cause Memtest86 to be confused about the size of memory and it will try to test non-existent memory. This will cause a large number of consecutive addresses to be reported as bad and generally there will be many bits in error"
well i had 4921 errors in about 5 seconds all in one test. so that may be the cause of that.

You can also try Windows Memory Diagnostics, the link is in my sig. Test with one stick in at a time, if any of them report even one error I would get that stick replaced. Just cant trust dodgy ram, it can cause a multitude of hard to troubleshoot problems.

Hong