Hello, thanks in advance for anyone willing to help me, because this is starting to drive me a little batty... I've been building computers for over 20 years now and have never run into this many problems...
so basically about a month I built a new system from scratch based around a i7 7700k processor (never overclocked it or anything crazy). I got it put together just fine and installed windows (been using 8.1) without any problems. After setting it up I started getting hit with random BSODs, all related to the network card. I googled all the errors and did everything suggested (including getting updated ethernet drivers straight from intel) until I decided it that was more than likely a faulty network card on the motherboard. So I RMA'd it (it was a ASRock Z270 KILLER SLI/AC LGA 1151 for the record), they sent me another Asrock board, got it back back together and reinstalled windows and BOOM, back to non-stop BSOD's, once again pointing to bad network drivers. Thinking I got another bad motherboard, I sent it back again and then this time insisted they let me swap it for a different brand, thinking maybe Asrock just had a bad run or something. So instead I got a MSI Z270 Gaming M3 (purposely because it had an entirely different Ethernet chipset), wiped the hard drive clean and did a fresh install of windows 8.1 and.... back to BSOD land, and yet again, pointing to the network drivers as the reason. I flashed the bios on every board before sending them back but that also didn't help. I've even tried downloading every windows update available with no luck or change.
Having no idea what to do at this point I decided to send the RAM back as well, got a new set, new install, same errors. Decided to take some ram out of a working system, fresh install windows 8.1, hit with network BSODs again. thinking maybe there was something wrong with the m.2 hard drive I decided to try and install windows on a regular sata drive, same network errors. I tried taking out the video card and reinstalling windows using only the onboard video, same errors. So at this point I really don't know what to do, the only parts I haven't returned/swapped yet are the processor and the power supply, and now it's way too late to try and return them because I burned over a month swapping the other parts.... I can try and get my year warranty from intel, but before I begin that battle I thought maybe I should seek out additional help. The logs keep insisting its not hardware related, but i don't know what to think any more.
I downloaded the CPU test programs from intel's site and I ran all the tests and it says it passed, I also did memtest on both the new set of ram and the set pulled from a working system, no errors detected. I can't see how a power supply can affect a lan port on three different motherboards, so I'm really confused on what to do here. here's all my whocrashed logs from my latest build, hopefully someone can provide me with some information. The logs keep insisting its not a hardware error, but really what else could it be? Thanks so much!
__________________________
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 5/5/2017 3:56:24 AM your computer crashed
crash dump file: C:\Windows\Minidump\050517-5625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0xA (0xFFFFFD3550855050, 0x2, 0x1, 0xFFFFF8016D83AFAB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/5/2017 3:35:27 AM your computer crashed
crash dump file: C:\Windows\Minidump\050517-4375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8010C083495, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 5/4/2017 1:40:55 PM your computer crashed
crash dump file: C:\Windows\Minidump\050417-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 5/4/2017 1:40:55 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 5/4/2017 1:34:50 PM your computer crashed
crash dump file: C:\Windows\Minidump\050417-5140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800BC113FC6, 0xFFFFD000277B2F10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
8 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
so basically about a month I built a new system from scratch based around a i7 7700k processor (never overclocked it or anything crazy). I got it put together just fine and installed windows (been using 8.1) without any problems. After setting it up I started getting hit with random BSODs, all related to the network card. I googled all the errors and did everything suggested (including getting updated ethernet drivers straight from intel) until I decided it that was more than likely a faulty network card on the motherboard. So I RMA'd it (it was a ASRock Z270 KILLER SLI/AC LGA 1151 for the record), they sent me another Asrock board, got it back back together and reinstalled windows and BOOM, back to non-stop BSOD's, once again pointing to bad network drivers. Thinking I got another bad motherboard, I sent it back again and then this time insisted they let me swap it for a different brand, thinking maybe Asrock just had a bad run or something. So instead I got a MSI Z270 Gaming M3 (purposely because it had an entirely different Ethernet chipset), wiped the hard drive clean and did a fresh install of windows 8.1 and.... back to BSOD land, and yet again, pointing to the network drivers as the reason. I flashed the bios on every board before sending them back but that also didn't help. I've even tried downloading every windows update available with no luck or change.
Having no idea what to do at this point I decided to send the RAM back as well, got a new set, new install, same errors. Decided to take some ram out of a working system, fresh install windows 8.1, hit with network BSODs again. thinking maybe there was something wrong with the m.2 hard drive I decided to try and install windows on a regular sata drive, same network errors. I tried taking out the video card and reinstalling windows using only the onboard video, same errors. So at this point I really don't know what to do, the only parts I haven't returned/swapped yet are the processor and the power supply, and now it's way too late to try and return them because I burned over a month swapping the other parts.... I can try and get my year warranty from intel, but before I begin that battle I thought maybe I should seek out additional help. The logs keep insisting its not hardware related, but i don't know what to think any more.
I downloaded the CPU test programs from intel's site and I ran all the tests and it says it passed, I also did memtest on both the new set of ram and the set pulled from a working system, no errors detected. I can't see how a power supply can affect a lan port on three different motherboards, so I'm really confused on what to do here. here's all my whocrashed logs from my latest build, hopefully someone can provide me with some information. The logs keep insisting its not a hardware error, but really what else could it be? Thanks so much!
__________________________
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 5/5/2017 3:56:24 AM your computer crashed
crash dump file: C:\Windows\Minidump\050517-5625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0xA (0xFFFFFD3550855050, 0x2, 0x1, 0xFFFFF8016D83AFAB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/5/2017 3:35:27 AM your computer crashed
crash dump file: C:\Windows\Minidump\050517-4375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8010C083495, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 5/4/2017 1:40:55 PM your computer crashed
crash dump file: C:\Windows\Minidump\050417-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 5/4/2017 1:40:55 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 5/4/2017 1:34:50 PM your computer crashed
crash dump file: C:\Windows\Minidump\050417-5140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800BC113FC6, 0xFFFFD000277B2F10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
8 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Facebook
Twitter
Instagram