BSOD again bad pool header, memory management

i got BSOD again 3 times in a day

nothing can do, is it best choice to swap memory and HDD with a new one??

i think BSOD comes with memory or HDD hardware problem

here my latest BSOD

 http://1drv.ms/1s2uuRD

please help to resolve my pc bsod

 

Question Info


Last updated April 26, 2018 Views 4,858 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

my computer windows 8.1 pro get BSOD by random activities when i do browsing etc.

latest BSOD caused by IRQL_NOT_LESS_OR_EQUAL

please help me to fix this problem

link to my dump file 

https://onedrive.live.com/redir?resid=8A920711B1A91146!452&authkey=!ABY5_UFWJU0MFEc&ithint=file%2c.zip

here newest dump file

==================================================
Dump File         : 052714-16812-01.dmp
Crash Time        : 27/05/2014 20:10:43
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff801`fe7c823e
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153fa0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.3.9600.17085 (winblue_gdr.140330-1035)
Processor         : x64
Crash Address     : ntoskrnl.exe+153fa0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\052714-16812-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 149.095
Dump File Time    : 27/05/2014 20:14:49
==================================================

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

MEMORY_MANAGEMENT (1a)

This indicates that a severe memory management error occurred.

BugCheck 1A, {5200, ffffe0017c825000, 4000008300000, 15edd030f19f4802}

1: kd> k
Child-SP          RetAddr           Call Site
ffffd000`470a6df8 fffff802`a89ad2f3 nt!KeBugCheckEx
ffffd000`470a6e00 fffff802`a88d2382 nt! ?? ::FNODOBFM::`string'+0x30e43
ffffd000`470a6e50 fffff802`a8aacf33 nt!ExpAllocateBigPool+0xd2
ffffd000`470a6f50 fffff802`a8901b32 nt!ExAllocatePoolWithTag+0xa73
ffffd000`470a7020 fffff802`a888e8f0 nt!MiAllocateAccessLog+0x7e
ffffd000`470a7050 fffff802`a888b97f nt!MiLogPageAccess+0x170
ffffd000`470a70c0 fffff802`a88886d4 nt!MiDeleteVirtualAddresses+0x9cf
ffffd000`470a7350 fffff802`a8bdfcd9 nt!MiDeleteVad+0x244
ffffd000`470a7450 fffff802`a8c5df10 nt!MiUnmapViewOfSection+0xf9
ffffd000`470a7520 fffff802`a8c2d810 nt!AlpcViewDestroyProcedure+0x1f8
ffffd000`470a75c0 fffff802`a8c5d38a nt!AlpcpDestroyBlob+0x28
ffffd000`470a75f0 fffff802`a8cc3f84 nt!AlpcpCaptureViewAttributeInternal+0x15e
ffffd000`470a7660 fffff802`a8c2e4a8 nt!AlpcpCaptureViewAttribute32+0x30
ffffd000`470a76b0 fffff802`a8c2ece7 nt!AlpcpCaptureAttributes+0x4b4
ffffd000`470a7720 fffff802`a8c33539 nt!AlpcpSendMessage+0x787
ffffd000`470a7840 fffff800`bd9116c8 nt!NtAlpcSendWaitReceivePort+0x169
ffffd000`470a7910 00000000`00000000 aswSnx+0x306c8

aswSnx.sys is the avast! Virtualization driver. It looks as if avast! (to no surprise) is causing memory corruption.

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

1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

and rename AODDriver2.sys to AODDriver.2old

and then Restart.

2. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:

avast! removal - http://www.avast.com/uninstall-utility

Windows Defender (how to turn on after removal) - http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

3. Uninstall all AsRock utilities ASAP - App Charger, RamDIsk, etc.

4. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Regards,

Patrick

Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

please my computer always get BSOD when copy large file with usb HDD ext to my computer

here dump files

https://onedrive.live.com/redir?resid=8A920711B1A91146!453&authkey=!AGxDFHG8UCyJzyA&ithint=file%2c.zip

and here latest BSOD with BSOD viewer

please help

==================================================
Dump File         : 053014-16109-01.dmp
Crash Time        : 30/05/2014 17:00:41
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`000000b8
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`002c670a
Caused By Driver  : Wdf01000.sys
Caused By Address : Wdf01000.sys+170a
File Description  : Kernel Mode Driver Framework Runtime
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 1.13.9600.16384 (winblue_rtm.130821-1623)
Processor         : x64
Crash Address     : ntoskrnl.exe+14dca0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\053014-16109-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 279.968
Dump File Time    : 30/05/2014 17:01:29
==================================================

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,


All of the attached DMP files are of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bug check.

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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.

5: kd> k
Child-SP          RetAddr           Call Site
ffffd000`207eb278 fffff800`26d637e9 nt!KeBugCheckEx
ffffd000`207eb280 fffff800`26d6203a nt!KiBugCheckDispatch+0x69
ffffd000`207eb3c0 fffff800`002c670a nt!KiPageFault+0x23a
ffffd000`207eb550 fffff800`002d3364 Wdf01000!FxRequest::CompleteInternal+0x4a
ffffd000`207eb610 fffff800`029a5e32 Wdf01000!imp_WdfRequestComplete+0x8c
ffffd000`207eb680 fffff800`029a65a0 USBXHCI!Bulk_Transfer_CompleteCancelable+0x15a
ffffd000`207eb6e0 fffff800`029a6c29 USBXHCI!Bulk_ProcessTransferEventWithHaltedCompletion+0x124
ffffd000`207eb740 fffff800`0299402b USBXHCI!Bulk_ProcessTransferEventWithED1+0x229
ffffd000`207eb7f0 fffff800`0035ec81 USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427
ffffd000`207eb8f0 fffff800`26c64d10 Wdf01000!FxInterrupt::DpcHandler+0xc1
ffffd000`207eb920 fffff800`26c649f0 nt!KiExecuteAllDpcs+0x1b0
ffffd000`207eba70 fffff800`26d5b7ea nt!KiRetireDpcList+0xd0
ffffd000`207ebbe0 00000000`00000000 nt!KiIdleLoop+0x5a

Something is causing USB trans conflicts, likely 3rd party driver.

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

1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

and rename AODDriver2.sys to AODDriver.2old

and then Restart.

2. wdcsam64.sys is listed and loaded which is the Western Digital SES (SCSI Enclosure Services) driver. Please remove this software ASAP as it's troublesome and is also not necessary to the functionality of your system.

3. If you are still crashing after the above, please enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8/8.1)
- DDI compliance checking (Windows 8/8.1)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・    Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel-Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

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

Regards,

Patrick

Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

here my computer BSOD after verifier and one before that. please help to identify this BSOD wish BSOD not come in again

here dump file from following link

https://onedrive.live.com/redir?resid=8A920711B1A91146!454&authkey=!ACmXRucyl0Tl5pI&ithint=file%2c.zip

hope to solved this

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

every motherboard driver has not installed now , and feature from my motherboard is junk? how can i OC. cpu because i need to OC. to improve performance

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

One of the minidumps was unreadable.

BugCheck D6, {ffffcf80065b3018, 0, fffff80002c03f35, 0}

Probably caused by : portcls.sys ( portcls!GetMaxMapRegisters+5 ) <-- this is a Windows component
which means something drove it into Fault. From the Stack the probably cause was


vaclcskd.sys dated 12/5/2009 driver file from company Eugene V. Muzychenko belonging to product Breakaway Pipeline. The file is  digitally signed from Claesson Edwards Audio LLC.

fffff800`02ddd000 fffff800`02deb780   vaclcskd T (no symbols)          
    Loaded symbol image file: vaclcskd.sys
    Image path: \SystemRoot\system32\DRIVERS\vaclcskd.sys
    Image name: vaclcskd.sys
    Timestamp:        Sat Dec 05 05:15:31 2009 (4B1A5CF3)

Check with its support and you may need to uninstall it.

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


BugCheck 3B, {c0000005, fffff960002325fc, ffffd00027cfaeb0, 0}

Probably caused by : hardware ( win32k!SfnDWORD+17c )

No other real help in the minidump.

If you resolve one of those you probably resolve both.

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

In "some" cases this KB article will help.

Windows hangs or freezes
http://support.microsoft.com/kb/2681286

Be sure to check with the System Maker's Support (Motherboard Maker for custom
systems), their on-line documentation and drivers, and ask in their forums (if any)
about any known issues. Be sure to update the BIOS, low level chipset drivers,
and the other major on-board and separate device drivers
. Those alone may
resolve some or all of these issues.

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/8.1)
http://www.winvistatips.com/disable-automatic-restart-t84.html

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

BCCode: 3b    0x0000003b

Try removing and reseating all cards, memory, and cables (both ends when possible) - actually
remove and replace - do not just snug (on a PC) and clean out the dust bunnies and vents. On
a laptop about all that can be done is reseat the memory and clean the vents. (Of course
remove ALL power prior to opening the case.)

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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.

SYSTEM_SERVICE_EXCEPTION Parameters

The following parameters are displayed on the blue screen.

Parameter Description

1

The exception that caused the bug check

2

The address of the exception record for the exception that caused the bug check

3

The address of the context record for the exception that caused the bug check

4

0


Cause

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.


BCCode: 3b    0x0000003b  <-- read this link
http://www.faultwire.com/solutions-fatal_error/SYSTEM-SERVICE-EXCEPTION-0x0000003B-*1074.html


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

Windows 8/8.1 - Improve performance by optimizing your hard drive - see "To repair a drive:
http://windows.microsoft.com/en-US/windows-8/improve-performance-optimizing-hard-drive

How to Check a Drive for Errors with "chkdsk" in Windows 8/8.1
http://www.eightforums.com/tutorials/6221-chkdsk-check-drive-errors-windows-8-a.html

Redesigning chkdsk and the new NTFS health model
http://blogs.msdn.com/b/b8/archive/2012/05/09/redesigning-chkdsk-and-the-new-ntfs-health-model.aspx

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

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 (and BIOS and chipset).

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 method
www.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) - in Windows 8 the
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!











Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

my computer get BSOD when copy data using USB 3.0 from External HDD (WD)

please help why this is happen to my computer/HDD

this minidump file download from my skydrive http://1drv.ms/1nr56PE

thanks for helping me :)

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,


The attached DMP file is of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bug check.

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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.


1: kd> k
Child-SP          RetAddr           Call Site
ffffd000`69d5b138 fffff800`6f16cae9 nt!KeBugCheckEx
ffffd000`69d5b140 fffff800`6f16b33a nt!KiBugCheckDispatch+0x69
ffffd000`69d5b280 fffff801`2e44870a nt!KiPageFault+0x23a
ffffd000`69d5b410 fffff801`2e455364 Wdf01000!FxRequest::CompleteInternal+0x4a
ffffd000`69d5b4d0 fffff801`30b71f16 Wdf01000!imp_WdfRequestComplete+0x8c
ffffd000`69d5b540 fffff801`30b72684 USBXHCI!Bulk_Transfer_CompleteCancelable+0x15a
ffffd000`69d5b5a0 fffff801`30b72d0d USBXHCI!Bulk_ProcessTransferEventWithHaltedCompletion+0x124
ffffd000`69d5b600 fffff801`30b6002b USBXHCI!Bulk_ProcessTransferEventWithED1+0x229
ffffd000`69d5b6b0 fffff801`2e4e0c81 USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427
ffffd000`69d5b7b0 fffff800`6f0671e0 Wdf01000!FxInterrupt::DpcHandler+0xc1
ffffd000`69d5b7e0 fffff800`6f0663fb nt!KiExecuteAllDpcs+0x1b0
ffffd000`69d5b930 fffff800`6f164aea nt!KiRetireDpcList+0xdb
ffffd000`69d5bbe0 00000000`00000000 nt!KiIdleLoop+0x5a


Looks like we have a USB driver conflict during transfer.


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


1.

AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys and rename AODDriver2.sys to AODDriver.2old and then Restart.

2.

wdcsam64.sys is listed and loaded which is the Western Digital SES (SCSI Enclosure Services) driver. Please remove this software ASAP as it's very troublesome and is also not necessary to the functionality of your system.



3. If you are crashing after the above, please enable Driver Verifier:




Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8/8.1)
- DDI compliance checking (Windows 8/8.1)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・    Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel-Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

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

Regards,

Patrick

Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

i have installing game from mounting drive powerISO at half load my computer get crash BSOD

here minidump file http://1drv.ms/1nrDjhZ

please help, thanks alot for the helpful

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.