Re: BSOD again

Thanks for the speedy response :) i have hopefully updated the right driver ethernet has changed so thats a newer one,(i downloaded the killer drivers only option, hoping it did them all) i also had an ME driver i updated to no idea if thats connected to crash or not, hope it is as simple as that this time round. Thanks again hope to not be back despite you all being so damn nice :)

Re: BSOD again

one more, i have had BSOD every since i had the comp, they come and go, this was a single crash this time, a few weeks later. I can go a couple of months between crashes or i can have 2 or 3 on a trot then stop. I have learned to live with it as 2 years of the pattern has not really led me any where. Still if you see omething it is always appreciated.

Re: BSOD again

The first parameter indicates that an invalid memory address was accessed. The exception seems to have been raised when the internal clock was being reset. The exception record doesn't seem to have been captured by the debugger correctly either.

However, judging by the bugcheck parameters, we can assume that the operation was a read operation and the address seems to be invalid too. The third parameter indicates a read operation and the fourth parameter provides the address which was being referenced.

Did you update the network driver properly? It appears to be in the raw stack just before the crash occured.