This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BSOD-tastic!

t all started after the last update I installed. Didn't even bother to look at what it was, sadly. But my computer went strait to start-up fix and it couldn't be fixed. I tried restoring with a back up, but that would work for a second, then I would have to update again and it would be the same thing all over again. Finally I just got fed up and decided to format and refresh to factory settings. It worked. For a little while. Until I installed those updates again. But I did a memcheck with no errors and it seemed to be working fine after that. Until the BSODs started showing up about a minute or two after booting up. So here I am in safe mode trying to figure out what I'm supposed to do.

Oh, and I got IRQL_NOT_LESS_OR_EQUAL and then another that didn't even give any code. I'm lost here.

This thread was automatically locked due to age.

0 wickedkittenz over 12 years ago

HI Cowboy
:( BSOD is not fun, but you came to the right place. :)
Could you provide more information please.
What OS,
What Service Packs,
Are you talking about Endpoint and if so which version did you have installed,
Are you updating from Sophos directly or from a ecntral server?
Are you running any other security products, microsoft essentials, firewalls, etc?
What are the configurations in AV, do you delete threats and suspicious files, or adware/PUA's?
Hope to help soon. :)
:17191
Cancel
Vote Up 0 Vote Down

Cancel
0 Placebo over 12 years ago

I have seen IRQL_NOT_LESS_OR_EQUAL once.
It was related to a defective DVD drive.
Only once I have seen a BSOD (PAGE_FAULT_IN_NONPAGED_AREA ) that was not related to a hardware problem. That was the Microsoft update (MS10-015 ) in combination with the TDL3 rootkit:
http://www.prevx.com/blog/143/BSOD-after-MS-TDL-authors-apologize.html
So I would fist check hardware and after that for MBR rootkits.
:17195
Cancel
Vote Up 0 Vote Down

Cancel
0 jak over 12 years ago

Hi,

I would suggest as a first step in identifying any such problem:

1. Generate a memory dump file. A full dump is ideal (the largest) but even a mini dump might help. http://support.microsoft.com/kb/254649 has some info on where to obtain the dmp files from or configure the machine to create them.

2. Download and install WinDbg (http://msdn.microsoft.com/en-us/windows/hardware/gg463009 )

Ideally configure the symbols path. http://msdn.microsoft.com/en-us/windows/hardware/gg462988

Which essentially comprises of adding:

SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

to the dialog under: "File" - "Symbols File Path"

3. Once installed open WinDbg and go to "File" - "Open Crash dump", choose the create dmp file mentioned in 1.

4. type in the command:
!analyze -v

5. This will give Microsoft's best guess as to which driver caused the exception. It's not always right but it's a good start, you can then try updating the suspected driver or even removing it if not required etc..

Feel free to post the output of that command here it might help.

Hope that helps.

Regards,

Jak
:17221
Cancel
Vote Up 0 Vote Down

Cancel