DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Help

[crafty]

Hi, my computer has blue screened a couple of times and it seems to be at ramdon, i am having trouble trying to figure out what it is,


*******************************************************************************
* *
* 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: fffffac043a3ec50, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800417d8e2, address which referenced memory

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


WRITE_ADDRESS: fffffac043a3ec50 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
afd!AfdTimeoutPoll+22
fffff880`0417d8e2 c7413002010000 mov dword ptr [rcx+30h],102h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0

TRAP_FRAME: fffff80000b9c270 -- (.trap 0xfffff80000b9c270)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffac043a3ec20
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800417d8e2 rsp=fffff80000b9c400 rbp=0000000000000000
r8=000000006308c20b r9=0000000001cd9743 r10=fffff80003265000
r11=fffff80000b9c470 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
afd!AfdTimeoutPoll+0x22:
fffff880`0417d8e2 c7413002010000 mov dword ptr [rcx+30h],102h ds:fffffac0`43a3ec50=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032e3769 to fffff800032e41c0

STACK_TEXT:
fffff800`00b9c128 fffff800`032e3769 : 00000000`0000000a fffffac0`43a3ec50 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c130 fffff800`032e23e0 : 00000000`00000000 fffff800`03456e80 fffff800`032ee085 fffff800`00b9c4c0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c270 fffff880`0417d8e2 : fffff800`03456e80 00000000`00000007 fffff880`0336d180 fffff800`032e981a : nt!KiPageFault+0x260
fffff800`00b9c400 fffff800`032eee3c : 00000000`00000000 00000000`000000ff 00000005`27d65000 00000000`00000043 : afd!AfdTimeoutPoll+0x22
fffff800`00b9c430 fffff800`032eecd6 : fffffa80`3a3a0168 fffffa80`3a3a0168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`032eebbe : 000000a3`2d0e8dd6 fffff800`00b9cb18 00000000`00448cdb fffff800`0345ade8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`032ee9a7 : 00000039`8fd218c2 00000039`00448cdb 00000039`8fd218ef 00000000`000000db : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`032dbeca : fffff800`03456e80 fffff800`03464cc0 00000000`00000000 fffff880`1138a038 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
afd!AfdTimeoutPoll+22
fffff880`0417d8e2 c7413002010000 mov dword ptr [rcx+30h],102h

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: afd!AfdTimeoutPoll+22

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4efa9418

FAILURE_BUCKET_ID: X64_0xD1_afd!AfdTimeoutPoll+22

BUCKET_ID: X64_0xD1_afd!AfdTimeoutPoll+22

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

Original Dump File Attached.

Can anyone help please.

 

[majorchaos]

Same thing just started to happen with me. Aftr 3 hours i havent fixed or read anything that has been usefull.

 

[Shintaro]

Mate, what USB devices do you have plugged in?

 

[crafty]

I have my 1TB seagate portable HDD plugged into a USB 3.0 port,
Then In the standard 2.0 ports I have,
1x turtle beach x11.
1x belkin wireless G+ network dock.
1x USB 2.0 1meter extension.
1x Etron Tech USB 2.0 HD webcam.
1x Apple Iphone charger cable.
1x Logitech wireless mouse and keyboard receiver.

That's everything I have plugged in. but I'm starting to now think it may be the turtle beaches because the problem has been happening since I very first built the system and from what I can remember I have always had my headset plugged in from when I first turned the tower on.

regards.

 

[Shintaro]

Well, unplug everything except one. Then add them back to see if you can find the one causing trouble.

 

[crafty]

I would try this except it happens at random or at least I cannot replicate the problem it just happens out of nowhere. For example, I had a bunch of stuff open and I got BSOD. Restarted the system, opened the exact same stuff no BSOD system ran fine, Another instance, had just skype running - BSOD, Restarted system - opened skype again, Nothing - system ran fine. So for me to take all out except 1 just wouldn't work because I cannot replicate the BSOD so I would be waiting forever not knowing weather it will BSOD or not..

Thanks for the tip though.. But until I can replicate the problem this method will not work.

 

[Shintaro]

Then please run Driver Verifier:
(Borrowed from Zigzag3143 posts)
Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft and click "Next"
7. Select "Finish" on the next page.

• Reboot the system and wait for it to crash to the Blue Screen.
• Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
• The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

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

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Let us know how you go.