Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD random, intermittent - Driver IRQL not less or equal

28 Feb 2013   #1

Windows 7 Home Premium x64 oem
 
 
BSOD random, intermittent - Driver IRQL not less or equal

The title says it all. Rig also freezes at random intervals with no BSOD.

Thanks in advance y'all.


My System SpecsSystem Spec
.

28 Feb 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome to SevenForums.
Code:
Start Menu\Programs\Ad-Aware Antivirus	Public:Start Menu\Programs\Ad-Aware Antivirus	Public
Start Menu\Programs\Spybot - Search & Destroy	Public:Start Menu\Programs\Spybot - Search & Destroy	Public
Not the best security software to have. I have seen both of these cause problems for users. Please remove and replace with Microsoft Security Essentials and Malwarebytes.

Remove Adaware and Spybot with the free version of Revo uninstaller in Advance mode and delete left over registry entries of both the program.Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
warning   Warning
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Note   Note
Let me know if you are unable to download MSE from the link above

Perform a System File Check to check the integrity of all protected Windows 7 :
  1. Click on the start
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type
    Code:
    SFC /scannow
Full tutorial here:Disk Check on your hard drive for file system errors and bad sectors on it.Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.Check for a BIOS update:
Code:
BIOS Version/Date	American Megatrends Inc. V11.0, 12/25/2009
Quote:
Your BIOS dates from 2009. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, fffff8800449d736}

Probably caused by : usbehci.sys ( usbehci!EHCI_iAsyncCacheFlush+102 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800449d736, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c8100
GetUlongFromAddress: unable to read from fffff800030c81c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
usbehci!EHCI_iAsyncCacheFlush+102
fffff880`0449d736 488930          mov     qword ptr [rax],rsi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80004462FB0

TRAP_FRAME:  fffff80004462270 -- (.trap 0xfffff80004462270)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800e433780
rdx=0000000010000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800449d736 rsp=fffff80004462400 rbp=0000000000000000
 r8=000000004f444648  r9=fffffa800f8df258 r10=fffff88004295080
r11=fffff88004291820 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
usbehci!EHCI_iAsyncCacheFlush+0x102:
fffff880`0449d736 488930          mov     qword ptr [rax],rsi ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8f1e9 to fffff80002e8fc40

STACK_TEXT:  
fffff800`04462128 fffff800`02e8f1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`04462130 fffff800`02e8de60 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`04351080 : nt!KiBugCheckDispatch+0x69
fffff800`04462270 fffff880`0449d736 : fffff880`04351080 fffffa80`0f8df258 fffffa80`0f8df258 fffff800`04462420 : nt!KiPageFault+0x260
fffff800`04462400 fffff880`0449c874 : 00000000`00000002 fffffa80`0f8df258 fffffa80`0e4336a0 fffff800`04462450 : usbehci!EHCI_iAsyncCacheFlush+0x102
fffff800`04462440 fffff880`0449cc25 : fffffa80`0f8df258 00000000`00000002 00000000`00000000 00000000`00000017 : usbehci!EHCI_RemoveQueueHeadFromAsyncList+0x8c
fffff800`04462480 fffff880`044a2f70 : fffffa80`0f8df258 00000000`00000002 fffffa80`0e4336a0 00000000`00000002 : usbehci!EHCI_SetAsyncEndpointState+0xa5
fffff800`044624c0 fffff880`04443a87 : fffffa80`0f8df002 fffffa80`0e4321a0 00000000`00000004 fffffa80`0f8df010 : usbehci!EHCI_SetEndpointState+0x58
fffff800`04462500 fffff880`04449321 : fffffa80`0f8df010 fffffa80`0e4321a0 fffffa80`0e432050 00000000`00000004 : USBPORT!MPf_SetEndpointState+0x6b
fffff800`04462530 fffff880`04448422 : 00000000`00000050 00000000`00000004 fffffa80`0f8df010 ffffffff`c0010000 : USBPORT!USBPORT_SetEp_PAUSE+0xcd
fffff800`04462570 fffff880`04457064 : fffffa80`0e4321a0 00000000`00000050 fffffa80`00000008 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x212
fffff800`044625d0 fffff880`0445235e : fffffa80`0daf6c00 fffffa80`0f9b6e10 fffffa80`0e433078 fffffa80`0e4321a0 : USBPORT!USBPORT_Core_iCancelPriorityTransfer+0x19c
fffff800`04462610 fffff800`02f3fb07 : fffffa80`0e432402 fffffa80`0f9b6e10 fffffa80`0e432480 00000000`0000fffe : USBPORT!USBPORT_TxCsqCompleteCanceledIrp+0x212
fffff800`04462670 fffff800`02e3d6a0 : fffffa80`0f9b6e10 fffffa80`0f9b6e02 00000000`00000002 00000000`00000000 : nt!IopCsqCancelRoutine+0x77
fffff800`044626a0 fffff880`00ea923b : 00000000`00026302 fffffa80`0f9b6020 00000000`00000002 fffff800`04462e88 : nt!IoCancelIrp+0x60
fffff800`044626e0 fffff880`00eadddc : fffffa80`0f9b6020 fffffa80`0e081c40 fffffa80`0e081c40 fffffa80`0f9b6020 : Wdf01000!FxRequestBase::Cancel+0x7b
fffff800`04462730 fffff800`02e9a94c : fffff800`04462802 fffff800`00000000 fffff800`04462848 00000000`0000fffe : Wdf01000!FxIoTarget::TimerCallback+0x12c
fffff800`044627a0 fffff800`02e9a7e6 : fffffa80`0fbfb570 00000000`00017d1c 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04462810 fffff800`02e9a6ce : 00000003`8b309661 fffff800`04462e88 00000000`00017d1c fffff800`0300e608 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04462e60 fffff800`02e9a4b7 : fffff800`0300bec3 fffffa80`00017d1c fffffa80`0e432d40 00000000`0000001c : nt!KiTimerExpiration+0x1be
fffff800`04462f00 fffff800`02e92e15 : 00000000`00000000 fffffa80`0d906040 00000000`00000000 fffff880`04444db0 : nt!KiRetireDpcList+0x277
fffff800`04462fb0 fffff800`02e92c2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`09004900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_iAsyncCacheFlush+102
fffff880`0449d736 488930          mov     qword ptr [rax],rsi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbehci!EHCI_iAsyncCacheFlush+102

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c00

FAILURE_BUCKET_ID:  X64_0xD1_usbehci!EHCI_iAsyncCacheFlush+102

BUCKET_ID:  X64_0xD1_usbehci!EHCI_iAsyncCacheFlush+102

Followup: MachineOwner
---------

0: kd> lmvm usbehci
start             end                 module name
fffff880`04498000 fffff880`044a9000   usbehci    (pdb symbols)          c:\symbols\usbehci.pdb\C17DE2202F204C9A842E60915B27E0CB1\usbehci.pdb
    Loaded symbol image file: usbehci.sys
    Mapped memory image file: c:\symbols\usbehci.sys\4D8C0C0011000\usbehci.sys
    Image path: \SystemRoot\system32\DRIVERS\usbehci.sys
    Image name: usbehci.sys
    Timestamp:        Fri Mar 25 09:29:04 2011 (4D8C0C00)
    CheckSum:         0000DE59
    ImageSize:        00011000
    File version:     6.1.7601.17586
    Product version:  6.1.7601.17586
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     USBEHCI.sys
    OriginalFilename: USBEHCI.sys
    ProductVersion:   6.1.7601.17586
    FileVersion:      6.1.7601.17586 (win7sp1_gdr.110324-1501)
    FileDescription:  EHCI eUSB Miniport Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
Please go through this tutorial: USB Driver - General Fix for Problems and let us know if the steps were helpful. You might also want to disconnect anything connected to the USB ports.

Let us know the results.
My System SpecsSystem Spec
01 Mar 2013   #3

Windows 7 Home Premium x64 oem
 
 
No BSOD, intermittent freezing

Thank you thank you thank you for your help.
I followed all instructions, except for flashing my bios, and didn't have a BSOD all night. Thanks.
Unfortunately my rig froze twice towards the end of the night.
I have attached another log in the hopes that more might be done.
Thanks in advance.
My System SpecsSystem Spec
.


01 Mar 2013   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

I will take a look at them soon.

Please do the following:


Upload a screenshot of your hard disk using CrystalDiskInfo and Summary tab using Speccy:Make a hard drive test from the hard drive manufacturers website:
My System SpecsSystem Spec
01 Mar 2013   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

For the stop 124, please go through this thread:
Quote:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try:Stop 124 Troubleshooting Strategy
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800e1bc038, 0, 0}
Probably caused by : AuthenticAMD
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800e1bc038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
 
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`031b66f0 fffff800`0311dca9 : fffffa80`0e1bc010 fffffa80`0caa2b50 00000000`00000005 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6c10 fffff800`02ffe077 : fffffa80`0e1bc010 fffff800`030782d8 fffffa80`0caa2b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6c40 fffff800`02f65435 : fffff800`030d9ae0 00000000`00000001 fffffa80`0e190610 fffffa80`0caa2b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6c80 fffff800`02edaca9 : fffff880`01188e00 fffff800`02f65410 fffffa80`0caa2b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6cb0 fffff800`0317234a : 33717eff`b36d8c4c fffffa80`0caa2b50 00000000`00000080 fffffa80`0ca90890 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02ec2946 : fffff880`02f64180 fffffa80`0caa2b50 fffff880`02f6efc0 4b2326be`2850053a : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`02e3b740 00000000`00000000 : nt!KiStartSystemThread+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME:  AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
1: kd> !errrec fffffa800e1bc038
===============================================================================
Common Platform Error Record @ fffffa800e1bc038
-------------------------------------------------------------------------------
Record Id     : 01ce162816283603
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/1/2013 2:54:32 (UTC)
Flags         : 0x00000002 PreviousError
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e1bc0b8
Section       @ fffffa800e1bc190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100f52
Processor ID  : 0x0000000000000000
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e1bc100
Section       @ fffffa800e1bc250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000000
CPU Id        : 52 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0  @ fffffa800e1bc250
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e1bc148
Section       @ fffffa800e1bc2d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f
My System SpecsSystem Spec
01 Mar 2013   #6
Microsoft MVP

Windows 7 Ultimate X64 SP1
 
 

Also uninstall and don't use Spybot - Search & Destroy IT does not work well with Windows 7.
Do a full Memtst86+ test. IT may take over 8 hours for 7 passes with 16GB.

RAM (memory):
This will require memtest on a bootable CD or USB stick.
RAM - Test with Memtest86+
My System SpecsSystem Spec
01 Mar 2013   #7

Windows 7 Home Premium x64 oem
 
 

Ran Speccy and crystaldisc.
Downloaded and tried to run Seagate's diagnostic tool. Get the following error
"Fatal Error: Device Discovery"
Argument 'Length' must be greater or equal to zero. System.String
Mid(System.String, Int, Int)
Will run memtest after posting.

Thanks!
My System SpecsSystem Spec
01 Mar 2013   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

They look fine
Let us know the results from memtest and what you have followed from the 124 troubleshooting link
My System SpecsSystem Spec
01 Mar 2013   #9

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

Hi DivinePaige

Here is a screenshot of your latest BIOS VERSION



If you don't have it here is the download for it

download

Choose your country when asked
My System SpecsSystem Spec
01 Mar 2013   #10

Windows 7 Home Premium x64 oem
 
 

Memtest froze after 5 hours. Found 1 error on test 8 pass 1.
124 troubleshooting:
No overclocked hardware.
External fan blowing in case.
All drivers up to date.
BIOS update - When i boot from usb i get the prompt
"No DEFAULT UI or config directive found" below Syslinux 3.86 EBIOS. Not sure how to proceed.

Thanks
My System SpecsSystem Spec
Reply

 BSOD random, intermittent - Driver IRQL not less or equal




Thread Tools



Similar help and support threads for2: BSOD random, intermittent - Driver IRQL not less or equal
Thread Forum
Solved BSOD at random times: DRIVER IRQL NOT LESS OR EQUAL BSOD Help and Support
BSOD Random Intervals; DRIVER IRQL NOT LESS OR EQUAL BSOD Help and Support
BSOD at random times: Driver IRQL Not Less Or Equal BSOD Help and Support
Intermittent BSOD, IRQL less or not equal BSOD Help and Support
Solved Random BSOD playing youtube videos, Driver IRQL Not less or equal BSOD Help and Support
Intermittent BSOD's PFN and Driver IRQL BSOD Help and Support
Random BSOD's can u help? [IRQL Not Less or Equal] BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 04:08 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33