intermittent hardware bsod week time error codes

[burgerman]

A winows machine occasionally reboots itself and in the event log is shown these error codes. the machine uses norton 360v3 if thats a clue

If anybody has any tips on how to easily recognise particular silver bullets on this stuff then please share !



Error code 00000050, parameter1 ffffffdf, parameter2 00000000, parameter3 00000000, parameter4 00000000.





Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 00000000, parameter4 e11a3968.





Error code 1000008e, parameter1 c0000005, parameter2 bf80dd21, parameter3 a99ce440, parameter4 00000000.

 

[sabashuali]

I used to get loads of BSOD's and eventually narrowed it down to bad RAM module.
If you have more than one memory module, I would try each on its own and run memtest for a number of hours (maybe overnight) or just operate your PC as normal for a while. If all is good the RAM module should be OK... move on to the next one. It took me a number of days, but I eventually found the rotten bugger (I had four modules to go through...)

In case you have only one module and it shows errors, replace it.

You can always try and search for the stop code and then try and see if you can decipher them with the "help" of Microsoft. More details here -
How to read the small memory dump files that Windows creates for debugging

Saying all that BSOD's can happen for a myriad of reasons. From software to hardware conflicts. Sorry that there is no easy answer.... that's how it goes with Windows... trial end error baby ;)