Z1710 Extreme6, windows 7, BSOD during any gaming |
Post Reply |
Author | |
jduats
Newbie Joined: 12 Oct 2015 Status: Offline Points: 5 |
Post Options
Thanks(0)
Posted: 12 Oct 2015 at 10:41pm |
I could use some help diagnosing my problem!
I recently built a new PC and it is consistently getting a BSOD after 5-10 minutes of any gaming. It seems to only BSOD during gaming, everything else runs fine. I did a fresh install of Windows 7 with updates, all drivers from the included MB disk, and Nvidia's latest GPU drivers and nothing changed. I'll post the WhoCrashed logs when I get home, but they all seem memory related. I ran memtest from a USBdrive and got zero errors. Build: i-5 6600k ASRock Z170 Extreme6 EVGA 980 TI G.SKILL Ripjaws V Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM
DDR4 2400 (PC4 19200) |
|
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 25073 |
Post Options
Thanks(0)
|
I will wait for your crash info so I know what to look for
Clear CMOS and see if that helps regardless of the crash info though.
|
|
ASRock Expert
Newbie Joined: 04 Oct 2015 Location: Croatia Status: Offline Points: 220 |
Post Options
Thanks(0)
|
I don't recommend W7 on a new platform - its like Vista with a SP3.
Go with 8.1 or W10 dude, You should do great with that. Anyway - could You write down more details about Your rig? The PSU, cooling, overclocking ETC. |
|
990FX Extreme 9 MOD P1.70
AMD FX 8120 4GHz 1.25V Thermalright HR-02 Patriot Viper 2x4GB 2133MHz Samsung 850 EVO 250GB MSI R7970 TFIII 3GB CORSAIR VX550W LanCool K62 Dragonlord ASUS Xonar D2X |
|
jduats
Newbie Joined: 12 Oct 2015 Status: Offline Points: 5 |
Post Options
Thanks(0)
|
Thanks for the quick replies, I'll reset the CMOS after I get home this afternoon, do I need to do anything else after I reset? No overclocking yet, the build is like 3 days old and I wanted to get it stable first. Cooling: Coolermaster Hyper 212 EVO PSU: CORSAIR HX Series HX850 850W ATX12V 2.3 / EPS12V 2.91 80 PLUS GOLD (from previous build)
|
|
jduats
Newbie Joined: 12 Oct 2015 Status: Offline Points: 5 |
Post Options
Thanks(0)
|
Here's the WhoCrashed Report:
On Mon 10/12/2015 1:44:47
PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown (0xFFFFF680000A5E38) Bugcheck code: 0x1A (0x41201, 0xFFFFF680000A5E38, 0x87E004022A01C867, 0xFFFFFA8014A4EB30) Error: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. A third party driver was identified as the probable root cause of this system error. Google query: MEMORY_MANAGEMENT On Mon 10/12/2015 12:27:37 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\101215-7644-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002C6E95F) 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 Mon 10/12/2015 12:06:29 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\101215-6708-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0) Bugcheck code: 0x1A (0x41201, 0xFFFFF680001C8530, 0x942000029EE84847, 0xFFFFFA80127A2200) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. |
|
ASRock_TSD
ASRock_Official Joined: 20 Mar 2015 Status: Offline Points: 8787 |
Post Options
Thanks(0)
|
Dear customer,
Thank you for the query. We provide some suggestions to try: 1. Please set BIOS to default settings for try. 2. Please flash the BIOS to P1.50 as the link for try: http://www.asrock.com/mb/Intel/Z170%20Extreme6/?cat=Download&os=BIOS 3. If possible, please use another memory to verify. Thank you for your patience. If any, please feel free to contact us! Kindest Regards, ASRock TSD
|
|
ASRock Expert
Newbie Joined: 04 Oct 2015 Location: Croatia Status: Offline Points: 220 |
Post Options
Thanks(0)
|
You should check Your RAM modules.
Test it with Memtest86+. If You got at least 1 BAD sector, the RAM is bad. If the system hangs during Memtest86+, something is bad with the RAM or the IMC.
|
|
990FX Extreme 9 MOD P1.70
AMD FX 8120 4GHz 1.25V Thermalright HR-02 Patriot Viper 2x4GB 2133MHz Samsung 850 EVO 250GB MSI R7970 TFIII 3GB CORSAIR VX550W LanCool K62 Dragonlord ASUS Xonar D2X |
|
Rabiddog
Newbie Joined: 14 Sep 2015 Status: Offline Points: 40 |
Post Options
Thanks(0)
|
BSOD are hadware failures..never go 10. |
|
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 25073 |
Post Options
Thanks(0)
|
ntoskrnl BSODS can be very tricky to pin down, they can be caused by anything from bad drivers to bad hardware. Given the combination of errors in your dump files it sounds like either RAM or hard disk issues. I say hard disk because it could be occurring when data is swapped from the hard disk to the RAM. Try testing the system a single stick of RAM (use each in turn to determine if one is bad) and run Memtest86+ as Asrock Expert suggested, if both sticks pass individually then test with both in single channel and dual channel configurations. It is quite a lengthy process but worth it to determine where the fault lies. If you have no errors at all then you may want to replace your hard disk SATA cable and run a scan on your drive. I suppose you could try the cable replacement first and see if it solves your issue, if it is the problem it will save you a lot of time. Also try the hard disk on different SATA ports.
Clearing CMOS will set the system to its factory defaults and force the system to reinitialize and redetect your hardware which is why I suggested it initially, fairly often this will correct minor UEFI bugs that can wreak havok on your system. This is usually my first step when troubleshooting.
|
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |