BSOD Restart, Watching DVD, Incomplete Start

22nd of June, 6 months after the PC upgrade.

The motherboard supports SSD but the drivers are really outdated.

I checked my motherboard and found NO bad capacitors also my ram modules safety was in place.

Hello,

I'm back. It seems BOSD wont stop but this time I'm 99% what is causing it. It being a long time since the last BOSD.

As I was doing my usual stuff on Firefox it crashed closed it self and asked me if I want to send a crash report. I wrote a word in the comments and clicked ok then boom BOSD. In the dump file it says something about usb port driver. A few weeks ago firefox got stuck like old times when I was getting more frequent BOSD but that was due to the misplaced memory module. But after a few minutes firefox came back to normal by itself.

After this BOSD I opened the case to check the ram modules which were all in place and locked.
I don't expect to fix this until I get a new PC. I will keep updating the post for the info.

Thank you.

Code:

BugCheck D1, {fe64840c, 2, 1, fffff88004a13528}

Probably caused by : hardware ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+90c )

I know this bugcheck uses the probability of hardware, however, this is most likely only caused by the misaligned instruction pointer.

Code:

MISALIGNED_IP: 
USBPORT!USBPORT_Core_iCompleteDoneTransfer+90c
fffff880`04a13528 42084c897a      or      byte ptr [rcx+r9*4+7Ah],cl

I believe the Assembly instruction is using the bitwise OR (||) logical operator on two operands, and then reserving the result into a byte of memory. The pointer is probably used to reference the address in which result of the OR operation is stored at, which I believe is the cl register. I may be wrong though, since I've never written any Assembly code before.

Code:

0: kd> u USBPORT!USBPORT_Core_iCompleteDoneTransfer+90c
USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x90c:
fffff880`04a13528 42084c897a      or      byte ptr [rcx+r9*4+7Ah],cl <-- Misaligned Instruction Pointer
fffff880`04a1352d 18488b          sbb     byte ptr [rax-75h],cl
fffff880`04a13530 8424e8          test    byte ptr [rax+rbp*8],ah
fffff880`04a13533 0000            add     byte ptr [rax],al
fffff880`04a13535 004c6374        add     byte ptr [rbx+74h],cl
fffff880`04a13539 2460            and     al,60h
fffff880`04a1353b 44897030        mov     dword ptr [rax+30h],r14d
fffff880`04a1353f 488b8424e8000000 mov     rax,qword ptr [rsp+0E8h]

The instruction pointer didn't conform to the memory alignment which the processor uses, I believe data alignment is 16 bytes on x64 systems.

Code:

0: kd> !stack
Call Stack : 5 frames
## Stack-Pointer    Return-Address   Call-Site       
00 fffffa80077484b8 fffff80002ecb569 nt!KeBugCheckEx+0 
01 fffffa80077484c0 fffff80002eca1e0 nt!KiBugCheckDispatch+69 
02 fffffa8007748600 fffff88004a13528 nt!KiPageFault+260 
03 fffffa8007748798 0000018000000400 USBPORT!USBPORT_Core_iCompleteDoneTransfer+90c

A certain driver also has caused a illegal page fault, since the IRQL Level 2, only non-paged pool will be accessible (there is reasoning for this) and therefore the page fault wouldn't be serviced by the Memory Manager.

Do you have the latest chipset drivers?

My motherboard is chipset is updated. version 9.1.2.1007, that's the last version that gigabyte is offering.

Have you checked the Intel support page too?

After using their scan utility it says this.


Intel Chipset Software Installation Utility (Chipset INF)
Product Detected Intel® 6, 5, 4, 3, 900 Series Chipsets Current Version Installed 9.1.2.1007 This version is valid.




Also this about this utility

infinst_autol.exe


Version:
9.4.0.1026

**Important**
The Intel Chipset Device Software does not install drivers for AGP or USB. DO NOT DOWNLOAD THIS UTILITY IF YOUR DEVICE MANUFACTURER IS RECOMMENDING IT TO CORRECT AN "AGP DRIVER," "AGP GART," OR "USB DRIVER" ISSUE; IT WILL NOT CORRECT YOUR ISSUE.

Have you tried searching on the Support Page for it manually?

I searched with the red colored word: South Bridge: Intel® ICH9

downloaded and ran as an administrator: infinst_autol

I will wait for the next BSOD then.