[Aubergine30]

Hello I have been having problems starting computers. I've gotten messages like this:

Invalid Kernel Handle STOP 93

ANOTHER ERROR MESSAGE
afd.sys An attempt was made to write to read only memory
STOP:0X000000BE (0XAA4A7BFB

DISABLE BIOS MEMORY OPTIONS SUCH AS CACHING OR SHADOWING

ANOTHER MESSAGE

STOP 24
ntfs.sys address F8345268


I wish they would make me plain for ordinary users. I dont know what this means. Any help would be appreciated.

[Advertisements]

0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware. If a driver file is named in the error message, try to correct the problem by disabling, removing, or rolling back the driver.

You could use microsoft's driver verifier to see what driver is causing your problem. There is a steep learning curve on how to use it so you may not want to try.

http://support.micro...=244617&sd=RMVP

a AFD sys error is "Ancillary Function Driver" for WinSock

It's a system kernel driver, aka "AFD Networking Support Environment" and is part of the Windows TCP/IP stack, supporting socket operations. Some versions of Windows apparently exhibit a memory leak with this driver (link: http://dn.codegear.com/article/30362) and, while Windows diagnostics reports that it does accept the "stop" command...it's probably best to understand its role first. See "link for more info's", i.e., "How To: Harden the TCP/IP Stack." My advice? Don't mess with it, unless you know *exactly* what you're doing.

http://msdn.microsof...x#hthardtcp_005

You might want to read this similar thread.

http://www.techspot....opic129752.html

i hope this helps.

SRX660

[SRX660]

0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware. If a driver file is named in the error message, try to correct the problem by disabling, removing, or rolling back the driver.

You could use microsoft's driver verifier to see what driver is causing your problem. There is a steep learning curve on how to use it so you may not want to try.

http://support.micro...=244617&sd=RMVP

a AFD sys error is "Ancillary Function Driver" for WinSock

It's a system kernel driver, aka "AFD Networking Support Environment" and is part of the Windows TCP/IP stack, supporting socket operations. Some versions of Windows apparently exhibit a memory leak with this driver (link: http://dn.codegear.com/article/30362) and, while Windows diagnostics reports that it does accept the "stop" command...it's probably best to understand its role first. See "link for more info's", i.e., "How To: Harden the TCP/IP Stack." My advice? Don't mess with it, unless you know *exactly* what you're doing.

http://msdn.microsof...x#hthardtcp_005

You might want to read this similar thread.

http://www.techspot....opic129752.html

i hope this helps.

SRX660