3538:Crashes system and that message on blue screen:kx.sys The driver mistakenly mar

mrvomit · Feb 10, 2006, 01:13 PM

i got a crash and that was the error.

"kx.sys
The driver mistakenly marked a part of it's image pagable instead of nonpagable"

It happened to a russian guy also here in the forum ,but since is in the rusisian
forum i can'tunderstand..
what happened?

ONjA · Feb 11, 2006, 11:40 AM

Pageable section or allocated block of memory can be swapped out of physical memory to a page file. But when it needed again, it can be accessed only at certain priority level (not above the priority of system service, which brings back that block of memory). This requires more attention on priority lowering/rising.

Nonpageable can be accessed at any time, but always consumes physical memory.

Feb 10, 2006, 01:13 PM	#1
mrvomit HardwareHeaven Addict Join Date: Oct 2003 Posts: 261 Rep Power: 0	3538:Crashes system and that message on blue screen:kx.sys The driver mistakenly mar i got a crash and that was the error. "kx.sys The driver mistakenly marked a part of it's image pagable instead of nonpagable" It happened to a russian guy also here in the forum ,but since is in the rusisian forum i can'tunderstand.. what happened? __________________ audio: Audigy 2 platinum SB0240 - amd 939 175 opty- Backup: Sblive 5.1 platinum (w.live drive) Sb060 DVDwriter : pioneer 107, nec 3540A windows XP

Feb 11, 2006, 11:40 AM	#2
ONjA DriverHeaven Junior Member Join Date: Sep 2005 Posts: 38 Rep Power: 0	Pageable section or allocated block of memory can be swapped out of physical memory to a page file. But when it needed again, it can be accessed only at certain priority level (not above the priority of system service, which brings back that block of memory). This requires more attention on priority lowering/rising. Nonpageable can be accessed at any time, but always consumes physical memory.