Bought a new computer with a dual core processor, kept having random reboot problems, so reinstalled, played with a shed load of drivers and it seemed to work fine for several days.

Decided to reinstall today, with the drivers i had tested and were working stable and now i keep getting this error, and really cant find any information that strings together in an understandable way from microsoft site, so please help me.

Any further error messages?  I had something similar with some crappy USB drivers a while back.  

download memtest and check your ram out
http://www.memtest.org/

if it all comes back green then fair enough, but ive known the cheap ram pc builders sometimes like to use to be flaky.

Ill attempt to get it to bsod again and post the parameters here.

edit madmax its corsair ram so not so crappy

lol no worries  :mrgreen:

Oh i have had this system stable and running for a whole week, running games / videofiles etc with no problems, so i dont believe this is a hardware issue.

ive got a minidump file and sysdata if someone can help me work out how to read them ?

get hold of Hirens boot CD & run some tests.
I never f**kabout with new hardware as It can get arsey to get replaced after a short while.

I remember last week i downloaded an update which caused errors related to my realtek hd sound driver, thus i removed it again and it solved an issue i had before, this week a new update was realeased to fix the issue that update caused.

Ive now removed both of them as i have a feeling its that causing the issue.

Im sat typing this and no crash yet, ill leave the pc on tonight and we will see how it goes.

Crashed at 7.24am this morning, is totally random..

Source: System Error
Category: 102
Event ID: 1003

Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 020a0002, parameter4 88f0e708.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

did a system restore, installed drivers again, now i get this error

http://support.microsoft.com/kb/925922/en-us

tbh all this started happening after i did windows updates,

windows update this week fixed one last that had issue with realtek hd driver

i think its those 2 updates causing further issues

shucks might have worked out its actually a conflict between windoes and modem driver, lets see how it goes, used windbg and read the minidmp files.