Freezing on Windows Server 2003 when Verifier is enabled

NTDEV
1

Hi,

I am checking a DiskDrive upper disk filter driver using Windows Verifier, and am experiencing a freeze when I enable Verifier on Windows Server 2003x64 platform, and only on release version of the driver. The debug version is fine, and the driver passes standard Verifier checks on other platforms including Windows Server 2003x32 and Windows Server 2008R2x64.

I was wondering what would be a possible explanation for a freeze in this specific configuration: Win Server 2003x64 + Verifier Enabled + Release version of the driver, while the same code compiled for other platforms works fine?

Thank You,
Hossein

2

Connect it to a debugger. Post the stacks.

3

I have difficulties breaking into this kernel as well. Windbg (as well as debuggee) becomes frozen at the following step, even without having the driver installed (debuggee cpu 100%):

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \.\com1
Waiting to reconnect…
Connected to Windows Server 2003 3790 x64 target at (Wed Jul 30 16:42:30.789 2014 (UTC - 6:00)), ptr64 TRUE
Kernel Debugger connection established.
Symbol search path is: srv*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) UP Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.130306-1435
Machine Name:
Kernel base = 0xfffff80001000000 PsLoadedModuleList = 0xfffff80001198b00

4

Finally I managed to break in and this is the call stack. Any idea of what is happening?

nt!DbgBreakPointWithStatus
nt!KeCapturePersistentThreadState+0x609
nt!IoGetRelatedDeviceObject+0x698c
nt!KeUpdateSystemTime+0xef
hal!HalSetTimeIncrement+0x211
nt!KeSynchronizeExecution+0xa49
nt!DbgPrint+0x4c6
nt!RtlLookupFunctionEntry+0x1cc
nt!RtlGetCallersAddress+0x3fd
nt!RtlCaptureStackBackTrace+0x72
nt!RtlCompressBuffer+0x591c
******!**********Queue_PopOut+0x33
******!******Thread****QueueCleanup+0x149
nt!ObCreateObject+0x47e
nt!memset+0x226

5

You need to load correct symbols into the debugger. Then post the stack trace.