By default the system automatically restarts upon a BSOD and you may miss the information that's printed on the screen. If you'd like to confirm the actual STOP error you are getting visually, then you need to change a setting in Windows XP and Windows Server 2003. If you end up in the unfortunate situation where you are experiencing a STOP 0XA BSODs, what can you do about it? In Part 1 we looked at common causes for IRQL_NOT_LESS_OR_EQUAL BSODs. run a memory tester application, remove unnecessary peripherals etc) Do some basic hardware troubleshooting first (e.g. ![]() the bugcheck is different each time), then it's possible that your machine has a hardware issue. ![]() Update 2: If you are getting random STOP numbers each time your machine blue screens (e.g. ![]() This can be handy if you are getting STOP 0xA crashes, but the faulting stack is different/corrupt each time. Update: I have now added Part 3 - where I cover enabling the Driver Verifier tool.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |