The failure profile of most hardware is that the failures are generally within the first 30 hours of operation.
then a year later as cheap fans tend to wear out, then the spinning hard drive start to give errors until you start to get general electronics parts to fail (3 to 5 years).
I would say, in general after your hardware is properly setup and done with its "burn in period"
You get software errors, most of them in the device drivers.
About 95 % of the bugged drivers are 3rd party drivers that Microsoft does not distribute. This is not a reflection of how great Microsoft is at creating drivers but reflects that a Microsoft driver is updated directly by Windows update while a third party driver requires you to figure out the problem and locate the proper update and install it yourself. Basically if several million machines hit a bug in a microsoft driver they get several million automatic windows error reports and some poor SOB at microsoft has a bad day until they roll out a fix via the windows update.
jddg5wa :
johnbl :
put the actual memory.dmp file on a cloud server like skydrive and give it public access.
I will take a quick look at it in a windows debugger.
most often it will be software drivers if you get a blue screen. When you get different bugcheck codes it is most often one driver corrupting memory of the driver that is using memory next to the first driver. Windows tries to load the drivers in a different order on each boot so the driver that does the corruption get to mess over a different driver on each boot. The driver that gets messed up calls the bugcheck, that is why is can be different each time.
Thanks, will do. Except for now a dmp has not been created. I was following a tutorial on how to make sure a dmp is created and found out the page file was set to small. I hope it will create a dmp next time but I can't say when that will be. As I mentioned the crashes are random and quiet sporadic.
Anyways if a dmp is created next time it crashes I will post it here.
Also is the randomness a sign that the issue is not hardware?