DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) error while idle

kylemcauliffe15 · May 28, 2014

My laptop rebooted in the middle of the night, and it was from a bluescreen. I have no idea what caused it but I uploaded the memory dump file to an analyzer and got: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

And that's about all I could figure out from it. I have no idea what the rest of the text means. I have included a zip of the minidump in this post!

Thanks!

blueelvis · May 28, 2014

Hi Kylemcauliffe15,

I have analyzed your dump file and the probable cause for the BSOD you encountered was because of "amd_sata.sys"
For further information on where to update this driver, please visit the below link :-

Driver Reference Table - amd_sata.sys

The Driver dates back to the Year 2012.
For further information, the dump has been analyzed as below :-

1: 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: 00000000000000e8, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880011ac27f, address which referenced memory

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

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff801d1bc6168
GetUlongFromAddress: unable to read from fffff801d1bc61f8
00000000000000e8 Nonpaged pool

CURRENT_IRQL: 9

FAULTING_IP:
amd_sata+727f
fffff880`011ac27f ff81e8000000 inc dword ptr [rcx+0E8h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE: FFFFF880009CEFB0

TRAP_FRAME: fffff880009c6860 -- (.trap 0xfffff880009c6860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011ac27f rsp=fffff880009c69f0 rbp=fffff880009c6ad0
r8=0000000000000029 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
amd_sata+0x727f:
fffff880`011ac27f ff81e8000000 inc dword ptr [rcx+0E8h] ds:00000000`000000e8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801d18c7769 to fffff801d18c8440

STACK_TEXT:
fffff880`009c6718 fffff801`d18c7769 : 00000000`0000000a 00000000`000000e8 00000000`00000009 00000000`00000001 : nt!KeBugCheckEx
fffff880`009c6720 fffff801`d18c5fe0 : 00000000`00000001 fffffa80`07991ff0 fffffa80`00000000 fffff880`009c6860 : nt!KiBugCheckDispatch+0x69
fffff880`009c6860 fffff880`011ac27f : 00000000`00000000 00000000`00000009 fffffa80`07991ff0 fffffa80`07984488 : nt!KiPageFault+0x260
fffff880`009c69f0 00000000`00000000 : 00000000`00000009 fffffa80`07991ff0 fffffa80`07984488 00000000`ffffffff : amd_sata+0x727f

STACK_COMMAND: kb

FOLLOWUP_IP:
amd_sata+727f
fffff880`011ac27f ff81e8000000 inc dword ptr [rcx+0E8h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: amd_sata+727f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: amd_sata

IMAGE_NAME: amd_sata.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 500d9948

FAILURE_BUCKET_ID: AV_amd_sata+727f

BUCKET_ID: AV_amd_sata+727f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_amd_sata+727f

FAILURE_ID_HASH: {541d7c86-3b24-f4f0-3717-9f9546e520e7}

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

1: kd> lmvm amd_sata
start end module name
fffff880`011a5000 fffff880`011c2000 amd_sata T (no symbols)
Loaded symbol image file: amd_sata.sys
Image path: \SystemRoot\System32\drivers\amd_sata.sys
Image name: amd_sata.sys
Timestamp: Tue Jul 24 00:04:48 2012 (500D9948)
CheckSum: 00015295
ImageSize: 0001D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Also, I would suggest you to run Windows Update and grab all the latest update as most of your drivers on your system date back to the year 2012. Please note that it might take several visits to get the latest updates from the Windows Update.

In case the issue is solved, please mark this thread as solved and in case the issue still persists, I will be glad to try to sort it out for you ^_^.

kylemcauliffe15 · May 28, 2014

blueelvis said:
Hi Kylemcauliffe15,

I have analyzed your dump file and the probable cause for the BSOD you encountered was because of "amd_sata.sys"
For further information on where to update this driver, please visit the below link :-

Driver Reference Table - amd_sata.sys

The Driver dates back to the Year 2012.
For further information, the dump has been analyzed as below :-

1: 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: 00000000000000e8, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880011ac27f, address which referenced memory

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

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff801d1bc6168
GetUlongFromAddress: unable to read from fffff801d1bc61f8
00000000000000e8 Nonpaged pool

CURRENT_IRQL: 9

FAULTING_IP:
amd_sata+727f
fffff880`011ac27f ff81e8000000 inc dword ptr [rcx+0E8h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE: FFFFF880009CEFB0

TRAP_FRAME: fffff880009c6860 -- (.trap 0xfffff880009c6860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011ac27f rsp=fffff880009c69f0 rbp=fffff880009c6ad0
r8=0000000000000029 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
amd_sata+0x727f:
fffff880`011ac27f ff81e8000000 inc dword ptr [rcx+0E8h] ds:00000000`000000e8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801d18c7769 to fffff801d18c8440

STACK_TEXT:
fffff880`009c6718 fffff801`d18c7769 : 00000000`0000000a 00000000`000000e8 00000000`00000009 00000000`00000001 : nt!KeBugCheckEx
fffff880`009c6720 fffff801`d18c5fe0 : 00000000`00000001 fffffa80`07991ff0 fffffa80`00000000 fffff880`009c6860 : nt!KiBugCheckDispatch+0x69
fffff880`009c6860 fffff880`011ac27f : 00000000`00000000 00000000`00000009 fffffa80`07991ff0 fffffa80`07984488 : nt!KiPageFault+0x260
fffff880`009c69f0 00000000`00000000 : 00000000`00000009 fffffa80`07991ff0 fffffa80`07984488 00000000`ffffffff : amd_sata+0x727f

STACK_COMMAND: kb

FOLLOWUP_IP:
amd_sata+727f
fffff880`011ac27f ff81e8000000 inc dword ptr [rcx+0E8h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: amd_sata+727f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: amd_sata

IMAGE_NAME: amd_sata.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 500d9948

FAILURE_BUCKET_ID: AV_amd_sata+727f

BUCKET_ID: AV_amd_sata+727f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_amd_sata+727f

FAILURE_ID_HASH: {541d7c86-3b24-f4f0-3717-9f9546e520e7}

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

1: kd> lmvm amd_sata
start end module name
fffff880`011a5000 fffff880`011c2000 amd_sata T (no symbols)
Loaded symbol image file: amd_sata.sys
Image path: \SystemRoot\System32\drivers\amd_sata.sys
Image name: amd_sata.sys
Timestamp: Tue Jul 24 00:04:48 2012 (500D9948)
CheckSum: 00015295
ImageSize: 0001D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Click to expand...

Also, I would suggest you to run Windows Update and grab all the latest update as most of your drivers on your system date back to the year 2012. Please note that it might take several visits to get the latest updates from the Windows Update.

In case the issue is solved, please mark this thread as solved and in case the issue still persists, I will be glad to try to sort it out for you ^_^.

Thanks a lot! I will give this a try and see how it goes. Should I update my BIOS as well? I've not done that before. Also even though you haven't indicated as such yet, nothing looks like it's pointing to a hardware error right? Just checking for peace of mind!

-EDIT

Forgot to ask, is there a program (safe one) out there that lets me know which drivers need to be updated? I regularly use Windows update and there's no driver updates on there. HP support assistant usually delivers those, but it's only a couple that I haven't updated yet I believe. (not counting the BIOS)

blueelvis · May 28, 2014

I would say that updating the BIOS should be the last option before changing the hardware as the updating of BIOS is a very risky process and one needs to be very cautious and wary during the process as even a slight mistake can fry your motherboard and the only option left would be to change the entire motherboard.

I don't think there would be a hardware fault, even if there is then most likely it could be either a faulty wire or loose connections. HP tends to use the Seagate hard disks which are indeed extremely good so the chance of that failing would be minimal. (I have HP desktop myself and the disks are pretty robust)

I found the latest driver on Softpedia over here :- AMD SATA Driver - download tag

Although, if there is an updated version of the driver at the HP website, please download and update that package instead of the above given as sometimes it happens that the system works fine with the OEM drivers only <_<

Please read the instructions carefully before proceeding.

Also, it is not mandatory that the system is not stable if only one BSOD occurs, if you are getting it too frequently then that becomes a problem. So, please perform the above steps and in case of any further problem, please do post back here ^_^

kylemcauliffe15 · May 28, 2014

blueelvis said:
I would say that updating the BIOS should be the last option before changing the hardware as the updating of BIOS is a very risky process and one needs to be very cautious and wary during the process as even a slight mistake can fry your motherboard and the only option left would be to change the entire motherboard.

I don't think there would be a hardware fault, even if there is then most likely it could be either a faulty wire or loose connections. HP tends to use the Seagate hard disks which are indeed extremely good so the chance of that failing would be minimal. (I have HP desktop myself and the disks are pretty robust)

I found the latest driver on Softpedia over here :- AMD SATA Driver - download tag

Although, if there is an updated version of the driver at the HP website, please download and update that package instead of the above given as sometimes it happens that the system works fine with the OEM drivers only <_<

Please read the instructions carefully before proceeding.

Also, it is not mandatory that the system is not stable if only one BSOD occurs, if you are getting it too frequently then that becomes a problem. So, please perform the above steps and in case of any further problem, please do post back here ^_^

Yes that's why I haven't updated the BIOS yet, I figured it was pretty risky. So I will hold off on that for now. Anyway, I went to AMD and used the driver update detector. Found the latest package and installed! Apparently I never EVER updated beyond the factory driver! I thought I did! lol

As of now it looks to be running good. I'll let it sit tonight and see what happens, then if all is well I'll mark the thread as solved.

Thanks a lot!

blueelvis · May 28, 2014

Sure thing, test it out but please make sure that you keep the laptop in a well ventilated and cool place as it happens a lot with me that I just keep the laptop running on the bed above a pillow and it all messes up it's cooling and Voila! there you have a driver IRQL or the Driver Power State Failure BSOD because the laptop becomes extremely hot to operate and Windows shuts it down.

kylemcauliffe15 · May 30, 2014

blueelvis said:
Sure thing, test it out but please make sure that you keep the laptop in a well ventilated and cool place as it happens a lot with me that I just keep the laptop running on the bed above a pillow and it all messes up it's cooling and Voila! there you have a driver IRQL or the Driver Power State Failure BSOD because the laptop becomes extremely hot to operate and Windows shuts it down.

Got some not so good news! I gave my computer a break last night and shut it down. When it booted up, it booted STRAIGHT to a bluescreen except it was unreadable. Like the text was a mess. It still rebooted and didn't glitch up or anything beyond that. I have never, ever seen anything like this before. I'm suspicious of fast startup but beyond that, I got no clue. Could this be something unrelated altogether? I got my suspicions on fast startup. I know how to disable it but I haven't tried yet. Included is another minidump.

blueelvis · May 30, 2014

kylemcauliffe15 said:
blueelvis said:

Sure thing, test it out but please make sure that you keep the laptop in a well ventilated and cool place as it happens a lot with me that I just keep the laptop running on the bed above a pillow and it all messes up it's cooling and Voila! there you have a driver IRQL or the Driver Power State Failure BSOD because the laptop becomes extremely hot to operate and Windows shuts it down.

Click to expand...

Got some not so good news! I gave my computer a break last night and shut it down. When it booted up, it booted STRAIGHT to a bluescreen except it was unreadable. Like the text was a mess. It still rebooted and didn't glitch up or anything beyond that. I have never, ever seen anything like this before. I'm suspicious of fast startup but beyond that, I got no clue. Could this be something unrelated altogether? I got my suspicions on fast startup. I know how to disable it but I haven't tried yet. Included is another minidump.

Hi kyle,
I have analyzed your latest dump file and the analysis is given below :-

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a018b33ff8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88005d7e2e0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802fa1ca168
GetUlongFromAddress: unable to read from fffff802fa1ca1f8
fffff8a018b33ff8 Paged pool

FAULTING_IP:
ks!memcpy+2e0
fffff880`05d7e2e0 f30f6f440af0 movdqu xmm0,xmmword ptr [rdx+rcx-10h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME: fffff880091ca2b0 -- (.trap 0xfffff880091ca2b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=fffffa80270a2eb0
rdx=fffffe1ff1a91158 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005d7e2e0 rsp=fffff880091ca448 rbp=0000000000000002
r8=00000000128a2fa8 r9=000000000094713d r10=000000001959dc08
r11=fffffa8014800008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
ks!memcpy+0x2e0:
fffff880`05d7e2e0 f30f6f440af0 movdqu xmm0,xmmword ptr [rdx+rcx-10h] ds:fffff8a0`18b33ff8=????????????????????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff802f9f8d3e5 to fffff802f9ecc440

STACK_TEXT:
fffff880`091ca0c8 fffff802`f9f8d3e5 : 00000000`00000050 fffff8a0`18b33ff8 00000000`00000000 fffff880`091ca2b0 : nt!KeBugCheckEx
fffff880`091ca0d0 fffff802`f9f06b2b : 00000000`00000000 fffff8a0`18b33ff8 fffffa80`09105b00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33c2b
fffff880`091ca170 fffff802`f9ec9eee : 00000000`00000000 fffffa80`14800008 00000000`1959dc00 fffff880`091ca2b0 : nt!MmAccessFault+0x55b
fffff880`091ca2b0 fffff880`05d7e2e0 : fffff880`05d9e4c9 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`091ca448 fffff880`05d9e4c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ks!memcpy+0x2e0
fffff880`091ca450 fffff880`05d9e65b : fffffa80`09f07300 fffff8a0`12241540 00000000`00000001 fffffa80`08dea940 : ks!KspPinPropertyHandler+0x129
fffff880`091ca4a0 fffff880`0779f693 : 00000000`00000000 fffffa80`09105b00 fffffa80`09f07538 fffff880`091ca6a0 : ks!KsPinPropertyHandler+0x1b
fffff880`091ca4e0 fffff880`05d9d59d : fffff880`091ca5e0 00000000`00000020 00000000`00000001 00000000`00000001 : portcls!PcPinPropertyHandler+0x83
fffff880`091ca560 fffff880`05d9d11b : fffffa80`14800000 fffff880`00000003 fffff8a0`1511a150 fffffa80`00000000 : ks!KspPropertyHandler+0x39d
fffff880`091ca5e0 fffff880`0779c631 : fffffa80`083375f0 fffffa80`09f07300 fffffa80`083375f0 fffffa80`083375f0 : ks!KsPropertyHandler+0x1b
fffff880`091ca630 fffff880`0779c076 : 0000006f`4a0aea00 00000000`00000000 fffffa80`08deae28 00000000`00000000 : portcls!DispatchDeviceIoControl+0x2c1
fffff880`091ca6d0 fffff880`07773a8f : fffffa80`083375f0 fffffa80`089fc210 00000000`00000000 00000000`00000000 : portcls!PcDispatchIrp+0x66
fffff880`091ca740 fffffa80`083375f0 : fffffa80`089fc210 00000000`00000000 00000000`00000000 fffff880`091ca820 : AtihdW86+0x33a8f
fffff880`091ca748 fffffa80`089fc210 : 00000000`00000000 00000000`00000000 fffff880`091ca820 fffff880`07627aa1 : 0xfffffa80`083375f0
fffff880`091ca750 00000000`00000000 : 00000000`00000000 fffff880`091ca820 fffff880`07627aa1 fffffa80`07b78f20 : 0xfffffa80`089fc210

STACK_COMMAND: kb

FOLLOWUP_IP:
ks!memcpy+2e0
fffff880`05d7e2e0 f30f6f440af0 movdqu xmm0,xmmword ptr [rdx+rcx-10h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: ks!memcpy+2e0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ks

IMAGE_NAME: ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 510cbf7e

IMAGE_VERSION: 6.2.9200.16518

BUCKET_ID_FUNC_OFFSET: 2e0

FAILURE_BUCKET_ID: AV_ks!memcpy

BUCKET_ID: AV_ks!memcpy

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_ks!memcpy

FAILURE_ID_HASH: {49c4638b-e87b-ab0b-a6d2-06299d13d513}

Followup: MachineOwner

The driver blamed here is the "ks.sys" but since this is a driver provided by Windows, the chance of this being at fault is extremely less. So on taking a further look at the stack, we see that there is the "AtihdW86.sys" . Click on the driver name and you should be able to find the place on where to update that.

Please update this driver and see if this solves your issue ^_^ . If it is still not solved, I would be glad to help you out.

kylemcauliffe15 · May 30, 2014

blueelvis said:
kylemcauliffe15 said:

blueelvis said:

Sure thing, test it out but please make sure that you keep the laptop in a well ventilated and cool place as it happens a lot with me that I just keep the laptop running on the bed above a pillow and it all messes up it's cooling and Voila! there you have a driver IRQL or the Driver Power State Failure BSOD because the laptop becomes extremely hot to operate and Windows shuts it down.

Click to expand...

Got some not so good news! I gave my computer a break last night and shut it down. When it booted up, it booted STRAIGHT to a bluescreen except it was unreadable. Like the text was a mess. It still rebooted and didn't glitch up or anything beyond that. I have never, ever seen anything like this before. I'm suspicious of fast startup but beyond that, I got no clue. Could this be something unrelated altogether? I got my suspicions on fast startup. I know how to disable it but I haven't tried yet. Included is another minidump.

Click to expand...

Hi kyle,
I have analyzed your latest dump file and the analysis is given below :-

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a018b33ff8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88005d7e2e0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802fa1ca168
GetUlongFromAddress: unable to read from fffff802fa1ca1f8
fffff8a018b33ff8 Paged pool

FAULTING_IP:
ks!memcpy+2e0
fffff880`05d7e2e0 f30f6f440af0 movdqu xmm0,xmmword ptr [rdx+rcx-10h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME: fffff880091ca2b0 -- (.trap 0xfffff880091ca2b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=fffffa80270a2eb0
rdx=fffffe1ff1a91158 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005d7e2e0 rsp=fffff880091ca448 rbp=0000000000000002
r8=00000000128a2fa8 r9=000000000094713d r10=000000001959dc08
r11=fffffa8014800008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
ks!memcpy+0x2e0:
fffff880`05d7e2e0 f30f6f440af0 movdqu xmm0,xmmword ptr [rdx+rcx-10h] ds:fffff8a0`18b33ff8=????????????????????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff802f9f8d3e5 to fffff802f9ecc440

STACK_TEXT:
fffff880`091ca0c8 fffff802`f9f8d3e5 : 00000000`00000050 fffff8a0`18b33ff8 00000000`00000000 fffff880`091ca2b0 : nt!KeBugCheckEx
fffff880`091ca0d0 fffff802`f9f06b2b : 00000000`00000000 fffff8a0`18b33ff8 fffffa80`09105b00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33c2b
fffff880`091ca170 fffff802`f9ec9eee : 00000000`00000000 fffffa80`14800008 00000000`1959dc00 fffff880`091ca2b0 : nt!MmAccessFault+0x55b
fffff880`091ca2b0 fffff880`05d7e2e0 : fffff880`05d9e4c9 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`091ca448 fffff880`05d9e4c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ks!memcpy+0x2e0
fffff880`091ca450 fffff880`05d9e65b : fffffa80`09f07300 fffff8a0`12241540 00000000`00000001 fffffa80`08dea940 : ks!KspPinPropertyHandler+0x129
fffff880`091ca4a0 fffff880`0779f693 : 00000000`00000000 fffffa80`09105b00 fffffa80`09f07538 fffff880`091ca6a0 : ks!KsPinPropertyHandler+0x1b
fffff880`091ca4e0 fffff880`05d9d59d : fffff880`091ca5e0 00000000`00000020 00000000`00000001 00000000`00000001 : portcls!PcPinPropertyHandler+0x83
fffff880`091ca560 fffff880`05d9d11b : fffffa80`14800000 fffff880`00000003 fffff8a0`1511a150 fffffa80`00000000 : ks!KspPropertyHandler+0x39d
fffff880`091ca5e0 fffff880`0779c631 : fffffa80`083375f0 fffffa80`09f07300 fffffa80`083375f0 fffffa80`083375f0 : ks!KsPropertyHandler+0x1b
fffff880`091ca630 fffff880`0779c076 : 0000006f`4a0aea00 00000000`00000000 fffffa80`08deae28 00000000`00000000 : portcls!DispatchDeviceIoControl+0x2c1
fffff880`091ca6d0 fffff880`07773a8f : fffffa80`083375f0 fffffa80`089fc210 00000000`00000000 00000000`00000000 : portcls!PcDispatchIrp+0x66
fffff880`091ca740 fffffa80`083375f0 : fffffa80`089fc210 00000000`00000000 00000000`00000000 fffff880`091ca820 : AtihdW86+0x33a8f
fffff880`091ca748 fffffa80`089fc210 : 00000000`00000000 00000000`00000000 fffff880`091ca820 fffff880`07627aa1 : 0xfffffa80`083375f0
fffff880`091ca750 00000000`00000000 : 00000000`00000000 fffff880`091ca820 fffff880`07627aa1 fffffa80`07b78f20 : 0xfffffa80`089fc210

STACK_COMMAND: kb

FOLLOWUP_IP:
ks!memcpy+2e0
fffff880`05d7e2e0 f30f6f440af0 movdqu xmm0,xmmword ptr [rdx+rcx-10h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: ks!memcpy+2e0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ks

IMAGE_NAME: ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 510cbf7e

IMAGE_VERSION: 6.2.9200.16518

BUCKET_ID_FUNC_OFFSET: 2e0

FAILURE_BUCKET_ID: AV_ks!memcpy

BUCKET_ID: AV_ks!memcpy

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_ks!memcpy

FAILURE_ID_HASH: {49c4638b-e87b-ab0b-a6d2-06299d13d513}

Followup: MachineOwner

Click to expand...

The driver blamed here is the "ks.sys" but since this is a driver provided by Windows, the chance of this being at fault is extremely less. So on taking a further look at the stack, we see that there is the "AtihdW86.sys" . Click on the driver name and you should be able to find the place on where to update that.

Please update this driver and see if this solves your issue ^_^ . If it is still not solved, I would be glad to help you out.

That's the AMD HDMI Audio driver which is really strange because the APU driver update I installed came with it. I did the custom installation option and saw HD AUDIO in the list. It was checked and should have installed with the rest of the package. I do recall during installation the progress bar changes denoting which driver is being installed at a time and during one of the many instances it said "installing catalyst control center" a "Windows installer has stopped" box appeared but the AMD installer never froze and never gave any errors itself!

I went ahead and grabbed the installer again and it says that the latest version of the audio driver is already installed. There's an option to reinstall over the current installation but I don't think I want to do that! Also there are some checked options I cannot uncheck; they say those components are installed but that they will be RE-installed. Finally there is an uninstall option but I don't know about trying that just yet.

One last thing; I went ahead and disabled fast boot then shut down. No bluescreen and behaved just like all my restarts since the first bluescreen.

blueelvis · May 31, 2014

So, you have finally solved your issue by just disabling the Fast Boot option?

If yes, then I am glad that the issue was solved ^_^ .

Please test the system further and let me know if any further issues crop up ^_^

kylemcauliffe15 · Jun 10, 2014

blueelvis said:
So, you have finally solved your issue by just disabling the Fast Boot option?

If yes, then I am glad that the issue was solved ^_^ .

Please test the system further and let me know if any further issues crop up ^_^

I was just about to mark this as solved (sorry for taking so long) but something new happened tonight. Was running Firefox, and like usual sometimes it locks up from a shockwave or flash player freeze. As soon as the "shockwave may not be responding" message appeared Firefox locked up and then the COMPUTER locked for around 5 seconds. Then I get a message from the notification center that said something to the effect of "AMD hardware has recovered from an error." It popped up twice despite only locking once. This is weird because according to error history, the ONLY error this computer has had on the list was the SAME error from February last year, the month after I bought it. And that time I didn't even know it happened nor saw it since.

So far it has not done it again but keep in mind this was about 20 minutes ago. I'm including both minidumps it gave me. I am very worried this could be a sign of hardware failure. :C

I hope you don't mind checking this out one last time. Thank you so much!

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) error while idle

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer

OMG Debugger!

My Computer

New Member

My Computer