DOCSLIB.ORG

Symdrive: Testing Drivers Without Devices

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Symdrive: Testing Drivers Without Devices SymDrive: Testing Drivers without Devices Matthew J. Renzelmann, Asim Kadav and Michael M. Swift Computer Sciences Department, University of Wisconsin–Madison mjr,kadav,swift @cs.wisc.edu { } Abstract modes. Device-driver development and testing is a complex and Static analysis tools such as Coverity [17] and Mi- error-prone undertaking. For example, testing error- crosoft’s Static Driver Verifier [31] can find many bugs handling code requires simulating faulty inputs from the quickly. However, these tools are tuned for fast, rela- device. A single driver may support dozens of devices, tively shallow analysis of large amounts of code and there- and a developer may not have access to any of them. Con- fore only approximate the behavior of some code features, sequently, many Linux driver patches include the com- such as pointers. Furthermore, they have difficulty with ment “compile tested only.” bugs that span multiple invocations of the driver. Hence, SymDrive is a system for testing Linux and FreeBSD static analysis misses large aspects of driver behavior. drivers without their devices present. The system uses We address these challenges using symbolic execution symbolic execution to remove the need for hardware, and to test device drivers. This approach executes driver code extends past tools with three new features. First, Sym- on all possible device inputs, allows driver code to execute Drive uses static-analysis and source-to-source transfor- without the device present, and provides more thorough mation to greatly reduce the effort of testing a new driver. coverage of driver code, including error handling code. 2 Second, SymDrive checkers are ordinary C code and ex- DDT [26] and S E[14, 15] previously applied symbolic ecute in the kernel, where they have full access to kernel execution to driver testing, but these systems require sub- and driver state. Finally, SymDrive provides an execution- stantial developer effort to test new classes of drivers and, tracing tool to identify how a patch changes I/O to the in many cases, even specific new drivers. device and to compare device-driver implementations. In This paper presents SymDrive, a system to test Linux applying SymDrive to 21 Linux drivers and 5 FreeBSD and FreeBSD drivers without devices. SymDrive uses drivers, we found 39 bugs. static analysis to identify key features of the driver code, such as entry-point functions and loops. With this analy- 1 Introduction sis, SymDrive produces an instrumented driver with call- Device drivers are critical to operating-system reliability, outs to test code that allows many drivers to be tested with yet are difficult to test and debug. They run in kernel no modifications. The remaining drivers require a few mode, which prohibits the use of many runtime program- annotations to assist symbolic execution at locations that analysis tools available for user-mode code, such as Val- SymDrive identifies. grind [34]. Their need for hardware can prevent testing We designed SymDrive for three purposes. First, a altogether: over two dozen driver Linux and FreeBSD driver developer can use SymDrive to test driver patches patches include the comment “compile tested only,” in- by thoroughly executing all branches affected by the code dicating that the developer was unable or unwilling to run changes. Second, a developer can use SymDrive as a de- the driver. Even with hardware, it is difficult to test error- bugging tool to compare the behavior of a functioning handling code that runs in response to a device error or driver against a non-functioning driver. Third, SymDrive malfunction. Thorough testing of failure-handling code can serve as a general-purpose bug-finding tool and per- is time consuming and requires exhaustive fault-injection form broad testing of many drivers with little developer tests with a range of faulty inputs. input. Complicating matters, a single driver may support SymDrive is built with the S2E system by Chipounov dozens of devices with different code paths. For exam- et al. [14, 15] , which can make any data within a vir- ple, one of the 18 supported medium access controllers tual machine symbolic and explore its effect. SymDrive in the E1000 network driver requires an additional EEP- makes device inputs to the driver symbolic, thereby elim- ROM read operation while configuring flow-control and inating the need for the device and allowing execution on link settings. Testing error handling in this driver requires the complete range of device inputs. In addition, S2E en- the specific device, and consideration of its specific failure ables SymDrive to further enhance code coverage by mak- USENIX Association 10th USENIX Symposium on Operating Systems Design and Implementation (OSDI ’12) 279 ing other inputs to the driver symbolic, such as data from (iii) efficiency. First, SymDrive must be able to find bugs the applications and the kernel. When it detects a failure, that are hard to find using other mechanisms, such as nor- either through an invalid operation or an explicit check, mal testing or static analysis tools. Second, SymDrive SymDrive reports the failure location and inputs that trig- must require low developer effort to test a new driver and ger the failure. therefore support many device classes, buses, and operat- SymDrive extends S2E with three major components. ing systems. Finally, SymDrive must be fast enough to First, SymDrive uses SymGen, a static-analysis and code apply to every patch. transformation tool, to analyze and instrument driver code 2.1 Symbolic Execution before testing. SymGen automatically performs nearly all the tasks previous systems left for developers, such as SymDrive uses symbolic execution to execute device- identifying the driver/kernel interface, and also provides driver code without the device being present. Symbolic hints to S2E to speed testing. Consequently, little effort execution allows a program’s input to be replaced with a is needed to apply SymDrive to additional drivers, driver symbolic value, which represents all possible values the classes, or buses. As evidence, we have applied SymDrive data may have. A symbolic-execution engine runs the to eleven classes of drivers on five buses in two operating code and tracks which values are symbolic and which systems. have concrete (i.e., fully defined) values, such as initial- Second, SymDrive provides a test framework that al- ized variables. When the program compares a symbolic lows checkers that validate driver behavior to be writ- value, the engine forks execution into multiple paths, one ten as ordinary C code and execute in the kernel. These for each outcome of the comparison. It then executes each checkers have access to kernel state and the parameters path with the symbolic value constrained by the chosen and results of calls between the driver and the kernel. A outcome of the comparison. For example, the predicate checker can make pre- and post-condition assertions over x>5 forks execution by copying the running program. In one copy, the code executes the path where x 5 and the driver behavior, and raise an error if the driver misbe- ≤ haves. Using bugs and kernel programming requirements other executes the path where x>5. Subsequent com- culled from code, documentation, and mailing lists, we parisons can further constrain a value. In places where wrote 49 checkers comprising 564 lines of code to en- specific values are needed, such as printing a value, the force rules that maintainers commonly check during code engine can concretize data by producing a single value reviews, such as matched allocation/free calls across entry that satisfies all constraints over the data. points, no memory leaks, and proper use of kernel APIs. Symbolic execution detects bugs either through ille- Finally, SymDrive provides an execution-tracing mech- gal operations, such as dereferencing a null pointer, or anism for logging the path of driver execution, including through explicit assertions over behavior, and can show the instruction pointer and stack trace of every I/O op- the state of the executing path at the failure site. eration. These traces can be used to compare execution Symbolic execution with S2E. SymDrive is built on a across different driver revisions and implementations. For modified version of the S2E symbolic execution frame- example, a developer can debug where a buggy driver di- work. S2E executes a complete virtual machine as the verges in behavior from a previous working one. We have program under test. Thus, symbolic data can be used any- also used this facility to compare driver implementations where in the operating system, including drivers and ap- across operating systems. plications. S2E is a virtual machine monitor (VMM) that We demonstrate SymDrive’s value by applying it to 26 tracks the use of symbolic data within an executing virtual drivers, and find 39 bugs, including two security vulner- machine. The VMM tracks each executing path within the abilities. We also find two driver/device interface viola- VM, and schedules CPU time between paths. Each path tions when comparing Linux and FreeBSD drivers. To the is treated like a thread, and the scheduler selects which best of our knowledge, no symbolic execution tool has ex- path to execute and when to switch execution to a differ- amined as many drivers. In addition, SymDrive achieved ent path. over 80% code coverage in most drivers, and is largely S2E supports plug-ins, which are modules loaded into limited by the ability of user-mode tests to invoke driver the VMM that can be invoked to record information or to entry points. When we use SymDrive to execute code modify execution. SymDrive uses plugins to implement changed by driver patches, SymDrive achieves over 95% symbolic hardware, path scheduling, and code-coverage coverage on 12 patches in 3 drivers. monitoring. 2 Motivation 2.2 Why Symbolic Execution? The goal of our work is to improve driver quality through Symbolic execution is often used to achieve high cover- thorough testing and validation.
Load more

Recommended publications
  • TK Backman, Jason Yang, SW Development at MS
    T.K. Backman Jason Yang [email protected] [email protected] Principal Development Lead Principal Development Lead Debugging and Tools Group Analysis Technologies Team Windows Engineering Desktop Windows Engineering Desktop Microsoft Corporation Microsoft Corporationnnn Code on a massive scale Developers on a massive scale Tight constraints on schedules University of Washington 3/2/2011 2 ◦ Company structure Why the world is not just about developers ☺ ◦ Innovation strategy How we actually improve software over time ◦ Dynamic tension When people are involved, everything changes ◦ Development cycles How we build software products in cycles ◦ Program analysis How we push quality upstream ◦ Windows engineering system How we build large-scale products University of Washington 3/2/2011 3 ◦ Total size: ~89,000 employees ◦ Windows & Office – “perfect org structure” PM – program managers Dev – software developers Test – software developers in test ◦ Around 1000 PM+Dev+Test feature teams on 100s of products University of Washington 3/2/2011 4 ◦ Team size: ~10,000 employees ◦ Sales & marketing ◦ Project managers / product managers ◦ 30 feature teams 1500 Devs 1500 Testers 1000 PMs ◦ Customer support engineers ◦ Build engineers University of Washington 3/2/2011 5 “I often say that when you can measure what you are speaking about, and express it in numbers, you know something about it; but when you cannot measure it, when you cannot express it in numbers, your knowledge is of a meager and unsatisfactory kind; it may be the beginning
    [Show full text]
  • Scheduling, Thread Context, and IRQL
    Scheduling, Thread Context, and IRQL December 31, 2020 Abstract This paper presents information about how thread scheduling, thread context, and a processor’s current interrupt request level (IRQL) affect the operation of kernel- mode drivers for the Microsoft® Windows® family of operating systems. It is intended to provide driver writers with a greater understanding of the environment in which their code runs. A companion paper, “Locks, Deadlocks, and Synchronization” at http://www.microsoft.com/whdc/hwdev/driver/LOCKS.mspx, builds on these fundamental concepts to address synchronization issues in drivers. Contents Introduction ....................................................................................................................... 3 Thread Scheduling ............................................................................................................ 3 Thread Context and Driver Routines .................................................................................. 4 Driver Threads .................................................................................................................. 5 Interrupt Request Levels .................................................................................................... 6 Processor-Specific and Thread-Specific IRQLs .............................................................. 8 IRQL PASSIVE_LEVEL ............................................................................................ 8 IRQL PASSIVE_LEVEL, in a critical region ..............................................................
    [Show full text]
  • Run-Commands-Windows-10.Pdf
    Run Commands Windows 10 by Bettertechtips.com Command Action Command Action documents Open Documents Folder devicepairingwizard Device Pairing Wizard videos Open Videos Folder msdt Diagnostics Troubleshooting Wizard downloads Open Downloads Folder tabcal Digitizer Calibration Tool favorites Open Favorites Folder dxdiag DirectX Diagnostic Tool recent Open Recent Folder cleanmgr Disk Cleanup pictures Open Pictures Folder dfrgui Optimie Drive devicepairingwizard Add a new Device diskmgmt.msc Disk Management winver About Windows dialog dpiscaling Display Setting hdwwiz Add Hardware Wizard dccw Display Color Calibration netplwiz User Accounts verifier Driver Verifier Manager azman.msc Authorization Manager utilman Ease of Access Center sdclt Backup and Restore rekeywiz Encryption File System Wizard fsquirt fsquirt eventvwr.msc Event Viewer calc Calculator fxscover Fax Cover Page Editor certmgr.msc Certificates sigverif File Signature Verification systempropertiesperformance Performance Options joy.cpl Game Controllers printui Printer User Interface iexpress IExpress Wizard charmap Character Map iexplore Internet Explorer cttune ClearType text Tuner inetcpl.cpl Internet Properties colorcpl Color Management iscsicpl iSCSI Initiator Configuration Tool cmd Command Prompt lpksetup Language Pack Installer comexp.msc Component Services gpedit.msc Local Group Policy Editor compmgmt.msc Computer Management secpol.msc Local Security Policy: displayswitch Connect to a Projector lusrmgr.msc Local Users and Groups control Control Panel magnify Magnifier
    [Show full text]
  • Unit OS6: Device Management
    Lab Manual - OS6 Device Management Unit OS6: Device Management 6.4. Lab Manual Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 1 Lab Manual - OS6 Device Management Copyright Notice © 2000-2005 David A. Solomon and Mark Russinovich These materials are part of the Windows Operating System Internals Curriculum Development Kit, developed by David A. Solomon and Mark E. Russinovich with Andreas Polze Microsoft has licensed these materials from David Solomon Expert Seminars, Inc. for distribution to academic organizations solely for use in academic environments (and not for commercial use) 2 2 Lab Manual - OS6 Device Management Roadmap for Section 6.4. Lab experiments investigating: Viewing Security Processes Looking at the SAM Viewing Access Tokens Looking at Security Identifiers (SIDs) Viewing a Security Descriptor structure Investigating ordering of Access Control Entries (ACEs) Investigating Privileges 3 This Lab Manual includes experiments investigating the the I/O system mechanisms and concepts implemented inside the Windows operating system. Students are expected to carry out Labs in addition to studying the learning materials in Unit OS6. A thorough understanding of the concepts presented in Unit OS6: Device Management is a prerequisite for these Labs. 3 Lab Manual - OS6 Device Management Lab: Viewing the Installed Driver List View the list of System Drivers in the Software Environment section of the Windows Information utility (Msinfo32.exe) Note: the distinction between File System Drivers and Kernel Drivers is from the Type value in the driver’s Registry key. This distinction is meaningless. 4 Lab objective: Viewing the Loaded Driver List You can see a list of registered drivers on a Windows 2000 system by going to the Drivers section of the Computer Management Microsoft Management Console (MMC) snapin or by right-clicking the My Computer icon on the desktop and selecting Manage from the context menu.
    [Show full text]
  • Windows Kernel Internals II Windows Driver Model University of Tokyo – July 2004*
    Windows Kernel Internals II Windows Driver Model University of Tokyo – July 2004* Dave Probert, Ph.D. Advanced Operating Systems Group Windows Core Operating Systems Division Microsoft Corporation © Microsoft Corporation 2004 1 Windows I/O Model Asychronous, Packet-based, Extensible Device discovery supports plug-and-play — volumes automatically detected and mounted — power management support (ACPI) Drivers attach to per device driver stacks — Drivers can filter actions of other drivers in each stack Integrated kernel support — memory Manager provides DMA support — HAL provides device access, PnP manages device resources — Cache manager provides file-level caching via MM file-mapping Multiple I/O completion mechanisms: —synchronous —update user-mode memory status —signal events —callbacks within initiating thread —reaped by threads waiting on an I/O Completion Port © Microsoft Corporation 2004 2 IO Request Packet (IRP) IO operations encapsulated in IRPs IO requests travel down a driver stack in an IRP Each driver gets an IRP stack location which contains parameters for that IO request IRP has major and minor codes to describe IO operations Major codes include create, read, write, PNP, devioctl, cleanup and close Irps are associated with the thread that made the IO request © Microsoft Corporation 2004 3 Object Relationships Driver Object Device Object Device Device Device Object Object Object Volume Device Object Driver Object File Object File Object © Microsoft Corporation 2004 4 Layering Drivers Device objects attach one on top of another
    [Show full text]
  • Windows Internals, Sixth Edition, Part 2
    spine = 1.2” Part 2 About the Authors Mark Russinovich is a Technical Fellow in ® the Windows Azure™ group at Microsoft. Windows Internals He is coauthor of Windows Sysinternals SIXTH EDITION Administrator’s Reference, co-creator of the Sysinternals tools available from Microsoft Windows ® The definitive guide—fully updated for Windows 7 TechNet, and coauthor of the Windows Internals and Windows Server 2008 R2 book series. Delve inside Windows architecture and internals—and see how core David A. Solomon is coauthor of the Windows Internals book series and has taught components work behind the scenes. Led by a team of internationally his Windows internals class to thousands of renowned internals experts, this classic guide has been fully updated Windows developers and IT professionals worldwide, SIXTH for Windows 7 and Windows Server® 2008 R2—and now presents its including Microsoft staff. He is a regular speaker 6EDITION coverage in two volumes. at Microsoft conferences, including TechNet As always, you get critical, insider perspectives on how Windows and PDC. operates. And through hands-on experiments, you’ll experience its Alex Ionescu is a chief software architect and internal behavior firsthand—knowledge you can apply to improve consultant expert in low-level system software, application design, debugging, system performance, and support. kernel development, security training, and Internals reverse engineering. He teaches Windows internals courses with David Solomon, and is ® In Part 2, you will: active in the security research community.
    [Show full text]
  • Dan's Motorcycle Windows Commands
    1 Complete List of Run Commands in Windows XP, Vista, 7, 8 & 8.1 ¶ People can get stuck if they are attacked with viruses or in any way can’t access different Applications in Windows. Sometimes it gets difficult to find the commands to start the applications directly. Knowing the Run Command for a program in different Windows versions can be very useful. if you’d like to start a program from a script file or if you only have access to a command line interface this can be helpful. For example, If you have Microsoft Word installed (Any version of Microsoft Office®) rather then searching or clicking the start icon, locating the Microsoft Office folder and then clicking the Microsoft Word. You can use the Windows Run Box instead to access the application directly. Just Click Start and Click Run or press "Window Key + R" and type "Winword" and press enter, Microsoft Word will open immediately. Here is a, hopefully, Complete list of RUN Commands in Windows XP, Vista, 7, 8 and 8.1 for your quick and easy access. Description of Applications Run Command 32-bit ODBC driver under 64-bit platform = C:\windows\sysWOW64\ odbcad32.exe 64 bit ODBC driver under 64-bit platform = C:\windows\system32\ odbcad32.exe Accessibility Controls access.cpl Accessibility Options control access.cpl Accessibility Wizard accwiz Copyright © 1999-2016 dansmc.com. All rights reserved. Adapter Troubleshooter (Vista/Win7) AdapterTroubleshooter 2 Add Features to Windows 8 Win8 windowsanytimeupgradeui Add Hardware Wizard Win8 hdwwiz Add New Hardware Wizard hdwwiz.cpl Add/Remove
    [Show full text]
  • Testing Closed-Source Binary Device Drivers with DDT
    Testing Closed-Source Binary Device Drivers with DDT Volodymyr Kuznetsov, Vitaly Chipounov, and George Candea School of Computer and Communication Sciences École Polytechnique Fédérale de Lausanne (EPFL), Switzerland Abstract non-privileged users to elevate their privileges to Local DDT is a system for testing closed-source binary de- System, leading to complete system compromise [24]. vice drivers against undesired behaviors, like race con- Our goal is to empower users to thoroughly test ditions, memory errors, resource leaks, etc. One can drivers before installing and loading them. We wish that metaphorically think of it as a pesticide against device the Windows pop-up requesting confirmation to install driver bugs. DDT combines virtualization with a spe- an uncertified driver also offered a “Test Now” button. cialized form of symbolic execution to thoroughly ex- By clicking that button, the user would launch a thor- ercise tested drivers; a set of modular dynamic check- ough test of the driver’s binary; this could run locally or ers identify bug conditions and produce detailed, exe- be automatically shipped to a trusted Internet service to cutable traces for every path that leads to a failure. These perform the testing on behalf of the user. Such function- traces can be used to easily reproduce and understand ality would benefit not only end users, but also the IT the bugs, thus both proving their existence and helping staff charged with managing corporate networks, desk- debug them. We applied DDT to several closed-source tops, and servers using proprietary device drivers. Microsoft-certified Windows device drivers and discov- Our work applies to all drivers, including those for ered 14 serious new bugs.
    [Show full text]
  • Windriver™ USB User's Manual
    WinDriver™ USB User's Manual Version 11.2.0 Jungo Ltd. WinDriver™ USB User's Manual: Version 11.2.0 Copyright © Jungo Ltd. 2005–2013 All Rights Reserved. Information in this document is subject to change without notice. The software described in this document is furnished under a license agreement. The software may be used, copied or distributed only in accordance with that agreement. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means, electronically or mechanically, including photocopying and recording for any purpose without the written permission of Jungo Ltd. Brand and product names mentioned in this document are trademarks of their respective owners and are used here only for identification purposes. © Jungo Ltd. 2005–2013 ii Table of Contents 1. WinDriver Overview .................................................................................................................. 1 1.1. Introduction to WinDriver .............................................................................................. 1 1.2. Background ..................................................................................................................... 2 1.2.1. The Challenge ...................................................................................................... 2 1.2.2. The WinDriver Solution ...................................................................................... 2 1.3. Conclusion ......................................................................................................................
    [Show full text]
  • Developing Drivers with Visual Studio 2012
    Developing Drivers with Visual Studio 2012 Advanced Developers Conference (adcpp.de) Bad Aibling, Germany May, 2013 Developed and Presented by : CodeMachine www.codemachine.com Introduction . T.Roy . Masters Degree in Computer Engineering . 20 years experience in system software development . Author, instructor, consultant & founder of CodeMachine . CodeMachine . Consulting and Training Company . codemachine.com, twitter.com/codemachineinc, facebook.com/codemachineinc . Custom software development and debugging services . WDM, KMDF, Networking, Storage, File System & Security . Onsite and online training courses . Windows Internals for Application Developers . Windows Application Debugging & Memory Dump Analysis . Windows Internals for Driver Developers . Windows Driver Debugging & Memory Dump Analysis Copyrighted Material © 2000-2013 CodeMachine Inc. All Rights Reserved. 2 Agenda Code Build Analyze Sign Provision Network and Select Samples F/W Settings Configuration PreFast Test Sign Templates Debugger Select SDV Production Connection Platform Existing Sign DVL Sources Target Project Build Configuration Settings Deploy Debug Verify Test Update Choose Select Target Select Driver Select Enable Qualifier Tests KDFiles Install Driver Method Attach & Verifier Test Choose Break into Parameters Target Additional Target KMDF Files Verifier Copyrighted Material © 2000-2013 CodeMachine Inc. All Rights Reserved. 3 Demo Setup . Host System Windows 8 Enterprise X64 . Visual Studio Professional 2012 (11.0.60315.01) . With Visual Studio 2012 Update 2 . .NET Framework 4.5.50709 . Windows Driver Kit 8.0 (6.2.9200.16384) . Debugging Tools for Windows (6.2.9200.16384) . Part of Windows Driver Kit . Virtualization Software is Virtual Box 4.2.0.r80737 . Target System VM is Windows 8 Basic X86 Copyrighted Material © 2000-2013 CodeMachine Inc. All Rights Reserved. 4 VS 2012 Features .
    [Show full text]
  • Attacking the Windows Kernel
    Attacking the Windows Kernel Jonathan Lindsay ([email protected]) An NGSSoftware Insight Security Research (NISR) Publication ©2007 Next Generation Security Software Ltd http://www.ngssoftware.com Abstract Most modern processors provide a supervisor mode that is intended to run privileged operating system services that provide resource management transparently or otherwise to non-privileged code. Although a lot of research has been conducted into exploiting bugs in user mode code for privilege escalation within the operating system defined boundaries as well as what can be done if one has arbitrary supervisor access (typically related to modern root kit work), not a great deal of research has been done on the interface between supervisor and non-supervisor, and potential routes from one to the other. The biggest problem arises when trying to protect the kernel from itself - for example, under the IA32 architecture implementation of Windows, the distinction between user mode and kernel mode from the user mode perspective is easily enforced through hardware based protection. However, as the kernel is running as supervisor, how does the kernel make distinctions between what it should be accessing? This would be irrelevant if the supervisor was not exposed to interaction with supervisee; but that would defeat the purpose of having a kernel. This paper is focused on Windows and the Intel Architecture, and will briefly outline the current supervisor boundaries provided. Different attack vectors, along with relevant examples, will be provided to demonstrate how to attack the supervisor from the perspective of the supervised, as well as an outline of what possible architectures could be used to mitigate such attacks, such as the research operating system Singularity.
    [Show full text]
  • Quickly Resolve Driver Problems Using the Built-In Verifier.Exe Tool
    D826.qxp_May 2018 29/03/2018 14:53 Page 15 Driver Errors, Quick Solutions D 826/1 Quickly Resolve Driver Problems Using the Built-in Verifier.exe Tool Using the information given in this article you will be able to: Pinpoint the faulty device drivers on your system, Solve driver errors to prevent Blue Screen STOP crashes, Fix problems with Verifier.exe in Safe Mode. Driver errors are the bane of many Windows users, and if you haven't come up against one yet you should count yourself lucky. Not only do faulty drivers lead to crashes, out-of-date drivers can drag down your performance. But it is not easy to identify the driver that is the cause of an error message or system crash. In this article, I’ll show you how to use the Driver Verifier Manager (Verifier.exe) to check all the installed drivers on your system in order to boost stability and Windows reliability and correct errors when you encounter driver problems. • Fix Half of All Hardware Errors Caused by Driver Problems ........................................................... D 826/2 • Run the Driver Verifier Manager on Your PC ........... .... D 826/3 • Analyse the Results of Your First Driver Test ... ............. D 826/6 • Solve Driver Problems Using the Driver Verifier Manager .............................................................. D 826/9 • The Different Driver Checks Explained in Detail ........... D 826/10 • Solve Driver Errors that Make Windows Constantly Re-boot .......................................................... D 826/12 The Windows Advisor May 2018 15 D826.qxp_May 2018 29/03/2018 14:53 Page 16 D 826/2 Driver Errors, Quick Solutions Fix Half of All Hardware Errors Caused by Driver Problems How Windows Drivers provide an essential interface between your uses drivers operating system and your PC’s hardware devices.
    [Show full text]