Iirc, DeviceInit is stack based on the call to AddDevice so I am not sure how !pte handles stack addresses. As for the break, this has nothing to do with kmdf, rather the debugger interacting with the os.
d
Bent from my phone
From: xxxxx@gmail.commailto:xxxxx
Sent: ?1/?14/?2014 5:44 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] KiPageFault into BSOD when stepping over
Krzysztof, I was digging this right before you wrote
Before unsuccessful call to WdfFdoInitQueryProperty (bp before call is made)
1: kd> !pte poi(DeviceInit)
VA ffffe00020464c10
PXE at FFFFF6FB7DBEDE00 PPE at FFFFF6FB7DBC0000 PDE at FFFFF6FB78000810 PTE at FFFFF6F000102320
contains 0000000000381863 contains 0000000000382863 contains 0000000000000000
pfn 381 —DA–KWEV pfn 382 —DA–KWEV not valid
After successful call to WdfFdoInitQueryProperty (bp after the call is made):
1: kd> !pte poi(DeviceInit)
VA ffffd00020464c10
PXE at FFFFF6FB7DBEDD00 PPE at FFFFF6FB7DBA0000 PDE at FFFFF6FB74000810 PTE at FFFFF6E800102320
contains 00000000002A4863 contains 00000000002A3863 contains 0000000000541863 contains 8000000002820963
pfn 2a4 —DA–KWEV pfn 2a3 —DA–KWEV pfn 541 —DA–KWEV pfn 2820 -G-DA–KW-V
Does this mean Windows fixes kernel PTEs on the fly? OK, but why does it bugcheck at that point?
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>