Hey all. I've been letting my roommate borrow my computer and, as roomies are prone to do, he managed to get a BSOD on every startup within a week. The error was as follows:
STOP: Driver IRQL not less or equal. 0x000000D1
It then referenced NDIS.sys and some particular addresses.
Now, I managed to fix this problem. In a startling display of foresight on my part, I created a separate account for my roommate, rather than letting him use mine. I deleted his account after backing up his files, and the problem went away. But before doing that, I spent almost an hour googling this error. I ended up with almost nothing, except "you probably installed something bad, like a wrong driver." Well, I know that I did not, and my roommate does not remember doing so. I tried googling the specific address noted in NDIS.sys, but that didn't return anything.
So, my question is, how would I have gone about fixing this error if simply deleting his account had not done it? I tried bootlogging but the file never got created--the BSOD somehow kept it from doing so. I ran eventvwr but with similar results--because i never got into Windows, the error I was encountering was never logged. So, I still don't know what exactly was causing the problem, except that it was something my roommate did. How would I have gone about fixing it otherwise? It gave me specific addresses in NDIS--what would have been the next step? I'm just trying to figure this out so I can actually fix this problem next time.
STOP: Driver IRQL not less or equal. 0x000000D1
It then referenced NDIS.sys and some particular addresses.
Now, I managed to fix this problem. In a startling display of foresight on my part, I created a separate account for my roommate, rather than letting him use mine. I deleted his account after backing up his files, and the problem went away. But before doing that, I spent almost an hour googling this error. I ended up with almost nothing, except "you probably installed something bad, like a wrong driver." Well, I know that I did not, and my roommate does not remember doing so. I tried googling the specific address noted in NDIS.sys, but that didn't return anything.
So, my question is, how would I have gone about fixing this error if simply deleting his account had not done it? I tried bootlogging but the file never got created--the BSOD somehow kept it from doing so. I ran eventvwr but with similar results--because i never got into Windows, the error I was encountering was never logged. So, I still don't know what exactly was causing the problem, except that it was something my roommate did. How would I have gone about fixing it otherwise? It gave me specific addresses in NDIS--what would have been the next step? I'm just trying to figure this out so I can actually fix this problem next time.
Facebook
Twitter