I did a System Restore to the last driver I installed to try and correct
this error:

0x000000D1 (0x81E1383F, 0x000000FF, 0x00000000, 0xC8FE29BF)

DRIVER_IRQL_NOT_EQUAL_OR_LESS

When the computer restarted, it went into yet another BSOD:

srv.sys

The driver is attempting to access memory after it has been freed.

0x000000D5 (0xA6DE4E01, 0x00000000, 0xA853FF22, 0x00000000)

srv.sys - Address A853FF22 base at A851A000, DateStamp 4549acfb

It seems the srv.sys is the problem here? Do I have to replace the file?

Tony--

Exhaust the directions I gave you the first time (which you have not done):

Why haven't you

1) Consulted a games forum and see if there are special issues?
2) Tried a startup repair if you have the DVD?
3) Tried a repair install if you have the DVD?
4) Tried system restore from another location--there are 5 and 6 if you have
the DVD?
5) Have you added any recent drivers and if so have you tried to

a) reinstall it
b) try another driver if there's an option
c) rolled back the driver

CH


"Tony" <Tony@discussions.microsoft.com> wrote in message
news:BADBF769-FF2D-4CC4-AC83-54A4AD51C07F@microsoft.com...[color=blue]
>I did a System Restore to the last driver I installed to try and correct
> this error:
>
> 0x000000D1 (0x81E1383F, 0x000000FF, 0x00000000, 0xC8FE29BF)
>
> DRIVER_IRQL_NOT_EQUAL_OR_LESS
>
> When the computer restarted, it went into yet another BSOD:
>
> srv.sys
>
> The driver is attempting to access memory after it has been freed.
>
> 0x000000D5 (0xA6DE4E01, 0x00000000, 0xA853FF22, 0x00000000)
>
> srv.sys - Address A853FF22 base at A851A000, DateStamp 4549acfb
>
> It seems the srv.sys is the problem here? Do I have to replace the file?
>
>
>[/color]

Sorry I didn't read as carefull as I should Tony. I see you system
restored.

If you have the DVD try Startup Repair or a repair install. The driver you
restored back to may not have been the problem. Usually with this error you
get mention of a driver that's the problem if a driver is a problem.

I don't think replacing that file is the solution. If so you can do it
running SFC--System File checker.

***SFC as a Remedy***:

SFC or System File Checker is a bit like the spare tire in your car or a
backup battery I suppose. In Vista of course, they have changed it somewhat
and come up with a new name--Redmond stands for name it something different
twice a year and now it's part of WRP or Windows Resource Protection. It
scans protected resources including thousands of files, libraries, critical
folders, and essential registry keys, and it replaces those that are
corrupted with intact ones. It fixes a lot of problems in Windows XP, OE,
Windows Vista, Win Mail, IE6, and on Vista or if it is installed on XP, IE7.
It protects these things from changes by any source including
administrators, by keeping a spare of most of them.


How to Run SFC:

Type "cmd" into the Search box above the Start Button>and when cmd comes up
at the top of the Start menu>right click cmd and click "run as Admin" and
when the cmd prompt comes up at the cmd prompt type "sfc /scannow" no quotes
and let it run. This may fix things quite a bit. It replaces corrupt files
with intact ones, if you're not familiar with it.

CH

"Tony" <Tony@discussions.microsoft.com> wrote in message
news:BADBF769-FF2D-4CC4-AC83-54A4AD51C07F@microsoft.com...[color=blue]
>I did a System Restore to the last driver I installed to try and correct
> this error:
>
> 0x000000D1 (0x81E1383F, 0x000000FF, 0x00000000, 0xC8FE29BF)
>
> DRIVER_IRQL_NOT_EQUAL_OR_LESS
>
> When the computer restarted, it went into yet another BSOD:
>
> srv.sys
>
> The driver is attempting to access memory after it has been freed.
>
> 0x000000D5 (0xA6DE4E01, 0x00000000, 0xA853FF22, 0x00000000)
>
> srv.sys - Address A853FF22 base at A851A000, DateStamp 4549acfb
>
> It seems the srv.sys is the problem here? Do I have to replace the file?
>
>
>[/color]