This paper aims to educate the reader on the espousal of code
coverage analysis and fuzzing philosophy presented by researchers as
a means to lighten the burden of bug detection. A kernel mode device
driver will be fuzzed for bugs using a standard fuzzing method.
Results from the initial fuzzing test will be examined to determine
coverage. The fuzz testing method will be revised to accommodate
coverage concerns and an execution graph is generated to view the
results of the previous testing. A comparison is then made between
the two prior testing methods, proving how effective code coverage
analysis through kernel mode Stalking can improve fuzzing endeavors.