I hardly seem to find a driver that is signed, seems microsoft doesn't verify too many pieces of hardware. Maybe that responsibility lies with the companies. I know WDM is the program used to control you desktop, so maybe the error lied in bad memory access having to do with the video card? Does it share memory with your comp? It seems if you had bad drivers it could be accessing the system memory out of place.
That is a thought- it is indeed shared memory, and could have been cannon balling the 'pool'. I just don't (and never will) know why it waited till now to start causing BSoDs.
Well, odd thing is, laptop has been up all day without further error. *shrug* windows :\
Worse comes to worse, I could revert the cleaned registry entries. My initial thought when using the cleaner was 'I know these can be bad- lets make a backup and see what happens'. Turns out nothing bad happened for over a month. Can't really say I think that was the issue now. Though if it does come to it, I can put it back. I think at the time I'd been hoping it would cure the ambiguous graphics card error/crash. It didn't. But it has been cured now.
Comments 4
I know WDM is the program used to control you desktop, so maybe the error lied in bad memory access having to do with the video card? Does it share memory with your comp? It seems if you had bad drivers it could be accessing the system memory out of place.
Reply
Reply
Reply
(The comment has been removed)
Worse comes to worse, I could revert the cleaned registry entries. My initial thought when using the cleaner was 'I know these can be bad- lets make a backup and see what happens'. Turns out nothing bad happened for over a month. Can't really say I think that was the issue now. Though if it does come to it, I can put it back. I think at the time I'd been hoping it would cure the ambiguous graphics card error/crash. It didn't. But it has been cured now.
Will see if/what/when error occurs next?
Reply
Leave a comment