Environment:
1. The process is called PCI devices interrupt program, run in kernel mode, about 2 ms scheduling time,
2. In the process created two Shared memory (SEC_NOCACHE | SEC_COMMIT | PAGE_READWRITE), and already VirtualLock,
3. The process and some run in user mode are in the process of reading and writing the two Shared memory,
4. The operating system, Windows XP Professional SP3, four dual-core CPU thread


Normal operation of a few hours later, would be the kernel configuration process as the Page Fault collapse, crash when the CPU register information is as follows:

The EIP: 00000000 (fixed)
EAX: F766DF67 (fixed)
EBX: 00000008 (fixed)
ECX: 00000014 (fixed)
EDX: 00000014 (fixed)

EBP: 89 a0de74 (A0D the three digital sometimes change, other fixed)
ESP: 89 a0de6c (A0D the three digital sometimes change, other fixed)

EDI: 00000000
ESI: 00000024

The problem for a long time, do you have any ideas?

CodePudding user response:

Windows driver development http://www.osronline.com/

CodePudding user response:

Use of driver genius software upgrades can drive?

CodePudding user response:

refer to the second floor zhao4zhong1 response:

use driver genius software upgrades can drive?

Thank you, the driver is developed, test is no problem, have determined the kernel processes its own problems,

CodePudding user response:

1. Send up and DUMP file
2. You can try Windows 2003 environment using the WRK source compile a then loaded with debug observation error location,

CodePudding user response:

Possible, debug the driver in the virtual machine, use windbg has connection debugging, see what's the problem