![]() If you aren't doing kernel or driver development, I don't think this has much use to you (other than to perhaps stress your drivers and determine if any are unstable.) This is because it requires that you understand how to analyze a core dump. Typically fatal system errors are generated by the stressed drivers in the test environment, producing core dumps which can be analysed and debugged immediately without stressing, intermittent faults would occur in the field, without proper troubleshooting facilities or personnel. The verifier works by forcing drivers to work with minimal resources, making potential errors that might happen only rarely in a working system manifest immediately. Once enabled, it monitors and stresses drivers to detect illegal function calls or actions that may be causing system corruption. It also has a slightly more detailed summary of how it works: It can simulate certain conditions such as low memory, I/O verification, pool tracking, IRQL checking, deadlock detection, DMA checks, IRP logging etc. Well, you've already stated how it works at the most basic level (by replacing Windows system calls.) The link you posted has a pretty good explanation of what it does, and what it can test:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |