BSOD Driver_IRQL_Not_less_or_equal; Bug Check Code : 0x000000d1

Anonymous
2014-08-05T02:18:24+00:00

Hello ive been recieving this error, i have reinstalled all the drivers repeatedly and the error still persists, i have gone to the minidumps folder and i have got them here 

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

Dump File         : 073014-22953-01.dmp

Crash Time        : 30-Jul-14 10:53:54 AM

Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bug Check Code    : 0x000000d1

Parameter 1       : 00000000`00000028

Parameter 2       : 00000000`00000002

Parameter 3       : 00000000`00000000

Parameter 4       : fffff801`028e2c47

Caused By Driver  : igdkmd64.sys

Caused By Address : igdkmd64.sys+62c47

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+153fa0

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\WINDOWS\Minidump\073014-22953-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 9600

Dump File Size    : 343,960

Dump File Time    : 30-Jul-14 10:56:15 AM

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

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

Dump File         : 073014-59531-01.dmp

Crash Time        : 30-Jul-14 9:42:35 AM

Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bug Check Code    : 0x000000d1

Parameter 1       : 00000000`00000028

Parameter 2       : 00000000`00000002

Parameter 3       : 00000000`00000000

Parameter 4       : fffff801`b5062c47

Caused By Driver  : igdkmd64.sys

Caused By Address : igdkmd64.sys+62c47

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+153fa0

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\WINDOWS\Minidump\073014-59531-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 9600

Dump File Size    : 343,960

Dump File Time    : 30-Jul-14 9:44:30 AM

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

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

Dump File         : 072714-26609-01.dmp

Crash Time        : 27-Jul-14 9:12:18 PM

Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bug Check Code    : 0x000000d1

Parameter 1       : 00000000`00000028

Parameter 2       : 00000000`00000002

Parameter 3       : 00000000`00000000

Parameter 4       : fffff801`c80fac47

Caused By Driver  : igdkmd64.sys

Caused By Address : igdkmd64.sys+62c47

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+153fa0

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\WINDOWS\Minidump\072714-26609-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 9600

Dump File Size    : 343,960

Dump File Time    : 27-Jul-14 9:13:59 PM

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

Please help thanks

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-08-05T04:07:49+00:00

Hi,

The Bug_Check were D1 CAUSE either igdkmd64.sys or athw8x.sys.

BugCheck D1, {28, 2, 0, fffff801b5062c47}

Probably caused by : igdkmd64.sys ( igdkmd64+62c47 )

BugCheck D1, {4, 2, 0, fffff800602740fa}

Probably caused by : athw8x.sys ( athw8x+18a0fa )

igdkmd64.sys dated 9/16/2013 Intel Graphics Accelerator Drivers for Windows 8(R)

athw8x.sys dated 8/15/2013 Atheros WiFi driver.

BiosVersion = K56CM.209

BiosReleaseDate = 11/19/2012

SystemManufacturer = ASUSTeK COMPUTER INC.

SystemProductName = K56CM

SystemFamily = K

SystemVersion = 1.0      

SystemSKU = ASUS-NotebookSKU

BaseBoardManufacturer = ASUSTeK COMPUTER INC.

BaseBoardProduct = K56CM

BaseBoardVersion = 1.0      

1. Check with ASUStek Support, their on-line documentation and drivers, and ask in their forums

about any known issues. Update the BIOS, low level chipset drivers, and the major on-board and

separate device drivers. After updating the chipset drivers check with Intel for even newer versions.

And same for the Atheros WiFi driver check both the Atheros sites for even newer versions. (See

driver update methods below.)

ASUS - Service <-- includes Live Chat

http://www.service.asus.com/

ASUStek Support

http://support.asus.com/

ASUStek Forums

http://vip.asus.com/forum/default.aspx?SLanguage=en-us

ASUStek Drivers

http://support.asus.com/download/download.aspx?SLanguage=en-usIntel Driver Update Utility <-- run this after checking with ASUStek

http://www.intel.com/p/en_US/support/detect?redirector_count=1&

Intel Download Center

http://downloadcenter.intel.com/

Intel - Support

http://www.intel.com/p/en_US/support

Intel - Community and Forums

http://www.intel.com/content/www/us/en/blogs-communities-social.html

Atheros - Drivers

http://www.atheros.cz/

Qualcomm-Atheros - Drivers

http://www.qca.qualcomm.com/resources/driverdownloads/


2. The Nvidia video drivers are probably also involved as the 5/19/2014 and 5/22/2014 versions

have been causing issues. Check with Nvidia support, their on-line documentation and drivers,

and ask in their forums about any known issues.

nvlddmkm.sys 5/19/2014

NvStreamKms.sys 5/22/2014

Nvidia - Drivers - Use OPTION 1 to manually enter your driver info to get most current drivers. 

http://www.nvidia.com/Download/index.aspx?lang=en-us

Nvidia Support - check with Support as it could be a known issue

http://www.nvidia.com/page/support.html

Nvidia Forums - also check for forums as it could be a known issue and/or others likely to have it

http://forums.nvidia.com/


3. As needed use ALL the methods in the troubleshooters below.


4. After ALL the above if needed run Driver Verifier to see if it can indicate a CAUSE (see

Driver Verifier methods below).

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

Note using Win Key + X and Win Key + W (to get to Control Panel, Run, and Settings

as needed). Win Key + D calls the desktop and the using Win Key toggles Desktop

and Start Screen.

Translate the Windows 7 methods and use them on Windows 8/8.1.

Resolving Blue Screen errors in Windows 8/8.1 ****http://windows.microsoft.com/en-ca/windows-8/resolve-windows-blue-screen-errors ****Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't

start Windows (applies to Windows 8/8.1). If you can't start Windows 8/8.1 try using

a Repair Disc (see methods to make one below) to access Safe Mode and other trouble-

shooting steps.

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

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

to troubleshoot BlueScreens - top 3 replies (+1 other) (applies to Windows 8/8.1)

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

 -------------------------------------------------------------------------

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.

(also Windows 7 and Windows 8)

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

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

BCCode: D1     0x000000D1Think Video drivers mainly though it can be others. See the driver section in my generic

bluescreen troubleshooting methods below. BIOS, low level chipset drivers and

antivirus/antispyway/security programs can also cause this. 


BCCode: D1     0x000000D1

Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUALThe DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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.

DRIVER_IRQL_NOT_LESS_OR_EQUAL Parameters

The following parameters are displayed on the blue screen.

Cause

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper addresses.

If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:

  • The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
  • The function call was made to a function in another driver, and that driver was unloaded.
  • The function was called by using a function pointer that was an invalid pointer.

Resolution

To begin debugging, use a kernel debugger to get a stack trace.

If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is not marked as pageable or does not call any other inline functions that could be paged out.

BCCode: d1   0x000000d1  <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/DRIVER-IRQL-NOT-LESS-OR-EQUAL-0x000000D1-\*1210.html?order=votes


This is my generic how to for proper driver updates : (update video/display driver and BIOS)

This utility makes it easy to see which versions are loaded : Run DriverView - set VIEW to Hide

Microsoft drivers - update those without Dump in their names. (Also update the BIOS and

low level chipset drivers.)

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

Windows 8/8.1 - Hardware and Drivers

http://windows.microsoft.com/en-US/windows/hardware-drivers-help#hardware-drivers-help=windows-8

Windows 8/8.1 - Why isn't Windows finding my device?

http://windows.microsoft.com/en-US/windows-8/why-isnt-windows-finding-device

Windows 8/8.1 - What if a device isn't installed properly

http://windows.microsoft.com/en-US/windows-8/what-device-isnt-installed-properly


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.

WinKEY + W  - type in the Search box ->  Memory - find Memory Diagnostics tool at top

of list - follow the prompts.

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 (and 8/8.1) - in Windows 8 /8.1the name is "Windows Memory Diagnostic".http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

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

After doing ALL the updates you can, and if the issue continues, then run DriverVerifier.

(Remember to use the Windows 8 methods posted at the top of the original reply above.)

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

WINKEY + X - RUN - type in -> 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!

Was this answer helpful?

0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-08-05T05:00:32+00:00

    Hi,

    The most important parts are 1. through 4. which is updating the BIOS, chipset, and the major

    drivers. First those that are available at ASUStek. ASUStek Support and their forums can help

    with that effort. Also how to update drivers is included in my reply above.

    Possibly you need to the help of a friend or family member.

    Rob - SpiritX

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-08-05T04:54:51+00:00

    Hi,

    The Bug_Check were D1 CAUSE either igdkmd64.sys or athw8x.sys.

    BugCheck D1, {28, 2, 0, fffff801b5062c47}

    Probably caused by : igdkmd64.sys ( igdkmd64+62c47 )

    BugCheck D1, {4, 2, 0, fffff800602740fa}

    Probably caused by : athw8x.sys ( athw8x+18a0fa )

    igdkmd64.sys dated 9/16/2013 ntel Graphics Accelerator Drivers for Windows 8(R)

    athw8x.sys dated 8/15/2013 Atheros WiFi driver.

    BiosVersion = K56CM.209

    BiosReleaseDate = 11/19/2012

    SystemManufacturer = ASUSTeK COMPUTER INC.

    SystemProductName = K56CM

    SystemFamily = K

    SystemVersion = 1.0      

    SystemSKU = ASUS-NotebookSKU

    BaseBoardManufacturer = ASUSTeK COMPUTER INC.

    BaseBoardProduct = K56CM

    BaseBoardVersion = 1.0      

    1. Check with ASUStek Support, their on-line documentation and drivers, and ask in their forums

    about any known issues. Update the BIOS, low level chipset drivers, and the major on-board and

    separate device drivers. After updating the chipset drivers check with Intel for even newer versions.

    And same for the Atheros WiFi driver check both the Atheros sites for even newer versions. (See

    driver update methods below.)

    ASUS - Service <-- includes Live Chat

    http://www.service.asus.com/

    ASUStek Support

    http://support.asus.com/

    ASUStek Forums

    http://vip.asus.com/forum/default.aspx?SLanguage=en-us

    ASUStek Drivers

    http://support.asus.com/download/download.aspx?SLanguage=en-usIntel Driver Update Utility <-- run this after checking with ASUStek

    http://www.intel.com/p/en_US/support/detect?redirector_count=1&

    Intel Download Center

    http://downloadcenter.intel.com/

    Intel - Support

    http://www.intel.com/p/en_US/support

    Intel - Community and Forums

    http://www.intel.com/content/www/us/en/blogs-communities-social.html

    Atheros - Drivers

    http://www.atheros.cz/

    Qualcomm-Atheros - Drivers

    http://www.qca.qualcomm.com/resources/driverdownloads/


    2. The Nvidia video drivers are probably also involved as the 5/19/2014 and 5/22/2014 versions

    have been causing issues. Check with Nvidia support, their on-line documentation and drivers,

    and ask in their forums about any known issues.

    nvlddmkm.sys 5/19/2014

    NvStreamKms.sys 5/22/2014

    Nvidia - Drivers - Use OPTION 1 to manually enter your driver info to get most current drivers. 

    http://www.nvidia.com/Download/index.aspx?lang=en-us

    Nvidia Support - check with Support as it could be a known issue

    http://www.nvidia.com/page/support.html

    Nvidia Forums - also check for forums as it could be a known issue and/or others likely to have it

    http://forums.nvidia.com/


    3. As needed use ALL the methods in the troubleshooters below.


    4. After ALL the above if needed run Driver Verifier to see if it can indicate a CAUSE (see

    Driver Verifier methods below).

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

    Note using Win Key + X and Win Key + W (to get to Control Panel, Run, and Settings

    as needed). Win Key + D calls the desktop and the using Win Key toggles Desktop

    and Start Screen.

    Translate the Windows 7 methods and use them on Windows 8/8.1.

    Resolving Blue Screen errors in Windows 8/8.1 ****http://windows.microsoft.com/en-ca/windows-8/resolve-windows-blue-screen-errors ****Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't

    start Windows (applies to Windows 8/8.1). If you can't start Windows 8/8.1 try using

    a Repair Disc (see methods to make one below) to access Safe Mode and other trouble-

    shooting steps.

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

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

    to troubleshoot BlueScreens - top 3 replies (+1 other) (applies to Windows 8/8.1)

    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

     -------------------------------------------------------------------------

    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.

    (also Windows 7 and Windows 8)

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

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

    BCCode: D1     0x000000D1Think Video drivers mainly though it can be others. See the driver section in my generic

    bluescreen troubleshooting methods below. BIOS, low level chipset drivers and

    antivirus/antispyway/security programs can also cause this. 


    BCCode: D1     0x000000D1

    Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUALThe DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

    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.

    DRIVER_IRQL_NOT_LESS_OR_EQUAL Parameters

    The following parameters are displayed on the blue screen.

    Cause

    A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

    This bug check is usually caused by drivers that have used improper addresses.

    If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:

    • The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
    • The function call was made to a function in another driver, and that driver was unloaded.
    • The function was called by using a function pointer that was an invalid pointer.

    Resolution

    To begin debugging, use a kernel debugger to get a stack trace.

    If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is not marked as pageable or does not call any other inline functions that could be paged out.

    BCCode: d1   0x000000d1  <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/DRIVER-IRQL-NOT-LESS-OR-EQUAL-0x000000D1-\*1210.html?order=votes


    This is my generic how to for proper driver updates : (update video/display driver and BIOS)

    This utility makes it easy to see which versions are loaded : Run DriverView - set VIEW to Hide

    Microsoft drivers - update those without Dump in their names. (Also update the BIOS and

    low level chipset drivers.)

    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

    Windows 8/8.1 - Hardware and Drivers

    http://windows.microsoft.com/en-US/windows/hardware-drivers-help#hardware-drivers-help=windows-8

    Windows 8/8.1 - Why isn't Windows finding my device?

    http://windows.microsoft.com/en-US/windows-8/why-isnt-windows-finding-device

    Windows 8/8.1 - What if a device isn't installed properly

    http://windows.microsoft.com/en-US/windows-8/what-device-isnt-installed-properly


    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.

    WinKEY + W  - type in the Search box ->  Memory - find Memory Diagnostics tool at top

    of list - follow the prompts.

    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 (and 8/8.1) - in Windows 8 /8.1the name is "Windows Memory Diagnostic".http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

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

    After doing ALL the updates you can, and if the issue continues, then run DriverVerifier.

    (Remember to use the Windows 8 methods posted at the top of the original reply above.)

    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

    WINKEY + X - RUN - type in -> 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! 

    I uh, dont understand sorry, can you write it a little easier to understand, sorry im not that well in this area >_<, thanks

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-08-05T02:59:42+00:00

    Ok then, here is the link http://1drv.ms/XzaY2s

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-08-05T02:26:02+00:00

    ****We do need the actual log file (called a DMP file) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    We prefer at least 2 DMP files to spot trends and confirm the cause.


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here

    If you have any questions about the procedure please ask

    If you are using Blue screen view, who crashed, or a similar application, don't.  They are wrong at least as often as they are correct

    Was this answer helpful?

    0 comments No comments