Hey guys I just got my new pc couple days ago, everything was going fine until i started getting this BSOD. It usually appears when Im playing a video game (steam). I have 2 ram memories 8gb each making it 16 gb total ... Here is the crash dump info if someone could help me i would appreciate it.
///NEW///
I actually got 2 errors today with the memtest... bad thing, I did the test with both ram memories... This is the picture of the results http://imgur.com/1a6prrN
Im always able to get into windows it happened while playing CS GO again. . .
Im now trying with only 1 ram card so I will update the results...
System Information (local)
--------------------------------------------------------------------------------
Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\Windows
Hardware: ASRock, Z170 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17128554496 bytes total
Im using two adata xpg 8gb ddr4 2400 corsair already tried the memtest and everything seems to work.. .
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 10/4/2015 4:34:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68079E5E458, 0xCA700001EEE94867, 0xFFFFE0015EC46DA0)
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.
On Sun 10/4/2015 4:34:02 AM GMT 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: 0x1A (0x41201, 0xFFFFF68079E5E458, 0xCA700001EEE94867, 0xFFFFE0015EC46DA0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 10/3/2015 10:36:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7671-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFEA1B0E0, 0x2000000, 0x0)
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.
On Sat 10/3/2015 10:19:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x4E (0x99, 0x217FCA, 0x2, 0xA0001F0001F679C)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
On Sat 10/3/2015 5:11:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680183D8810, 0x40000000000000, 0x0)
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.
On Sat 10/3/2015 5:09:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7500-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0xC21C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8002155C21C, 0xFFFFD00025392D38, 0xFFFFD00025392550)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
///NEW///
I actually got 2 errors today with the memtest... bad thing, I did the test with both ram memories... This is the picture of the results http://imgur.com/1a6prrN
Im always able to get into windows it happened while playing CS GO again. . .
Im now trying with only 1 ram card so I will update the results...
System Information (local)
--------------------------------------------------------------------------------
Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\Windows
Hardware: ASRock, Z170 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17128554496 bytes total
Im using two adata xpg 8gb ddr4 2400 corsair already tried the memtest and everything seems to work.. .
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 10/4/2015 4:34:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68079E5E458, 0xCA700001EEE94867, 0xFFFFE0015EC46DA0)
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.
On Sun 10/4/2015 4:34:02 AM GMT 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: 0x1A (0x41201, 0xFFFFF68079E5E458, 0xCA700001EEE94867, 0xFFFFE0015EC46DA0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 10/3/2015 10:36:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7671-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFEA1B0E0, 0x2000000, 0x0)
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.
On Sat 10/3/2015 10:19:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x4E (0x99, 0x217FCA, 0x2, 0xA0001F0001F679C)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
On Sat 10/3/2015 5:11:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680183D8810, 0x40000000000000, 0x0)
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.
On Sat 10/3/2015 5:09:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100315-7500-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0xC21C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8002155C21C, 0xFFFFD00025392D38, 0xFFFFD00025392550)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Facebook
Twitter
Instagram