Where does Driver Verifier Store the Results of its Tests?
-
I am trying to troubleshoot a blue screen problem in Windows 10. I enabled Driver Verifier, and it immediately raised the bug check DRIVER_VERIFIER_DETECTED_VIOLATION. Where do I go on the system to find out what the error is?
The difficult we do right away... ...the impossible takes slightly longer.
-
I am trying to troubleshoot a blue screen problem in Windows 10. I enabled Driver Verifier, and it immediately raised the bug check DRIVER_VERIFIER_DETECTED_VIOLATION. Where do I go on the system to find out what the error is?
The difficult we do right away... ...the impossible takes slightly longer.
Windows 10 is still the same Windows Runtime based operating system, most of the things come from Win32 and a few cover ups to provide a Metro look and feel. :-) May the following threads help you: https://msdn.microsoft.com/en-us/library/windows/hardware/dn457995%28v=vs.85%29.aspx[^] http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/windows-8-driververifierdetectedviolation-caused/09c53a43-4feb-4d48-aa5d-5c625d23bd32?auth=1[^] From the MSDN documentation, the error message is due to a memory-leak (did you write that driver?)
Quote:
Driver Verifier generates Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION with a parameter 1 value of 0x62 when a driver unloads without first freeing all of its pool allocations. Unfreed memory allocations (also called memory leaks) are a common cause of lowered operating system performance. These can fragment the system pools and eventually cause system crashes. When you have a kernel debugger connected to a test computer running Driver Verifier, if Driver Verifier detects a violation, Windows breaks into the debugger and displays a brief description of the error.
So, the solution (in my opinion) can be to fix the memory-leaks in those drivers. List of the bugs can be found here: https://msdn.microsoft.com/en-us/library/windows/hardware/ff560187(v=vs.85).aspx[^], it may help you checking which bug it was (since you haven't shared the bug code). Note: The table provided there (in MSDN document provided above) has 5 rows, make sure you can view all 5 to determine th
-
Windows 10 is still the same Windows Runtime based operating system, most of the things come from Win32 and a few cover ups to provide a Metro look and feel. :-) May the following threads help you: https://msdn.microsoft.com/en-us/library/windows/hardware/dn457995%28v=vs.85%29.aspx[^] http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/windows-8-driververifierdetectedviolation-caused/09c53a43-4feb-4d48-aa5d-5c625d23bd32?auth=1[^] From the MSDN documentation, the error message is due to a memory-leak (did you write that driver?)
Quote:
Driver Verifier generates Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION with a parameter 1 value of 0x62 when a driver unloads without first freeing all of its pool allocations. Unfreed memory allocations (also called memory leaks) are a common cause of lowered operating system performance. These can fragment the system pools and eventually cause system crashes. When you have a kernel debugger connected to a test computer running Driver Verifier, if Driver Verifier detects a violation, Windows breaks into the debugger and displays a brief description of the error.
So, the solution (in my opinion) can be to fix the memory-leaks in those drivers. List of the bugs can be found here: https://msdn.microsoft.com/en-us/library/windows/hardware/ff560187(v=vs.85).aspx[^], it may help you checking which bug it was (since you haven't shared the bug code). Note: The table provided there (in MSDN document provided above) has 5 rows, make sure you can view all 5 to determine th
First, thank you very much for your reply. Windows 10 blue screens do not list any bug check code information like all prior Windows did. Therefore, I do not know the bug code. And that's what I'm asking: Where to go on the system to find the code?
The difficult we do right away... ...the impossible takes slightly longer.
-
First, thank you very much for your reply. Windows 10 blue screens do not list any bug check code information like all prior Windows did. Therefore, I do not know the bug code. And that's what I'm asking: Where to go on the system to find the code?
The difficult we do right away... ...the impossible takes slightly longer.
Right, sorry for missing that important and valid point there. Actually, everything in the operating system is logged, somewhere. So, if Windows itself doesn't show anything (it is mainly because, most users aren't concerned with resolving those problems, like you are concerned, they just take it to a hardware repair center). Same in these cases, the logs are shown in the DMP files (I would say, that the Dump file, where Windows dumps everything that it has about that crash report). Although they are not used, or viewed by the consumers, they are meant to be uploaded and shared with Microsoft developers directly, you won't be able to get anything useful, but if you want. You can get the files right in C:\Windows\Minidump or inside the C:\Windows, there will be a file MEMORY.DMP. Use it, to see if you can get to to any use of yours in debugging the error. :-) For more on that topic, BSOD, read this Microsoft answers thread: http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d[^] Maybe helpful: http://superuser.com/questions/148114/where-are-blue-screen-of-death-events-logged-on-windows-xp-and-how-can-i-view-th[^]
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
-
Right, sorry for missing that important and valid point there. Actually, everything in the operating system is logged, somewhere. So, if Windows itself doesn't show anything (it is mainly because, most users aren't concerned with resolving those problems, like you are concerned, they just take it to a hardware repair center). Same in these cases, the logs are shown in the DMP files (I would say, that the Dump file, where Windows dumps everything that it has about that crash report). Although they are not used, or viewed by the consumers, they are meant to be uploaded and shared with Microsoft developers directly, you won't be able to get anything useful, but if you want. You can get the files right in C:\Windows\Minidump or inside the C:\Windows, there will be a file MEMORY.DMP. Use it, to see if you can get to to any use of yours in debugging the error. :-) For more on that topic, BSOD, read this Microsoft answers thread: http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d[^] Maybe helpful: http://superuser.com/questions/148114/where-are-blue-screen-of-death-events-logged-on-windows-xp-and-how-can-i-view-th[^]
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
Thanks for following up. I think you have solved my problem. The reason I wasn't able to find the MEMORY.DMP file is that it did not create one. And the reason it didn't create one is given in the first link you provided. Namely, the page file must be located on the boot drive for the memory dump to work, and I currently have my page file on another drive. So I'll move the page file and wait for the BSOD to happen again. Thanks again!
The difficult we do right away... ...the impossible takes slightly longer.
-
Thanks for following up. I think you have solved my problem. The reason I wasn't able to find the MEMORY.DMP file is that it did not create one. And the reason it didn't create one is given in the first link you provided. Namely, the page file must be located on the boot drive for the memory dump to work, and I currently have my page file on another drive. So I'll move the page file and wait for the BSOD to happen again. Thanks again!
The difficult we do right away... ...the impossible takes slightly longer.
Great that your problem got (almost) solved, Richard! :-)
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
-
I am trying to troubleshoot a blue screen problem in Windows 10. I enabled Driver Verifier, and it immediately raised the bug check DRIVER_VERIFIER_DETECTED_VIOLATION. Where do I go on the system to find out what the error is?
The difficult we do right away... ...the impossible takes slightly longer.
Go to the system advanced and in start up and recovery set the machine to produce a memory dump, you can chose full or mini. Mini is OK ish, in which case its written to system\minidumps as a dmp file with the date/time in the name. If you chose full dump its written to \system\memory.dmp and overwrites any existing one. To look at the contents use windbg, and open the file. Then run !analyze -v from the command line (bottom of windbg window) and it will do an autoanalyse. Be careful, these aren't always accurate and often blame the wrong component. Now you need to debug the issue. Commands like !poolused can hep you find drivers that are using excessive memory, !thread and .thread are very useful to switch to any thread in the system so you can look at each threads stack and wait times. In fact what you can do with windbg is immense, its got a massive and powerful command set. There is a doc that comes with windbg on basic debugging practices, it is very worth reading.
