Thanks for the answer nass. Yes, I did have the ifsmount driver on my
Win XP system and as I previously posted verifier pointed out an error
it was tossing which I looked up at the link you provided. Here is the
info I found there -
0x20C Fatal error The caller of IoFreeIrp is freeing an IRP that is
still queued against a thread. (IRP specified.)
This is the supposed error ifsmount.sys was causing [even 'though it has
been working fine for weeks with no problems before]
Anyway, I un-installed ifsmount and now Windows is working again. ???
What the heck happened to cause this wonderful driver to stop working?
My theory is an update from Mickeysoft broke it some how, but upon
looking in Add/Remove in Control Panel with "Show Updates" checkmarked
the newest update I could find was last month. It's been working fine in
the interim.
I lament that I can no longer access my Ubuntu partition from within
windows, but oh well, I hardly use Windows anymore, and can access all
of the Windows partitions just fine from Ubuntu.
Later, Ray Parrish
nass wrote:
> Hi Ray,
> Do you have IFS Mount Manager driver.
> It is a Kernal Mode app that create and delete Dives letter for any volume
> like in Linux Ext2..etc
> It ids located here:
> C:\Windows\LASTGOOD.TMP\System32\Drivers\IFSMOUNT.SYS
> C:\Windows\System32\Drivers\IFSMOUNT.SYS
>
> IO SYSTEM VERIFICATION ERROR
> http://www.osronline.com/DDKx/ddtools/dv_962b.htm
>
> HTH,
> nass
> ---
> http://www.nasstec.co.uk
>
> "Ray Parrish" wrote:
>
>> Hello again,
>>
>> This is an update with what I've tried so far. I booted to Safe Mode and
>> ran verifier. My computer then rebooted and I attempted to start in
>> normal mode to run the verification, and almost immediately the computer
>> stopped on a blue screen with the following error -
>>
>> IOSystem verification error in ifsmount.sys (WDM driver error 20e)
>> ifsmount.sys+9123 at F7630123
>>
>> I'm off to google this, in the meantime any tips or tricks from the
>> group would be most appreciated.
>>
>> Later, Ray Parrish
>>
>> Ray Parrish wrote:
>>> Hello,
>>>
>>> I booted into Windows XP, SP3 on my EMachine T3410 this morning for the
>>> first time in about a week and a half [I dual boot Ubuntu and have been
>>> using that for the most part] and got the error in the subject line
>>> before everything had completely loaded in Windows.
>>>
>>> I rebooted to see if the error persisted and noted that on the second
>>> boot that almost everything had loaded, but the chat program [Windows
>>> Live Messenger] was still trying to sign in when the BSOD happened again.
>>>
>>> The last time I was in Windows successfully I only used my checking
>>> account program, then shut down, When shutting down I noted that Windows
>>> had downloaded updates as it warned me it was going to install them upon
>>> shutdown.
>>>
>>> I've researched it briefly using google, and it seems to be a widespread
>>> occurrence with varying causes. It was recommended that one run
>>> Microsoft's verifier [driver verifier] and also to run a memory test.
>>>
>>> I'm pretty sure it's not the memory as I'm running just fine in Ubuntu,
>>> so it must be the update that was just installed.
>>>
>>> Does anyone have any other tips on what I might try to do to solve the
>>> problem?
>>>
>>> Later, Ray Parrish
--
http://www.rayslinks.com/ Web index of human reviewed links.
<http://www.rayslinks.com/Troubleshooting%20and%20fixing%20Windows.html>
Trouble shooting and Fixing Windows
http://www.writingsoftheschizophrenic.com My poetry in web pages
Similar Threads
