Hi,
FYI:Probelem is in 2003 and 2008 R2 Server, it works on 2008 Server.
Problem Description:
My driver has a Bus Driver (FDO) and Storage Stack (Storport) loaded on the PDO created under via Bus Driver. I’m using the WDF call (WdfDeviceSetSpecialFileSupport(hDevice, WdfSpecialFilePaging, TRUE) in the Bus Driver’s as well as for PDO created for storage stack. When I select the paging file on this driver which is a non boot driver, I do see system calling the usage notification in my Bus Driver and PDO, and I could see the page file created.
But on reboot I see the following page file error “Windows created a temporary paging file on your computer because of a problem that occured with you paging file configuration when you started your computer” and system starts using the default temporary pagefile. System/KMDF does not call the usagenotification on reboot under 2008 R2 Server. I don’t understand what I am doing wrong or I need to do to make it work. I need help here.
Tarun Singh
You could try putting a breakpoint on NtCreatePagingFile during boot and see
if a) it gets called and b) what the return code is (it returns an NTSTATUS
value).
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
wrote in message news:xxxxx@ntfsd…
> Hi,
>
> FYI:Probelem is in 2003 and 2008 R2 Server, it works on 2008 Server.
>
> Problem Description:
> My driver has a Bus Driver (FDO) and Storage Stack (Storport) loaded on
> the PDO created under via Bus Driver. I’m using the WDF call
> (WdfDeviceSetSpecialFileSupport(hDevice, WdfSpecialFilePaging, TRUE) in
> the Bus Driver’s as well as for PDO created for storage stack. When I
> select the paging file on this driver which is a non boot driver, I do see
> system calling the usage notification in my Bus Driver and PDO, and I
> could see the page file created.
>
> But on reboot I see the following page file error “Windows created a
> temporary paging file on your computer because of a problem that occured
> with you paging file configuration when you started your computer” and
> system starts using the default temporary pagefile. System/KMDF does not
> call the usagenotification on reboot under 2008 R2 Server. I don’t
> understand what I am doing wrong or I need to do to make it work. I need
> help here.
>
> Tarun Singh
>
Hi Scott,
The NtCreatePagingFile was called from “nt!KiSystemServiceCopyEnd+0x13”, so I put a breakpoint at “nt!KiSystemServiceCopyEnd+0x13” and checked the eax register for a return value, which was 0;
Stack was:
nt!NtCreatePagingFile
nt!KiSystemServiceCopyEnd+0x13
Please let me know how I can debug it further.
-Tarun
Bummer, I was hoping it would be that easy.
If you can figure out which component pops that dialog that would be a
start. Also, I think that Process Monitor supports boot logging so that
might be something worth trying.
It’s so much easier when the system just crashes or hangs. These, “it
doesn’t work” can be a real pain.
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
wrote in message news:xxxxx@ntfsd…
> Hi Scott,
>
> The NtCreatePagingFile was called from “nt!KiSystemServiceCopyEnd+0x13”,
> so I put a breakpoint at “nt!KiSystemServiceCopyEnd+0x13” and checked the
> eax register for a return value, which was 0;
>
> Stack was:
> nt!NtCreatePagingFile
> nt!KiSystemServiceCopyEnd+0x13
>
> Please let me know how I can debug it further.
>
> -Tarun
>
Have you tried making this a boot start driver? Every time I’ve dealt
with paging file issues in the end having everything boot start made it
easier.
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
-----Original Message-----
From: Scott Noone [mailto:xxxxx@osr.com]
Posted At: Tuesday, April 13, 2010 10:09 AM
Posted To: ntfsd
Conversation: UsageNotification not called on system reboot on a non
boot
storage driver
Subject: Re: UsageNotification not called on system reboot on a non
boot
storage driver
Bummer, I was hoping it would be that easy.
If you can figure out which component pops that dialog that would be a
start.
Also, I think that Process Monitor supports boot logging so that might
be
something worth trying.
It’s so much easier when the system just crashes or hangs. These, “it
doesn’t
work” can be a real pain.
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
wrote in message news:xxxxx@ntfsd…
> > Hi Scott,
> >
> > The NtCreatePagingFile was called from
“nt!KiSystemServiceCopyEnd+0x13”,
> > so I put a breakpoint at “nt!KiSystemServiceCopyEnd+0x13” and
checked the
> > eax register for a return value, which was 0;
> >
> > Stack was:
> > nt!NtCreatePagingFile
> > nt!KiSystemServiceCopyEnd+0x13
> >
> > Please let me know how I can debug it further.
> >
> > -Tarun
> >
>
>
> Information from ESET Smart Security, version of virus
signature
> database 5025 (20100413)
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
Making it boot Start, paging file operation worked. I could now see the usagenotification coming on the reboots and page file being created.
Thanks lot to all, and Don Burn.
Tarun Singh