[SOLVED] Unrepeatable BSOD, fixed few problems I think, more inside - Windows 8.1 x64

Made your post a little bit friendlier : )

Let me know how things go when you finally get the new PSU.

Regards,

Patrick
 
Right on time averaging 10 days (11 days in this case) I got another bluescreen. This one not related to GPU I don't think as it says Tcpip.sys which was the network driver, which I haven't seen it lead to that since the first motherboard crashes. Dump file is attached.

Edit: DRIVER_IRQL_NOT_LESS_OR_EQUAL was error caused by tcpip.sys that is. New PSU on its way. These last two errors haven't been relating to the GPU which is weird.
 

Attachments

Is it really unlikely to be the motherboard again? Or should I look into RMAing that as well after the PSU. I'd hope that I wouldn't be that unlucky.
 
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

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

Code: 
2: kd> .trap 0xffffd0003b79b560
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe000ca6a6540 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800e6ea5acf rsp=ffffd0003b79b6f0 rbp=0000000000000000
 r8=fffff800e7020740  r9=0000000000000001 r10=000000000000007f
r11=000000000007286c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
tcpip!TcpPeriodicTimeoutHandler+0x81f:
fffff800`e6ea5acf 4c8b7580        [COLOR=#ff0000]mov     [/COLOR][COLOR=#0000cd]r14[/COLOR],qword ptr [[COLOR=#800080]rbp-80h[/COLOR]] ss:0018:ffffffff`ffffff80=????????????????

Failure moving the contents of the rbp-80h register to the r14 register. This was an instruction from tcpip!TcpPeriodicTimeoutHandler+0x81f, which is a TCP/IP routine (networking related). Your problem just confuses me more and more :grin1:

1. Uninstall MSI Afterburner. If that's not installed, uninstall MSI Live Update.

2. Uninstall Intel Smart Connect.

3. Update your Intel(R) Gigabit Adapter NDIS 6.x driver if possible. If I can remember, we swapped from Killer network driver > Intel's because we were having issues with Killer's, correct?

Regards,

Patrick
 
Hey Patrick thanks for replying. I updated the Intel adapter driver just after the crash. As far as I know, MSI Afterburner or Live Update aren't installed. Intel Smart Connect was never installed either. I opted out of installed them on this install of Windows when installing my audio drivers and stuff from the MSI mobo CD. I have since updated the stuff that I did install from the CD as far as I am aware.

Yeah I was a bit confused and worried when I saw that it wasn't the GPU the last two crashes. Though there's not much to do other than replace the PSU and then continue troubleshooting afterwards I guess, eliminating things one by one.

Edit: Confirming that MSI Afterburner and MSI Live Update are not installed, Intel Smart Connect is not installed either, and the network driver for the Intel Gigabit CT Adapter has been updated

Yeah I originally was getting errors regarding the network adapter (Killer ethernet) when I had the first faulty motherboard. That's why I went and bought the Intel adapter. It's probably possible to use either at this point, but since the Killer adapter required me to update its driver before I could access the internet and the Intel one didn't, I just stuck an ethernet cord into the Intel and haven't looked back.
 
Do me a favor and rename the drivers then in C:\Windows\System32\Drivers

NTIOLib_X64.sys > NTIOLib_X64.old

ISCTD64.sys > ISCTD64.old

and then restart.

Regards,

Patrick
 
I don't see a NTIOLib_X64.sys wtf. The ISCTD64.sys is there though.

When searching for NTIOLib_X64.sys, I find one in my MSI CD that I have saved in My Documents.
 
Reiterating. There is no NTIOLib_X64.sys in the C:\Windows\System32\Drivers folder. There is one in the folder of my MSI mobo CD that I have a copy of because I don't have an optical drive. What should I do?
 
Apologies, I should have checked. It's not in \Drivers as you said, it appears:

Code: 
2: kd> lmvm NTIOLib_X64
start             end                 module name
fffff800`e998c000 fffff800`e9993000   NTIOLib_X64   (deferred)             
    Image path: \??\[COLOR=#ff0000]C:\Program Files (x86)\MSI\Fast Boot\NTIOLib_X64.sys[/COLOR]
    Image name: NTIOLib_X64.sys
    Timestamp:        Thu Oct 25 21:46:44 2012 (5089EB84)

Regards,

Patrick
 
Renamed and restarting. Does it matter that there's another one in my MSI CD folder?

Edit: Alright we're back.
 
It shouldn't, no. That's likely just the driver to be implemented/installed as opposed to the one that's actually loaded that we just renamed.

Keep me updated as usual.

Regards,

Patrick
 
Renaming from .sys. to .old simply stops the drivers from loading. Those drivers I suspect of causing a potential conflict, and they're unnecessary regardless.

Regards,

Patrick
 
Update: Replacement PSU is in. Lets see how the system responds now. Will be back with any further news.
 
Update:

BSOD with error -> IRQL_NOT_LESS_OR_EQUAL. Error occurred while playing League of Legends. Nothing seemed out of the ordinary. The replacement PSU is in and nothing feels like it has changed. Dump file attached. Maybe I'll be looking into RMAing the motherboard again? Not sure what else it could be, unless the RAM is trash even though it passed multiple memtests.
 

Attachments

RMA the motherboard, or get a refund if possible and get an entirely different model. In the meantime while you're going through the RMA process, run one stick at a time in different slots to see if that helps. I'd RMA the RAM too if you can just so we're sure at this point really. By the time we're done here, you'll have a brand new computer :r1:

Regards,

Patrick
 
Alright. Will get on that and update when I can. Until I have the new board in I'm still going to post dump files and updates here, for my own sake of knowing what happened when.

Thanks Patrick.
 
I'm a little skeptical that it's the RAM after using it for so long. However I have a sinking feeling that it might be something as little as a piece of dust in the ram slot. I haven't been able to check because of the cpu cooler blocking my access to the RAM.

Gonna remove the noctua and put the stock cooler on when I get home to inspect the slots and sticks. I might be in denial or something but I thought I'd try it just in case I don't have to send things back just yet. Something definitely improved after the motherboard swap way back, but the errors now seem like nothing's changed but the frequency of them.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top