Windows error 0x00000076, 118

Detailed Error Information


MessageThe verify-on-write switch parameter value is not correct.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070076.


This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x76: PROCESS_HAS_LOCKED_PAGES.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
Reserved (X)false
FacilityCode0 (0x000)
DescriptionThe default facility code.[3][1]
Error Code118 (0x0076)

Possible solutions


C# program causes bluescreen?


I discovered this issue a few weeks back. It only happens when using .NET 4.

Reported at MS Connect.


(Will*) Add this link to MS Connect bug report.

* is going into an infinite loop again...

answered on Stack Overflow Nov 2, 2011 by leppie • edited Nov 2, 2011 by leppie

C# program causes bluescreen?


Just to be clear, there is no way for "user" mode code to forcibly create a blue screen in windows, unless it uses undocumented APIs and or forces bad data into a driver. Your C# code is likely not be at fault here, as if you use the user mode classes (Socket) then the socket is responsible for not crashing your computer.

As @Joe has commented Microsoft Support KB Article 256010 clearly describes this stop message, but better yet has clear instructions on capturing the driver name responsible for this error.

Note that any software firewall that you have installed also is involved at kernel mode level so could also be responsible for this error. I recommend you follow the KB articles advice and try to find out what is at fault. But you could also ensure that you have updated your network drivers and firewall/VPN software to the latest stable versions.

answered on Stack Overflow Nov 2, 2011 by Spence

Customizing Fantacy Remote .INI file


In my opinion you should change this:

On server side, set iAcceptInput in [SERVER] section to 0. This might disable mouse and keyboard input.

On client side, in section [MENU] you have to try different values for the key iWindowMode. Try 1, 2 or 3.

answered on Super User May 27, 2010 by user4085

Calling to a pointer from a c++ thread


0x00000076 is an invalid memory address. All addresses under 0x0000ffff are invalid. This catches a whole class of errors (failed memory allocations or object creation) along the lines of 0x0 and 0x0 + 2 (or 0x0 + 0x76) etc. The errors are errors that programmers are supposed to check for but often don't.

My guess is you are accessing the 0x76th byte of a structure that wasn't initialised.

VB6 is designed to be a COM server not a dynamic load dll.

AddressOf has rules because you are actually calling VB6 runtime not your program.

You can also start in a debugger.

windbg or ntsd (ntsd is a console program and maybe installed). Both are also from Debugging Tools For Windows.

Download and install Debugging Tools for Windows

Install the Windows SDK but just choose the debugging tools.

Create a folder called Symbols in C:\

Start Windbg. File menu - Symbol File Path and enter



windbg -o -g -G c:\windows\system32\cmd.exe /k batfile.bat

You can press F12 to stop it and kb will show the call stack (g continues the program). If there's errors it will also stop and show them.

Type lm to list loaded modules, x *!* to list the symbols and bp symbolname to set a breakpoint

If programming in VB6 then this environmental variable link=/pdb:none stores the symbols in the dll rather than seperate files. Make sure you compile the program with No Optimisations and tick the box for Create Symbolic Debug Info. Both on the Compile tab in the Project's Properties.

Also CoClassSyms ( can make symbols from type libraries.

answered on Stack Overflow Sep 20, 2014 by Noodles


Leave a comment

(plain text only)


  1. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0