View Full Version : Fage_fault_in_nonpaged_area!!!!
MoreSpeed!
30-11-2001, 09:13
Chi sa dirmi come risolvere questo problema????
Il Pc si spegne spesso causa questo errore, sospetto che sia dovuto al modem (un AtlantisLand Isnd Usb esterno)
io ho il tuo stesso problema ma o me in avvio mi fa la schermata blu e mi dice questo errore. io come modem ho un US robotics fax interno.
Penso di avere lo stesso problema. Ho postato anche io una cosa del genere un pòmpiùnsotto
ma non potrebbe essere data dalla scheda video
MoreSpeed!
30-11-2001, 12:24
Ho provato con 3/4 driver per la mia scheda video e ora ho installato i driver Detonator XP 21.83 (o qualcosa del genere) e non penso siano quelli visto che sono anche certificati Microsoft.
Ultime nuove: ieri mi si è piantato 3/4 volte di seguito ogni volta che entravo in internet.
Oggi mi si è bloccato 1 volta all'avvio, sempre lo stesso errore ma questa volta riferito al file sysaudio.sys (o qualcosa del genere :p :p :p ), ho riavviato e poi è filato tutto liscio, compreso l'accesso a internet. Potrebbe essere qualche sito internet?????
Anche a me succede la maggior parte delle volte su internet. Ho appena aggiornato i driver del modem (Message Plus V90 esterno).
Speriamo bene.
ragazzi io ho gli ultimi drive per il modem e gli ultimi detenator ma mi fanno sempre lo stesso casino
ragazzi è possibile che dipenda da uno di quei 3 troiai che a messo via in rete ora ciè 4in1 4.35, agp 4.30 e il controller eide che non mi ricordo la versione . dai raga sotto con le idee
MoreSpeed!
30-11-2001, 16:52
Questa è solo la mia teoria ma potete confermarla:
Allora, come ho dettoa me succede spesso che vada in errore quando mi collego ad internet...
e non è tutto! Precisamente quando provo ad aprire un sito di chat (www.ten-percent.com) per la precisione una chat JAVA!!! vi viene in mente nulla???
:cool: :cool: :cool:
non lo so perchè te lo detto e me invece in fase di avvio ma nessuno so cosa vuol dire questa frase
MoreSpeed!
30-11-2001, 17:46
Ma come, non vi viene in mente che con win xp non c'è nessuna console java (causa i soliti problemi legali di microsoft) installata e che per vedere un sito java bisogna installarla???
Potrebbe essere proprio questo il problema
puo darsi ma a me a date problemi con l'istazione dei ultimi 4in1
MoreSpeed!
02-12-2001, 11:19
Allora raga, nessuno ha + provato???
Fatevi sentire!
Ciao ragazzi,
sul Technet quel tipo di errore é documentato. Vi consiglio di dargli una letta. Ciao
Originariamente inviato da mario78
[B]Ciao ragazzi,
sul Technet quel tipo di errore é documentato. Vi consiglio di dargli una letta. Ciao
puoi postare un link
mario78 potresti postare un link, preferibilmente diretto? Grazie.
Comunque a me dopo circa tre giorni che ho aggiornato i driver del modem, l'errore non si è più presentato.
Bho!
MoreSpeed!
02-12-2001, 14:38
Se puoi farci un favore posta l'url per tutti Thanks!
MoreSpeed!
03-12-2001, 12:22
c'è nessuno???
MoreSpeed!
03-12-2001, 17:33
MARIOOOOOO
Debugging Driver Verifier Violations
------------------------------------
Both the !verifier command in the kernel debugger and the Verifier.exe tool show
the current Driver Verifier configuration and statistics in real time.
All Driver Verifier violations result in bug checks, the most common ones
(although not necessarily all of them) are:
- IRQL_NOT_LESS_OR_EQUAL 0xA
- PAGE_FAULT_IN_NONPAGED_AREA 0x50
- PAGE_FAULT_IN_NONPAGED_AREA 0x50
- ATTEMPTED_WRITE_TO_READONLY_MEMORY 0xBE
- SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0xC1
- DRIVER_VERIFIER_DETECTED_VIOLATION 0xC4
- DRIVER_CAUGHT_MODIFYING_FREED_POOL 0xC6
- TIMER_OR_DPC_INVALID 0xC7
- DRIVER_VERIFIER_IOMANAGER_VIOLATION 0xC9
Driver Verifier and Graphics Drivers
------------------------------------
Windows 2000 kernel-mode graphics drivers (such as printer and display driver
DLLs) are restricted from calling the pool entry point directly. Rather, pool
allocations are performed indirectly using graphics device driver interface
(DDI) callbacks to Win32k.sys. For example, EngAllocMem is the callback that a
graphics driver calls to explicitly allocate pool memory. Also, other
specialized callbacks such as EngCreatePalette and EngCreateBitmap return pool
memory.
To provide the same sort of automated testing for the graphics drivers, support
for some of the Driver Verifier functions is incorporated into Win32k.sys.
However, because graphics drivers are more restricted than other kernel-mode
drivers, they require only a subset of the Driver Verifier functionality.
Specifically, IRQL checking and I/O verification are not needed. The other
functionality, namely using special pool, random failure of pool allocations,
and pool tracking, are supported to varying degrees in the different graphics
DDI callbacks.
Random failures are supported for the following graphics DDI callback functions:
- EngAllocMem
- EngAllocUserMem
- EngCreateBitmap
- EngCreateDeviceSurface
- EngCreateDeviceBitmap
- EngCreatePalette
- EngCreateClip
- EngCreatePath
- EngCreateWnd
- EngCreateDriverObj
- BRUSHOBJ_pvAllocRbrush
- CLIPOBJ_ppoGetPath
In addition, the use of special pool and pool tracking is supported for
EngAllocMem.
Enabling Driver Verifier for the graphics drivers is identical to the other
drivers (refer to the "Enabling Driver Verifier" section of this article for
additional information). Unsupported flags such as IRQL checking are ignored. In
addition, you can use the !gdikdx.verifier kernel-debugger command to examine
current Driver Verifier state and pool traces for graphics drivers.
NOTE: You should only use the random allocation failure setting for robustness
testing. Use of this setting may cause rendering error messages, so you should
not use this setting with verification tests to check the correctness of the
graphics driver's implementation (for example, by comparing the graphics driver
output to a reference image).
Driver Verifier Manager (Verifier.exe)
--------------------------------------
The Driver Verifier Manager tool (Verifier.exe) is the preferred way to create
and modify Driver Verifier settings and to gather statistics from Driver
Verifier. Verifier.exe is located in the %WinDir%\System32 folder for every
Windows 2000 installation.
Driver Status:
The Driver Status property page gives you an image of the current status of
Driver Verifier. You can see what drivers the verifier detects. The status can
be one of the following:
- Loaded: The driver is currently loaded and verified.
- Unloaded: The driver is not currently loaded but it was loaded at least once
since you restarted the computer.
- Never Loaded: The driver was never loaded. This status can indicate that the
driver's image file is corrupted or that you specified a driver name that is
missing from the system.
You can click the list header to sort the list by driver names or status. In the
upper-right area of the dialog box, you can view the current types of the
verification that are in effect. The status of the drivers is updated
automatically if you do not switch to manual refresh mode. You can modify the
refresh rate using the radio buttons in the lower-left area of the dialog box.
You can also force an update of the status by clicking Update Now.
If you enable the Special Pool flag and less than 95 percent of the pool
allocations went to the special pool, a warning message is displayed on this
page. This means that you need to select a smaller set of drivers to verify or
add more physical memory to the computer to obtain better coverage of the pool
allocations verification.
Global Counters
---------------
The Global Counters property page shows the current value of some counters
maintained by Driver Verifier. A zero value for a counter can indicate that the
associated Driver Verifier flag is not enabled. For example, a value of 0 for
the Other/Faults counter indicates that the low resource simulation flag is not
enabled. You can monitor the activity of the verifier because the values of the
counters are updated automatically (by default). You can change the refresh
rate, switch to manual refresh, or force a refresh using the group of controls
in the lower-left area of the dialog box.
Pool Tracking
-------------
This property page shows more statistics gathered from Driver Verifier. All of
the counters shown on this page are related to the Pool Tracking flag of the
verifier. Most of them are per-driver counters (for example, current
allocations, current allocated bytes, and so on). This means you must select a
driver name from the top combination box to view the counters for that specific
driver.
Settings
--------
You can use this page to create and modify Driver Verifier settings. The settings
are saved in the registry and you must restart the computer for the settings to
take effect. You can use the list to view the currently installed drivers. Each
driver can be in one of the following states:
- Verify Enabled: The driver is currently verified.
- Verify Disabled: The driver is currently not verified.
- Verify Enabled (Reboot Needed): The driver is verified only after the next
restart.
- Verify Disabled (Reboot Needed): The driver is currently verified but is not
verified after the next restart.
You can select one or several drivers from the list and switch the status using
the two buttons under the list. You can also right-click a driver name to
display the context menu, which lets you perform state toggling.
In the bottom of the dialog box, you can specify additional drivers (separated by
spaces) that you want verified after the next restart. You typically use this
edit control when you want to install a new driver that is not already loaded.
If the radio button group on the top of the list is set to Verify all drivers,
the list and the Verify and Don't Verify buttons and the edit control are
unavailable. This means that after the next restart, all the drivers in the
system are verified.
You can set the verification type using the check boxes in the upper-right area
of the dialog box. You can enable I/O Verification at level 1 or at level 2.
Level 2 verification is stronger than level 1.
You must save any modification to the settings by clicking Apply. There are two
more buttons in this page:
- Preferred Settings: This selects some commonly used settings (with all
drivers verified).
- Reset All: This clears all the Driver Verifier settings so that no drivers
are verified.
After you click Apply, you must restart the computer for the changes to take
effect.
Volatile Settings
-----------------
You can use this property page to change the Driver Verifier flags immediately.
You can only toggle the state of some of the Driver Verifier flags and you
cannot change the list of the drivers that are being verified. After you change
the status of some check boxes, you must click Apply for the changes to take
effect. The changes take effect immediately and they last until you make
additional changes or until you restart the computer.
The Command-Line Interface
--------------------------
You can also run Verifier.exe from a command line (for more information, type
"verifier.exe /?" (without the quotation marks) at a command prompt). The
following list shows the most commonly used command line flags:
- verifier.exe /flags <value> [/iolevel 2]
Specifies a decimal value of the Driver Verifier flags and possibly the level
for the I/O verification (for a list of available flags, type "verifier.exe
/?" (without the quotation marks) at a command prompt or refer to the
"Enabling Driver Verifier" section of this article).
Replace the <value> parameter with one of the following verification bit
values:
0 - Special pool checking
1 - Force IRQL checking
2 - Low resources simulation
3 - Pool tracking
4 - I/O verification
For example, type the following command:
c:\verifier /flags 3 /iolevel 2
NOTE: The default I/O verification level is 1. The value is ignored if the I/O
verification bit is not set in flags.
- verifier.exe /all
Verifies all the drivers in the system.
- verifier.exe /volatile /flags <value>
Changes verifier flags immediately.
- verifier.exe /reset
Erases all current Driver Verifier settings.
- verifier /query
Dump the current Driver Verifier status and counters to the standard output.
- verifier.exe /log LOG_FILE_NAME [/interval <seconds>]
Logs the Driver Verifier status and counters to a log file (where
<seconds> is the period of time you specify).
Additional query words: bugcheck
======================================================================
Keywords : kbenv kbprogramming KBW2KHOME
Technology : kbwin2000AdvServ kbwin2000AdvServSearch kbwin2000DataServ kbwin2000DataServSearch kbwin2000Serv kbwin2000ServSearch kbwin2000Search kbwin2000ProSearch kbwin2000Pro kbWinAdvServSearch kbWinDataServSearch
Version : WINDOWS:2000
Issue type : kbhowto
=============================================================================
Copyright Microsoft Corporation 2000.
Originariamente inviato da mario78
[B]Debugging Driver Verifier Violations
------------------------------------
Both the !verifier command in the kernel debugger and the Verifier.exe tool show
the current Driver Verifier configuration and statistics in real time.
All Driver Verifier violations result in bug checks, the most common ones
(although not necessarily all of them) are:
- IRQL_NOT_LESS_OR_EQUAL 0xA
- PAGE_FAULT_IN_NONPAGED_AREA 0x50
- PAGE_FAULT_IN_NONPAGED_AREA 0x50
- ATTEMPTED_WRITE_TO_READONLY_MEMORY 0xBE
- SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0xC1
- DRIVER_VERIFIER_DETECTED_VIOLATION 0xC4
- DRIVER_CAUGHT_MODIFYING_FREED_POOL 0xC6
- TIMER_OR_DPC_INVALID 0xC7
- DRIVER_VERIFIER_IOMANAGER_VIOLATION 0xC9
Driver Verifier and Graphics Drivers
------------------------------------
Windows 2000 kernel-mode graphics drivers (such as printer and display driver
DLLs) are restricted from calling the pool entry point directly. Rather, pool
allocations are performed indirectly using graphics device driver interface
(DDI) callbacks to Win32k.sys. For example, EngAllocMem is the callback that a
graphics driver calls to explicitly allocate pool memory. Also, other
specialized callbacks such as EngCreatePalette and EngCreateBitmap return pool
memory.
To provide the same sort of automated testing for the graphics drivers, support
for some of the Driver Verifier functions is incorporated into Win32k.sys.
However, because graphics drivers are more restricted than other kernel-mode
drivers, they require only a subset of the Driver Verifier functionality.
Specifically, IRQL checking and I/O verification are not needed. The other
functionality, namely using special pool, random failure of pool allocations,
and pool tracking, are supported to varying degrees in the different graphics
DDI callbacks.
Random failures are supported for the following graphics DDI callback functions:
- EngAllocMem
- EngAllocUserMem
- EngCreateBitmap
- EngCreateDeviceSurface
- EngCreateDeviceBitmap
- EngCreatePalette
- EngCreateClip
- EngCreatePath
- EngCreateWnd
- EngCreateDriverObj
- BRUSHOBJ_pvAllocRbrush
- CLIPOBJ_ppoGetPath
In addition, the use of special pool and pool tracking is supported for
EngAllocMem.
Enabling Driver Verifier for the graphics drivers is identical to the other
drivers (refer to the "Enabling Driver Verifier" section of this article for
additional information). Unsupported flags such as IRQL checking are ignored. In
addition, you can use the !gdikdx.verifier kernel-debugger command to examine
current Driver Verifier state and pool traces for graphics drivers.
NOTE: You should only use the random allocation failure setting for robustness
testing. Use of this setting may cause rendering error messages, so you should
not use this setting with verification tests to check the correctness of the
graphics driver's implementation (for example, by comparing the graphics driver
output to a reference image).
Driver Verifier Manager (Verifier.exe)
--------------------------------------
The Driver Verifier Manager tool (Verifier.exe) is the preferred way to create
and modify Driver Verifier settings and to gather statistics from Driver
Verifier. Verifier.exe is located in the %WinDir%\System32 folder for every
Windows 2000 installation.
Driver Status:
The Driver Status property page gives you an image of the current status of
Driver Verifier. You can see what drivers the verifier detects. The status can
be one of the following:
- Loaded: The driver is currently loaded and verified.
- Unloaded: The driver is not currently loaded but it was loaded at least once
since you restarted the computer.
- Never Loaded: The driver was never loaded. This status can indicate that the
driver's image file is corrupted or that you specified a driver name that is
missing from the system.
You can click the list header to sort the list by driver names or status. In the
upper-right area of the dialog box, you can view the current types of the
verification that are in effect. The status of the drivers is updated
automatically if you do not switch to manual refresh mode. You can modify the
refresh rate using the radio buttons in the lower-left area of the dialog box.
You can also force an update of the status by clicking Update Now.
If you enable the Special Pool flag and less than 95 percent of the pool
allocations went to the special pool, a warning message is displayed on this
page. This means that you need to select a smaller set of drivers to verify or
add more physical memory to the computer to obtain better coverage of the pool
allocations verification.
Global Counters
---------------
The Global Counters property page shows the current value of some counters
maintained by Driver Verifier. A zero value for a counter can indicate that the
associated Driver Verifier flag is not enabled. For example, a value of 0 for
the Other/Faults counter indicates that the low resource simulation flag is not
enabled. You can monitor the activity of the verifier because the values of the
counters are updated automatically (by default). You can change the refresh
rate, switch to manual refresh, or force a refresh using the group of controls
in the lower-left area of the dialog box.
Pool Tracking
-------------
This property page shows more statistics gathered from Driver Verifier. All of
the counters shown on this page are related to the Pool Tracking flag of the
verifier. Most of them are per-driver counters (for example, current
allocations, current allocated bytes, and so on). This means you must select a
driver name from the top combination box to view the counters for that specific
driver.
Settings
--------
You can use this page to create and modify Driver Verifier settings. The settings
are saved in the registry and you must restart the computer for the settings to
take effect. You can use the list to view the currently installed drivers. Each
driver can be in one of the following states:
- Verify Enabled: The driver is currently verified.
- Verify Disabled: The driver is currently not verified.
- Verify Enabled (Reboot Needed): The driver is verified only after the next
restart.
- Verify Disabled (Reboot Needed): The driver is currently verified but is not
verified after the next restart.
You can select one or several drivers from the list and switch the status using
the two buttons under the list. You can also right-click a driver name to
display the context menu, which lets you perform state toggling.
In the bottom of the dialog box, you can specify additional drivers (separated by
spaces) that you want verified after the next restart. You typically use this
edit control when you want to install a new driver that is not already loaded.
If the radio button group on the top of the list is set to Verify all drivers,
the list and the Verify and Don't Verify buttons and the edit control are
unavailable. This means that after the next restart, all the drivers in the
system are verified.
You can set the verification type using the check boxes in the upper-right area
of the dialog box. You can enable I/O Verification at level 1 or at level 2.
Level 2 verification is stronger than level 1.
You must save any modification to the settings by clicking Apply. There are two
more buttons in this page:
- Preferred Settings: This selects some commonly used settings (with all
drivers verified).
- Reset All: This clears all the Driver Verifier settings so that no drivers
are verified.
After you click Apply, you must restart the computer for the changes to take
effect.
Volatile Settings
-----------------
You can use this property page to change the Driver Verifier flags immediately.
You can only toggle the state of some of the Driver Verifier flags and you
cannot change the list of the drivers that are being verified. After you change
the status of some check boxes, you must click Apply for the changes to take
effect. The changes take effect immediately and they last until you make
additional changes or until you restart the computer.
The Command-Line Interface
--------------------------
You can also run Verifier.exe from a command line (for more information, type
"verifier.exe /?" (without the quotation marks) at a command prompt). The
following list shows the most commonly used command line flags:
- verifier.exe /flags <value> [/iolevel 2]
Specifies a decimal value of the Driver Verifier flags and possibly the level
for the I/O verification (for a list of available flags, type "verifier.exe
/?" (without the quotation marks) at a command prompt or refer to the
"Enabling Driver Verifier" section of this article).
Replace the <value> parameter with one of the following verification bit
values:
0 - Special pool checking
1 - Force IRQL checking
2 - Low resources simulation
3 - Pool tracking
4 - I/O verification
For example, type the following command:
c:\verifier /flags 3 /iolevel 2
NOTE: The default I/O verification level is 1. The value is ignored if the I/O
verification bit is not set in flags.
- verifier.exe /all
Verifies all the drivers in the system.
- verifier.exe /volatile /flags <value>
Changes verifier flags immediately.
- verifier.exe /reset
Erases all current Driver Verifier settings.
- verifier /query
Dump the current Driver Verifier status and counters to the standard output.
- verifier.exe /log LOG_FILE_NAME [/interval <seconds>]
Logs the Driver Verifier status and counters to a log file (where
<seconds> is the period of time you specify).
Additional query words: bugcheck
======================================================================
Keywords : kbenv kbprogramming KBW2KHOME
Technology : kbwin2000AdvServ kbwin2000AdvServSearch kbwin2000DataServ kbwin2000DataServSearch kbwin2000Serv kbwin2000ServSearch kbwin2000Search kbwin2000ProSearch kbwin2000Pro kbWinAdvServSearch kbWinDataServSearch
Version : WINDOWS:2000
Issue type : kbhowto
=============================================================================
Copyright Microsoft Corporation 2000.
Non ci ho capito un granchè, qualcuno mi puo spiegare come risolvere il problema? Non mastico troppo bene l'inglese!
Comunque gli errori su schermata blu che mi si presentano sono:
- IRQL_NOT_LESS_OR_EQUAL 0xA
- PAGE_FAULT_IN_NONPAGED_AREA 0x50
Grazie.
Sono riuscito a capire che bisogna lanciare il file verifier.exe!
E poi???????????????????????''
Spiegatemelo voi.
Ciao.
Qualcuno ha delle novità?
Originariamente inviato da mario78
[B]Debugging Driver Verifier Violations
------------------------------------
Both the !verifier command in the kernel debugger and the Verifier.exe tool show
the current Driver Verifier configuration and statistics in real time.
All Driver Verifier violations result in bug checks, the most common ones
(although not necessarily all of them) are:
- IRQL_NOT_LESS_OR_EQUAL 0xA
- PAGE_FAULT_IN_NONPAGED_AREA 0x50
- PAGE_FAULT_IN_NONPAGED_AREA 0x50
- ATTEMPTED_WRITE_TO_READONLY_MEMORY 0xBE
- SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0xC1
- DRIVER_VERIFIER_DETECTED_VIOLATION 0xC4
- DRIVER_CAUGHT_MODIFYING_FREED_POOL 0xC6
- TIMER_OR_DPC_INVALID 0xC7
- DRIVER_VERIFIER_IOMANAGER_VIOLATION 0xC9
Driver Verifier and Graphics Drivers
------------------------------------
Windows 2000 kernel-mode graphics drivers (such as printer and display driver
DLLs) are restricted from calling the pool entry point directly. Rather, pool
allocations are performed indirectly using graphics device driver interface
(DDI) callbacks to Win32k.sys. For example, EngAllocMem is the callback that a
graphics driver calls to explicitly allocate pool memory. Also, other
specialized callbacks such as EngCreatePalette and EngCreateBitmap return pool
memory.
To provide the same sort of automated testing for the graphics drivers, support
for some of the Driver Verifier functions is incorporated into Win32k.sys.
However, because graphics drivers are more restricted than other kernel-mode
drivers, they require only a subset of the Driver Verifier functionality.
Specifically, IRQL checking and I/O verification are not needed. The other
functionality, namely using special pool, random failure of pool allocations,
and pool tracking, are supported to varying degrees in the different graphics
DDI callbacks.
Random failures are supported for the following graphics DDI callback functions:
- EngAllocMem
- EngAllocUserMem
- EngCreateBitmap
- EngCreateDeviceSurface
- EngCreateDeviceBitmap
- EngCreatePalette
- EngCreateClip
- EngCreatePath
- EngCreateWnd
- EngCreateDriverObj
- BRUSHOBJ_pvAllocRbrush
- CLIPOBJ_ppoGetPath
In addition, the use of special pool and pool tracking is supported for
EngAllocMem.
Enabling Driver Verifier for the graphics drivers is identical to the other
drivers (refer to the "Enabling Driver Verifier" section of this article for
additional information). Unsupported flags such as IRQL checking are ignored. In
addition, you can use the !gdikdx.verifier kernel-debugger command to examine
current Driver Verifier state and pool traces for graphics drivers.
NOTE: You should only use the random allocation failure setting for robustness
testing. Use of this setting may cause rendering error messages, so you should
not use this setting with verification tests to check the correctness of the
graphics driver's implementation (for example, by comparing the graphics driver
output to a reference image).
Driver Verifier Manager (Verifier.exe)
--------------------------------------
The Driver Verifier Manager tool (Verifier.exe) is the preferred way to create
and modify Driver Verifier settings and to gather statistics from Driver
Verifier. Verifier.exe is located in the %WinDir%\System32 folder for every
Windows 2000 installation.
Driver Status:
The Driver Status property page gives you an image of the current status of
Driver Verifier. You can see what drivers the verifier detects. The status can
be one of the following:
- Loaded: The driver is currently loaded and verified.
- Unloaded: The driver is not currently loaded but it was loaded at least once
since you restarted the computer.
- Never Loaded: The driver was never loaded. This status can indicate that the
driver's image file is corrupted or that you specified a driver name that is
missing from the system.
You can click the list header to sort the list by driver names or status. In the
upper-right area of the dialog box, you can view the current types of the
verification that are in effect. The status of the drivers is updated
automatically if you do not switch to manual refresh mode. You can modify the
refresh rate using the radio buttons in the lower-left area of the dialog box.
You can also force an update of the status by clicking Update Now.
If you enable the Special Pool flag and less than 95 percent of the pool
allocations went to the special pool, a warning message is displayed on this
page. This means that you need to select a smaller set of drivers to verify or
add more physical memory to the computer to obtain better coverage of the pool
allocations verification.
Global Counters
---------------
The Global Counters property page shows the current value of some counters
maintained by Driver Verifier. A zero value for a counter can indicate that the
associated Driver Verifier flag is not enabled. For example, a value of 0 for
the Other/Faults counter indicates that the low resource simulation flag is not
enabled. You can monitor the activity of the verifier because the values of the
counters are updated automatically (by default). You can change the refresh
rate, switch to manual refresh, or force a refresh using the group of controls
in the lower-left area of the dialog box.
Pool Tracking
-------------
This property page shows more statistics gathered from Driver Verifier. All of
the counters shown on this page are related to the Pool Tracking flag of the
verifier. Most of them are per-driver counters (for example, current
allocations, current allocated bytes, and so on). This means you must select a
driver name from the top combination box to view the counters for that specific
driver.
Settings
--------
You can use this page to create and modify Driver Verifier settings. The settings
are saved in the registry and you must restart the computer for the settings to
take effect. You can use the list to view the currently installed drivers. Each
driver can be in one of the following states:
- Verify Enabled: The driver is currently verified.
- Verify Disabled: The driver is currently not verified.
- Verify Enabled (Reboot Needed): The driver is verified only after the next
restart.
- Verify Disabled (Reboot Needed): The driver is currently verified but is not
verified after the next restart.
You can select one or several drivers from the list and switch the status using
the two buttons under the list. You can also right-click a driver name to
display the context menu, which lets you perform state toggling.
In the bottom of the dialog box, you can specify additional drivers (separated by
spaces) that you want verified after the next restart. You typically use this
edit control when you want to install a new driver that is not already loaded.
If the radio button group on the top of the list is set to Verify all drivers,
the list and the Verify and Don't Verify buttons and the edit control are
unavailable. This means that after the next restart, all the drivers in the
system are verified.
You can set the verification type using the check boxes in the upper-right area
of the dialog box. You can enable I/O Verification at level 1 or at level 2.
Level 2 verification is stronger than level 1.
You must save any modification to the settings by clicking Apply. There are two
more buttons in this page:
- Preferred Settings: This selects some commonly used settings (with all
drivers verified).
- Reset All: This clears all the Driver Verifier settings so that no drivers
are verified.
After you click Apply, you must restart the computer for the changes to take
effect.
Volatile Settings
-----------------
You can use this property page to change the Driver Verifier flags immediately.
You can only toggle the state of some of the Driver Verifier flags and you
cannot change the list of the drivers that are being verified. After you change
the status of some check boxes, you must click Apply for the changes to take
effect. The changes take effect immediately and they last until you make
additional changes or until you restart the computer.
The Command-Line Interface
--------------------------
You can also run Verifier.exe from a command line (for more information, type
"verifier.exe /?" (without the quotation marks) at a command prompt). The
following list shows the most commonly used command line flags:
- verifier.exe /flags <value> [/iolevel 2]
Specifies a decimal value of the Driver Verifier flags and possibly the level
for the I/O verification (for a list of available flags, type "verifier.exe
/?" (without the quotation marks) at a command prompt or refer to the
"Enabling Driver Verifier" section of this article).
Replace the <value> parameter with one of the following verification bit
values:
0 - Special pool checking
1 - Force IRQL checking
2 - Low resources simulation
3 - Pool tracking
4 - I/O verification
For example, type the following command:
c:\verifier /flags 3 /iolevel 2
NOTE: The default I/O verification level is 1. The value is ignored if the I/O
verification bit is not set in flags.
- verifier.exe /all
Verifies all the drivers in the system.
- verifier.exe /volatile /flags <value>
Changes verifier flags immediately.
- verifier.exe /reset
Erases all current Driver Verifier settings.
- verifier /query
Dump the current Driver Verifier status and counters to the standard output.
- verifier.exe /log LOG_FILE_NAME [/interval <seconds>]
Logs the Driver Verifier status and counters to a log file (where
<seconds> is the period of time you specify).
Additional query words: bugcheck
======================================================================
Keywords : kbenv kbprogramming KBW2KHOME
Technology : kbwin2000AdvServ kbwin2000AdvServSearch kbwin2000DataServ kbwin2000DataServSearch kbwin2000Serv kbwin2000ServSearch kbwin2000Search kbwin2000ProSearch kbwin2000Pro kbWinAdvServSearch kbWinDataServSearch
Version : WINDOWS:2000
Issue type : kbhowto
=============================================================================
Copyright Microsoft Corporation 2000.
Ancora nessuno lo ha decifrato?
Purtroppo il problema non è ancora scomparso perchè ancora non ho capito cosa bisogna fare con questo verifier.exe.
Voi come avete risolto?
Ciao.
vBulletin® v3.6.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.