Меню Рубрики

For any windows updates you might need run the driver verifier against

For any windows updates you might need run the driver verifier against

Здравствуйте, после сбора машины и установки всего нужного, машина нормально проработала несколько дней, WinXP была полностью автоматически обновлена.
Теперь после загрузки и непродолжительной работы от 2 до 15 минут, вылетает синий экран следующего содержания:

Run the driver verifier aganst any new (or) suspect drivers.
If that doesn’t reveal the corrupting driver, try enabling special pool. Both of these features are intended to catch the corrupting at an earlier point where the offending driver can be identified.

Далее он предлагает загрузиться в Safe Mode и отключать постепенно железо и софт. А так же в биос выключить shadow buffering, это вроде к памяти относится, но в биосе такой фишки нет.

Код ошибки:
STOP: **00000005 (**21ea8f34, **00000002, **00000000, **8054b0ba)

Завершение:
Begining dump of physical memory
Physical memory dump complete.

Подскажите в каком направлении двигаться.

Конфигурация компьютера:
1. Intel «Core 2 Duo E4600» (2.40ГГц, 2МБ, 800МГц, EM64T) Socket775 (Box)
2. Мат. плата Socket775 GIGABYTE «GA-P35-S3G» (iP35)
3. 2х1ГБ DDR2 SDRAM Kingston «ValueRAM» KVR800D2N5/1G (PC6400, 800МГц, CL5) (установлены в 1 и 3 слот)
4. 320ГБ Seagate «Barracuda 7200.11 ST3320613AS» 7200об./мин., 16МБ (SATA II)
5. PCI-E 256МБ Gainward «Bliss 8600GT PCX SilentFX» 8859 (GeForce 8600 GT, DDR3, D-Sub, DVI, HDMI) (рабочая температура по родной утилите — 50-60 градусов, он с большим радиатором)
6. Корпус Miditower IN-WIN «IW-C583» ATX 2.03, черно-серебр. (350Вт, ATX12V V1.3)

Не маловато для такого запака?
Понимаю, что не аргумент, но в магазине уверяли, что 350Вт достаточно, хотел 450Вт, в наличии не оказалось, а бюджет строго ограничен был. Сначала, думал про видео, там пассивное охлаждение, а фирменная утилита показывает температуру граф. ядра 50-55 градусов.

2 Sharer,
Юзал поиск, именно такого ответа не нашел, или пропустил. Исправлюсь.
Через недельку попробую планки перевтыкать. Shadow memory в биосе не нашел.
Есть еще одна зацепка, биос в режиме авто ставит тайминги 5-5-5-18, на сайте Kingston тайминги 5-5-5-15, это может как-то влиять на ситуацию?
Повторюсь, неделю компьютер нормально работал, а тут такое.
Доступ к машине будет, через неделю, если не получится, не ругайтесь, обращусь за помощью снова. 😉

Источник

Driver Verifier— tracking down a mis-behaving driver.

Technical Level : Intermediate

Summary
Driver verifier is a utility built into the OS (Vista, WIN 7, Win 8, and win 10) that will often find the driver/drivers that are the underlying cause of BSOD/Crashes It is an «iffy» proposition because it will not ALWAYS tell us which driver it was, but it is the best way to narrow down the possibilities
Details

Most times it will crash and tell you what the driver is, but sometimes it will crash and not tell you the driver.

Other times it will crash before you can log in to Windows. In Any case please note what you see on the screen and upload the DMP files to us for analysis.

I’d suggest that you first backup your data just in case

You should not be running verifier in safe mode because many drivers do not load in safe mode. If you want to add safe mode to the boot menu You can enable this here

Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).


Be sure you can get back into safe mode to turn off verifier or you may may brick your computer The command to turn verifier off is verifier /reset launched from an elevated command prompt

Here is the procedure:
Go to Start and type in «verifier» (without the quotes) and press Enter (win 10 may be different when it is released)
Select «Create custom settings (for code developers)» and click «Next«

Select everything. For Win 8 and win 10 dont check DDI compliance checking and randomized low resource simulation, then click «Next«


Select «Select driver names from a list» and click «Next»

Then select all drivers NOT provided by Microsoft and click «Next»

Select «Finish»

Please make sure it is running by opening an elevated command prompt and typing verifier /querysettings It should return a list of drivers (we do not care which ATM). If it does not it is NOT running

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.

If it doesn’t crash for you, then let it run for at least 36 hours of continuous operation.

When it crashes use these instructions to find & upload the log files (called DMP files) to us

When it crashes it will say something like DRIVER_VERIFIED_DETECTED_VIOLATION (xxxxx.sys) The xxxx.sys is the name of the driver that caused the crash. If it is listed please note it and tell us what it is.


If you can’t get into Windows because it crashes too soon, try it in Safe Mode. (For win 8 try msconfig here is how) and to disable verifier type the following. Verifier /reset

If you can’t get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

When the problem has been fixed be sure to turn off verifier by typing verifier /reset from an elevated command prompt

‘If you have a question about this topic, Ask the community’.

If this wiki has proved helpful please click me too at the bottom of the wiki.

Other Wiki’s you may be interested in

Источник

Driver Verifier

Driver Verifier monitors Windows kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject Windows drivers to a variety of stresses and tests to find improper behavior. You can configure which tests to run, which allows you to put a driver through heavy stress loads or through more streamlined testing. You can also run Driver Verifier on multiple drivers simultaneously, or on one driver at a time.

  • Running Driver Verifier could cause the computer to crash.
  • You should only run Driver Verifier on computers that you are using for testing and debugging.
  • You must be in the Administrators group on the computer to use Driver Verifier.
  • Driver Verifier is not included in Windows 10 S, so we recommend testing driver behavior on Windows 10 instead.

Where can I download Driver Verifier?

You don’t need to download Driver Verifier, because it is included with most versions of Windows in %WinDir%\system32\ as Verifier.exe. (Driver Verifier is not included with Windows 10 S.) Driver Verifier is not distributed separately as a download package.

For information about changes in Driver Verifier for Windows 10 and previous versions of Windows, see Driver Verifier: What’s New.

When to use Driver Verifier

Run Driver Verifier throughout development and testing of your driver. More specifically, use Driver Verifier for the following purposes:

To find problems early in the development cycle, when they are easier and less costly to correct.

For troubleshooting and debugging test failures and computer crashes.

To monitor behavior when you deploy a driver for testing using the WDK, Visual Studio, and the tests from the Windows Hardware Lab Kit (Windows HLK) or Windows Hardware Certification Kit (for Windows 8.1). For more information about testing drivers, see Testing a Driver.

How to start Driver Verifier

You should only run Driver Verifier on test computers, or on computers that you are testing and debugging. To get the most benefit from Driver Verifier, you should use a kernel debugger and connect to the test computer. For more information about debugging tools, see Debugging Tools for Windows (WinDbg, KD, CDB, NTSD).

Start a Command Prompt window by selecting Run as administrator, and type verifier to open Driver Verifier Manager.

Select Create standard settings (the default task), and select Next.

You can also choose Create custom settings to select from predefined settings, or to select individual options. For more information, see Driver Verifier options and rule classes and Selecting Driver Verifier Options.

Under Select what drivers to verify, choose one of the selection schemes described in the following table.

Useful for testing on computers that are running versions of Windows that do not require signed drivers.

Useful for testing driver compatibility with newer versions of Windows.

Provides maximum coverage in terms of the number of drivers that are tested on a system. This option is useful for test scenarios where a driver can interact with other devices or drivers on a system.

This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance.

In most cases, you will want to specify which drivers to test.

Selecting all drivers in a device stack allows the Enhanced I/O Verification option to track objects and check compliance because an I/O request packet (IRP) is passed between each of the drivers in the stack, which allows for a greater level of detail to be provided when an error is detected.

Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues (such as deadlocks or mutexes). The Special Pool and I/O Verification options are more effective when used on one driver at a time.

If you chose Select driver names from a list, select Next, and then select one or more specific drivers.

Select Finish, and then restart the computer.

You can also run Driver Verifier in a Command Prompt window without starting Driver Verifier Manager. For example, to run Driver Verifier with the standard settings on a driver called myDriver.sys, you would use the following command:

For more information about command line options, see Driver Verifier Command Syntax.

How to control Driver Verifier

You can use either Driver Verifier Manager or a command line to control Driver Verifier. To start Driver Verifier Manager, see How to start Driver Verifier, earlier in this topic.

For each of the following actions, you can use Driver Verifier Manager or enter a command line.

To stop or reset Driver Verifier

In Driver Verifier Manager, select Delete existing settings, and then select Finish.

Enter the following command at a command prompt:

Restart the computer.

To view Driver Verifier statistics

In Driver Verifier Manager, select Display information about the currently verified drivers, and then select Next. Continuing to select Next displays additional information.

Enter the following command at a command prompt:

To view Driver Verifier settings

In Driver Verifier Manager, select Display existing settings, and then select Next.

Enter the following command at a command prompt:

How to debug Driver Verifier violations

To get the most benefit from Driver Verifier, you should use a kernel debugger and connect it to the test computer. For an overview of debugging tools for Windows, see Debugging Tools for Windows (WinDbg, KD, CDB, NTSD).

If Driver Verifier detects a violation, it generates a bug check to stop the computer. This is to provide you with the most information possible for debugging the issue. When you have a kernel debugger connected to a test computer that is running Driver Verifier, and Driver Verifier detects a violation, Windows breaks into the debugger and displays a brief description of the error.

All violations detected by Driver Verifier result in bug checks. Common bug check codes include the following:

When you start a new debugging session, use the debugger extension command, !analyze. In kernel mode, the !analyze command displays information about the most recent bug check. To display additional information, to help identify the faulting driver, add option -v to the command at the kd> prompt:

In addition to !analyze, you can enter the following debugger extensions at the kd> prompt to view information that is specific to Driver Verifier:

!verifier dumps captured Driver Verifier statistics. Use !verifier -? to display all of the available options.

!deadlock displays information related to locks or objects tracked by Driver Verifier’s deadlock detection feature. Use !deadlock -? to display all of the available options.

!iovirp [address] displays information related to an IRP tracked by I/O Verifier. For example:

!ruleinfo [RuleID] displays information related to the DDI compliance checking rule that was violated. (RuleID is always the first argument to the bug check.) All rule IDs from DDI compliance checking are in the form 0x200nn. For example:

Источник

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *

  • Flags ищите prefer html over flash mac windows linux chrome os
  • Fix problems that are preventing windows from starting
  • First part of windows xp professional sp3 setup from partition 0 что это
  • First part of windows xp professional sp3 setup from partition 0 перевод
  • Find the right variant there three windows in my room


    • Option Recommended use
    Automatically select unsigned drivers
    Automatically select drivers built for older versions of Windows
    Automatically select all drivers installed on this computer