Getting Blue Screen error STOP: 0x0000000A

Question

Here is the Error code. 

STOP: 0x0000000A (0x0000000000080010, 0x0000000000000007, 0x0000000000000000 0xFFFFF800032EA915

If anymore information is needed please don't hesitate to ask :)

Original title: BSOD help Error code inside

Answer 1

Hi,

Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows.

http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7 

Check this thread for information on using BlueScreenView, MyEventViewer, and other methods

to troubleshoot BlueScreens - top 3 methods (+1 other).

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990

We can analyze the minidumps if you make them available from the SkyDrive or other file

sharing sites (such as MediaFire). If you have problems uploading the minidumps copy

them to the Desktop or the Documents folder and upload them from there.

Zip or upload the contents of C:\Windows\minidump

Use SkyDrive to upload collected files. 

http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

---

BCCode: 0A     0x0000000A

Check these KB's

Error message on a blue screen on a computer that is running Windows 7 or Windows Server

2008 R2: "STOP: 0x0000000A"

http://support.microsoft.com/kb/979444

Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2 and

that has iSCSI storage: "0x0000000A"

http://support.microsoft.com/kb/979711

Those and 12 other KB Articles are available

http://support.microsoft.com/search/default.aspx?mode=a&query=0x0000000A&spid=14019&catalog=LCID%3D1033&1033comm=1&res=10

---

BCCode: 0A     0x0000000A

Drivers could be at fault however disk issues or antivirus/antispyware/security products are

just as likely to be the root cause as they can force a driver to corrupt or go out of bounds.

The video driver or something affecting it would be very suspect.

Be sure the drivers, BIOS, and low level chipset drivers are all updated by manually checking

at the System maker and device makers's sites.

Below I will post a generic bluescreen troubleshooter and in the next message how to update

drivers and BIOS as well as do memory checks.

---

BCCode: 0A     0x0000000ABug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

Important Info If You Have Received a STOP Code 

If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.

If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.

These actions might prevent an error like this from happening again:

1. Download and install updates and device drivers for your computer from Windows Update.
2. Scan your computer for computer viruses.
3. Check your hard disk for errors.

IRQL_NOT_LESS_OR_EQUAL Parameters

The following parameters are displayed on the blue screen.

Parameter	Description
1	Memory referenced
2	IRQL at time of reference
3	0: Read<br><br><br>1: Write
4	Address which referenced memory

Cause

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Resolution

If a kernel debugger is available, obtain a stack trace.

To resolve an error caused by a faulty device driver, system service, or BIOS

1. Restart your computer.
2. Press F8 at the character-based menu that displays the operating system choices.
3. Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.

To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

1. Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
2. Try disabling memory caching of the BIOS.
3. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
4. Make sure the latest Service Pack is installed.
5. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
6. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.

If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are compatible with the version of Windows being installed. For example, you can get information about compatibility with Windows 7 at the Windows 7 Compatibility Center.

Here is a debugging example: (See this link)http://msdn.microsoft.com/en-us/library/ff560129(v=vs.85).aspx 

BCCode: 0A     0x0000000A  <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/IRQL-NOT-LESS-OR-EQUAL-0x0000000A-\*1025.html

==================================================================

Look in the Event Viewer to see if anything is reported about those.

http://www.computerperformance.co.uk/vista/vista\_event\_viewer.htm

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.

http://www.nirsoft.net/utils/my\_event\_viewer.html

---

Also do this so you can see the likely bluescreens.

Windows Vista automatically restarts if your PC encounters an error that causes it to crash.

http://www.winvistatips.com/disable-automatic-restart-t84.html

---

Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen

info that would help. Such as the BCC and the other 4 entries on the lower left. And any other

error information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples :

BCCode: 116

BCP1: 87BC9510

BCP2: 8C013D80

BCP3: 00000000

BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)

tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table - Freehttp://www.nirsoft.net/utils/blue\_screen\_view.html

Many BlueScreens are caused by old or corrupted drivers, especially video drivers however

there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or

Recovery Options if your system has that installed by the maker.

How to Boot to the System Recovery Options in Windows 7

http://www.sevenforums.com/tutorials/668-system-recovery-options.html

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Windows 7

http://www.sevenforums.com/tutorials/700-system-restore.html

---

Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to Repair Windows 7 System Files with System File Checker

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program

generates in Windows Vista cbs.log (and Windows 7)

http://support.microsoft.com/kb/928228

The log might give you the answer if there was a corrupted driver. (Does not tell all the possible

driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.

How to Run Check Disk at Startup in Windows 7

http://www.sevenforums.com/tutorials/433-disk-check.html

---

Often updating drivers will help, usually Video, Sound, Network Card  (NIC), WiFi, 3rd party

keyboard and mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

How to Install a Device Driver in Vista Device Manager (also Windows 7) 

http://www.vistax64.com/tutorials/193584-device-manager-install-driver.html

Stop Windows 7 from Automatically Installing Device Drivers

http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/

How To Disable Automatic Driver Installation In Windows 7 / Vista

http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for Professional,

Ultimate, and Enterprise)

http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/

---

How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart

unexpectedly

http://support.microsoft.com/kb/958233

Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)

http://www.chicagotech.net/vista/vistabluescreen.htm

Understanding and Decoding BSOD (blue screen of death) Messages

http://www.taranfx.com/blog/?p=692

Windows - Troubleshooting Blue Screen Errors

http://kb.wisc.edu/page.php?id=7033

---

In some cases this might be required.

StartUp Repair from Recovery Options or Windows 7 disk

How to Run a Startup Repair in Windows 7

http://www.sevenforums.com/tutorials/681-startup-repair.html

How to Boot to the System Recovery Options in Windows 7

http://www.sevenforums.com/tutorials/668-system-recovery-options.html

How to Create a Windows 7 System Repair Disc

http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

How to Do a Repair Install to Fix Windows 7

http://www.sevenforums.com/tutorials/3413-repair-install.html

Hope this helps.

---

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

Answer 2

Hi,

If you need to check for malware here are my recommendations - these will allow you to do

a thorough check and removal without ending up with a load of spyware programs running

resident which can cause as many issues as the malware and maybe harder to detect as

the cause.

No one program can be relied upon to detect and remove all malware. Added that often easy

to detect malware is often accompanied by a much harder to detect and remove payload. So

its better to be overly thorough now than to pay the high price later. Check with these to an

extreme overkill point and then run the cleanup only when you are very sure the system is clean.

These can be done in Safe Mode - repeatedly tap F8 as you boot however you should also run 

them in regular Windows when you can.

TDSSKiller.exe. - Download to the Desktop - then go to it and Right Click on it - RUN AS ADMIN

it will show any infections in the report after running - if it will not run change the name from

tdsskiller.exe to tdsskiller.com. Whether it finds anything or not does not mean you should not

check with the other methods below.

http://support.kaspersky.com/viruses/solutions?qid=208280684

Download malwarebytes and scan with it, run MRT, and add Prevx to be sure it is gone.

(If Rootkits run UnHackMe)

Download - SAVE - go to where you put it - Right Click on it - RUN AS ADMIN

Malwarebytes - free

http://www.malwarebytes.org/products/malwarebytes_free

SuperAntiSpyware Portable Scanner - Free

http://www.superantispyware.com/portablescanner.html?tag=SAS_HOMEPAGE

Run the Microsoft Malicious Removal Tool

Start - type in Search box -> MRT  find at top of list - Right Click on it - RUN AS ADMIN.

You should be getting this tool and its updates via Windows Updates - if needed you can

download it here.

Download - SAVE - go to where you put it - Right Click on it - RUN AS ADMIN

(Then run MRT as above.)

Microsoft Malicious Removal Tool - 32 bit

http://www.microsoft.com/downloads/details.aspx?FamilyID=AD724AE0-E72D-4F54-9AB3-75B8EB148356&displaylang=en

Microsoft Malicious Removal Tool - 64 bit

http://www.microsoft.com/downloads/details.aspx?FamilyId=585D2BDE-367F-495E-94E7-6349F4EFFC74&displaylang=en

also install Prevx to be sure it is all gone.

Download - SAVE - go to where you put it - Right Click on it - RUN AS ADMIN

Prevx - Home - Free - small, fast, exceptional CLOUD protection, works with other

security programs. This is a scanner only, VERY EFFECTIVE, if it finds something come back

here or use Google to see how to remove. 

http://www.prevx.com/   <-- information

http://info.prevx.com/downloadcsi.asp?prevx=Y  <-- download

PCmag - Prevx - Editor's Choice

http://www.pcmag.com/article2/0,2817,2346862,00.asp

Try the trial version of Hitman Pro :

Hitman Pro is a second opinion scanner, designed to rescue your computer from malware

(viruses, trojans, rootkits, etc.) that have infected your computer despite all the security

measures you have taken (such as anti virus software, firewalls, etc.).

http://www.surfright.nl/en/hitmanpro

---

If needed here are some online free scanners to help

http://www.eset.com/onlinescan/

---

Original version is now replaced by the Microsoft Safety Scanner

http://onecare.live.com/site/en-us/default.htm

Microsoft Safety Scanner

http://www.microsoft.com/security/scanner/en-us/default.aspx

---

http://www.kaspersky.com/virusscanner

Other Free online scans

http://www.google.com/search?hl=en&source=hp&q=antivirus+free+online+scan&aq=f&oq=&aqi=g1

---

After removing any malware :

Also do these to cleanup general corruption and repair/replace damaged/missingsystem files.

Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to Repair Windows 7 System Files with System File Checker

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program

generates in Windows Vista cbs.log

http://support.microsoft.com/kb/928228

Also run CheckDisk so we can rule out corruption as much as possible.

How to Run Disk Check in Windows 7

http://www.sevenforums.com/tutorials/433-disk-check.html

---

If any Rootkits are found use this thread and other suggestions. (Run UnHackMe)

http://social.answers.microsoft.com/Forums/en-US/InternetExplorer/thread/a8f665f0-c793-441a-a5b9-54b7e1e7a5a4/

======================================

If needed AFTER you are sure the machine is clean of all malware. (DO NOT USE IF

MALWARE IS STILL PRESENT.)

How to Do a Repair Install to Fix Windows 7

http://www.sevenforums.com/tutorials/3413-repair-install.html

=======================================

**For extreme cases :**Norton Power Eraser - Eliminates deeply embedded and difficult to remove crimeware

that traditional virus scanning doesn't always detect. Because the Norton Power Eraser

uses aggressive methods to detect these threats, there is a risk that it can select some

legitimate programs for removal. You should use this tool very carefully, and only after

you have exhausted other options.

http://us.norton.com/support/DIY/index.jsp

================================

If you are in North America, you can call 866-727-2338 for help with virus and spyware

infections. See http://www.microsoft.com/protect/support/default.mspx for details. For

international information, see your local subsidiary Support site.

Microsoft Support - Virus and Security Solution Center

http://support.microsoft.com/contactus/cu_sc_virsec_master?ws=support#tab0

Hope this helps.

---

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

Answer 3

Hi,

**Results verified by WindDBG, DumpCHK, and BlueScreenView.**You said the Bug_Check was 0A however the minidump showed 1E so you must have had

more than on BSOD.

The Bug_Check was 1E CAUSE ntkrnlmp.exe which is a Windows component which means

something else drove it into Fault.

BugCheck 1E, {ffffffffc0000005, fffff8000358e6ea, 1, 18}

Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a )

IMAGE_NAME:  ntkrnlmp.exe

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!ObpCreateHandle+29a

BUCKET_ID:  X64_0x1E_c0000005_R_nt!ObpCreateHandle+29a

1. Remove ALL power and reseat all the cards, memory, and cables (both ends whenpossible) - actually remove and replace - do not just snug. Those are for a PC and about all

that can be done for a laptop is reseat the memory and clear the vents.

2. Check for malware very thoroughly - especially RootKits (see the methods in the next

message).

3. Make sure the BIOS, low level chipset drivers, and major device drivers are all up to date by

check manually at the makers' sites. Run DriverView - set VIEW to Hide Microsoft drivers -

update those without Dump in their name (see driver update methods in the previously

posted troubleshooters).

BiosVersion = P01-B0

BiosReleaseDate = 02/24/2010 <- check for updates to the BIOS, low level chipset drivers, and

the major on-board and separate device drivers.

SystemManufacturer = Gateway

SystemProductName = DX4300

SystemFamily = Gateway Desktop

BaseBoardManufacturer = Gateway

BaseBoardProduct = RS780

Gateway Drivers and Downloads

http://support.gateway.com/support/drivers/dlcenter.asp

Gateway Support

http://support.gateway.com/support/?cmpid=topnav

Gateway Documents

http://support.gateway.com/support/supinfo/index.asp?cmpid=topnav

4. Check the memory very thoroughly. Keep in mind that memory tests do not detect all

errors such as the tiny speed differences between memory modules that appear to be

identical. So it may be necessary to swap the modules in and out in differenct combinations

and patterns (see the memory test methods in the previously posted troubleshooters).

5. After the above, especially update BIOS, chipset, and other drivers and IF needed, run Driver

Verifier to see if it can indicate a CAUSE (see methods below).

6. Use ALL the other methods in the previously posted troubleshooters and those below.

========================================================

BCCode: 1E   0x0000001E Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLEDThe KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.Important Info If You Have Received a STOP Code

If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.

If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.

These actions might prevent an error like this from happening again:

1. Download and install updates and device drivers for your computer from Windows Update.
2. Scan your computer for computer viruses.
3. Check your hard disk for errors.

KMODE_EXCEPTION_NOT_HANDLED Parameters

The following parameters are displayed on the blue screen.

Parameter	Description
1	The exception code that was not handled
2	The address at which the exception occurred
3	Parameter 0 of the exception
4	Parameter 1 of the exception

Cause

This is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:

• 0x80000002: STATUS_DATATYPE_MISALIGNMENT An unaligned data reference was encountered.
• 0x80000003: STATUS_BREAKPOINT A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
• 0xC0000005: STATUS_ACCESS_VIOLATION A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)

For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows Driver Kit.

Resolution

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame will supply additional information.

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility. First, make sure that any new hardware installed is compatible with the installed version of Windows. For example, you can get information about compatibility with Windows 7 at the Windows 7 Compatibility Center.

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is a system BIOS incompatibility. BIOS problems can be resolved by upgrading the system BIOS version.

To get a stack trace if the normal stack tracing procedures fail

1. Use the **kb (Display Stack Backtrace)** command to display parameters in the stack trace. Look for the call to NT!PspUnhandledExceptionInSystemThread. (If this function is not listed, see the note below.)
2. The first parameter to NT!PspUnhandledExceptionInSystemThread is a pointer to a structure, which contains pointers to an except statement:

Copy

typedef struct _EXCEPTION_POINTERS { PEXCEPTION_RECORD ExceptionRecord; PCONTEXT ContextRecord; } EXCEPTION_POINTERS, *PEXCEPTION_POINTERS; ULONG PspUnhandledExceptionInSystemThread( IN PEXCEPTION_POINTERS ExceptionPointers )

Use the [**dd (Display Memory)**](http://msdn.microsoft.com/en-us/library/ff542790%28v=vs.85%29.aspx) command on that address to display the necessary data.

3. The first retrieved value is an exception record and the second is a context record. Use the **.exr (Display Exception Record)** command and the **.cxr (Display Context Record)** command with these two values as their arguments, respectively.
4. After the .cxr command executes, use the kb command to display a stack trace that is based on the context record information. This stack trace indicates the calling stack where the unhandled exception occurred.

Note  This procedure assumes that you can locate NT!PspUnhandledExceptionInSystemThread. However, in some cases (such as an access violation crash) you will not be able to do this. In that case, look for ntoskrnl!KiDispatchException. The third parameter passed to this function is a trap frame address. Use the **.trap (Display Trap Frame)** command with this address to set the Register Context to the proper value. You can then perform stack traces and issue other commands.

Here is an example of bug check 0x1E on an x86 processor:

Bug_Check 0x1E - read link for the examplehttp://msdn.microsoft.com/en-us/library/ff557408(v=vs.85).aspx

BCCode: 1E   0x0000001E  <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/Check-to-be-sure-you-have-adequate-disk-space-0x0000001E-\*1045.html

=============================================================

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users

http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7.

http://www.winvistaclub.com/t79.html 

Using Driver Verifier

http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx 

How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues

http://www.youtube.com/watch?v=\_VwIDD9xngM

Driver Verifier

http://www.techsupportforum.com/2110308-post3.html

Using Driver Verifier

http://www.faultwire.com/solutions/using\_driver\_verifier.php 

How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues

http://www.youtube.com/watch?v=\_VwIDD9xngM 

You can disable Driver Verifier

http://support.microsoft.com/kb/244617 

Start - type in Search box -> verifier /reset      hit enter to disable

Use BlueScreenView to see if there is a driver specified in the error message. Also check with

MyEventViewer at the time of the BlueScreen.

If DriverVerifier creates a minidump upload it and post the link here so we can analyze it.

Hope this helps.

---

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

Answer 4

https://skydrive.live.com/redir?resid=12F2C44A38A1C52F!106

I have uploaded the dump file.

Answer 5

Hi,

References to Vista also apply to Windows 7.

This is my generic how to for proper driver updates :

This utility makes it easy to see which versions are loaded :

DriverView - Free - utility displays the list of all device drivers currently loaded on your system.

For each driver in the list, additional useful information is displayed: load address of the driver,

description, version, product name, company that created the driver, and more.

http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the most current.

Control Panel - Device Manager - Display Adapter - write down the make and complete model

of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate

Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -

Uninstall - REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party

with their own software and drivers and any other major device drivers you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device

Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for

BIOS, Chipset and software updates at System Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after

each installation.

Always check in Device Manager - Drivers tab to be sure the version you are installing actually

shows up. This is because some drivers rollback before the latest is installed (sound drivers

particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as

needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check

manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

Installing and updating drivers in 7 (updating drivers manually using the methods above is

preferred to ensure the latest drivers from System maker and Device makers are found)

http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

If you update drivers manually then it is a good idea to disable Driver Installations in Windows

Updates, this leaves Windows Updates ON however it will not install drivers which will usually

be older and cause issues. If Updates suggests a new driver then HIDE it (Right Click on it)

and then go look for new ones manually if you wish.

Stop Windows 7 from Automatically Installing Device Drivers

http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/

How To Disable Automatic Driver Installation In Windows 7 / Vista

http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for Professional,

Ultimate, and Enterprise)

http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/

==========================================

Memory tests do not catch all errors such as mismatched memory (possible even for sticks

that appear to be identical) and when faster memory is placed in system behind slower memory.

So it is best to also swap sticks in and out to check for those even if all memory tests fail to

show a problem.

To test RAM check here - let it run 4+ hours or so.  <-- best methodwww.memtest.org

For the Windows Memory Diagnostic Tool.

Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click -

RUN AS ADMIN follow the instructions

Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory

Diagnostic Tool

http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

How to Run the Memory Diagnostics Tool in Windows 7

http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Hope this helps.

---

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!