- Jan 9, 2015
- 2
- 0
- 4,510
Hi Everyone,
I'm really looking for some insight as I am about to lose my mind. I built a brand new computer from New Egg on December 26th. The specs are the following:
PSU: CORSAIR HX series HX650 650W
Video Card: EVGA SuperClocked GeForce GTX 760 2GB 256-bit GDDR5 PCI Express 3.0
CPU: Intel Core i7-4770 Haswell Quad-Core 3.4GHz LGA 1150 84W Desktop Processor Intel HD
Mobo: ASUS MAXIMUS VII HERO LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard
SSD: Intel 730 Series SSDSC2BP240G4R5 2.5" 240GB SATA 6Gb/s MLC Internal Solid State Drive (SSD)
Memory: 16GB (2x8GB) PNY DDR3 1600
To make a long story short, everything was working fine the first few days. Off the bat, I had issues playing several games where my game would crash (No Blue Screen, but errors pointing to what appeared to be a faulty graphics driver). These crashes were never consistent and typically after a reboot it would go away until the computer had been on for several hours.
Now, as of more recent, I've been experiencing multiple blue screens that appear to be related to memory. I've ran memtest86+, but I may run that overnight as a next step. I ran through 2 successful tests with no errors.
From this point, I did a complete reinstall and have removed the video card, but I am still receiving BSOD errors so that is not that case. Something tells me it may be the SSD, but I am not 100% sure.
I've installed Seagate Seatools as well as the Intel SSD Toolbox. In Seagate Tools, the Short DST Test fails (don't know what that means). When running the Long test, the computer froze up on me once (couldn't move mouse or anything) and the second time it caused a MEMORY_MANAGEMENT BSOD.
I also ran the Intel SSD Toolbox DIagnostics, and that caused two different BSODs. MEMORY_MANAGEMENT, and a POOL_CORRUPTION_IN_FILE_AREA
One other thing I've noticed is that chrome will continue to fault and say "Aw Snap" right before I receive a MEMORY_MANAGEMENT BSOD..
Here are my most recent BSODs (from WhoCrashed):
computer name: MIKE-DESKTOP
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VII HERO
CPU: GenuineIntel Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8460845056 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 1/10/2015 2:17:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-5265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFF46C6D8, 0x8000, 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 1/10/2015 2:17:26 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 (0x41792, 0xFFFFF6BFFF46C6D8, 0x8000, 0x0)
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 1/10/2015 2:13:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-6015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6804E6C98D8, 0x90400003A0489867, 0xFFFFF6804E6C9918)
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 1/10/2015 1:40:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-5328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xDE (0x2, 0xFFFFC00008F51618, 0xFFFFC00008F515E9, 0x3EEE268C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 driver has corrupted pool memory that is used for holding pages destined for disk.
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 1/10/2015 1:27:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-6375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x402, 0xFFFFC00007FAAF98, 0x8000000386B5EB8A, 0xFFFFC00007FAAF59)
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 1/10/2015 1:15:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-6156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x41284, 0x206E64000, 0x6E17, 0xFFFFF58010804000)
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 1/10/2015 1:01:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-6312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x4E (0x99, 0x29E60B, 0x2, 0x20002900029ED37)
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.
I'm really looking for some insight as I am about to lose my mind. I built a brand new computer from New Egg on December 26th. The specs are the following:
PSU: CORSAIR HX series HX650 650W
Video Card: EVGA SuperClocked GeForce GTX 760 2GB 256-bit GDDR5 PCI Express 3.0
CPU: Intel Core i7-4770 Haswell Quad-Core 3.4GHz LGA 1150 84W Desktop Processor Intel HD
Mobo: ASUS MAXIMUS VII HERO LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard
SSD: Intel 730 Series SSDSC2BP240G4R5 2.5" 240GB SATA 6Gb/s MLC Internal Solid State Drive (SSD)
Memory: 16GB (2x8GB) PNY DDR3 1600
To make a long story short, everything was working fine the first few days. Off the bat, I had issues playing several games where my game would crash (No Blue Screen, but errors pointing to what appeared to be a faulty graphics driver). These crashes were never consistent and typically after a reboot it would go away until the computer had been on for several hours.
Now, as of more recent, I've been experiencing multiple blue screens that appear to be related to memory. I've ran memtest86+, but I may run that overnight as a next step. I ran through 2 successful tests with no errors.
From this point, I did a complete reinstall and have removed the video card, but I am still receiving BSOD errors so that is not that case. Something tells me it may be the SSD, but I am not 100% sure.
I've installed Seagate Seatools as well as the Intel SSD Toolbox. In Seagate Tools, the Short DST Test fails (don't know what that means). When running the Long test, the computer froze up on me once (couldn't move mouse or anything) and the second time it caused a MEMORY_MANAGEMENT BSOD.
I also ran the Intel SSD Toolbox DIagnostics, and that caused two different BSODs. MEMORY_MANAGEMENT, and a POOL_CORRUPTION_IN_FILE_AREA
One other thing I've noticed is that chrome will continue to fault and say "Aw Snap" right before I receive a MEMORY_MANAGEMENT BSOD..
Here are my most recent BSODs (from WhoCrashed):
computer name: MIKE-DESKTOP
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VII HERO
CPU: GenuineIntel Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8460845056 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 1/10/2015 2:17:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-5265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFF46C6D8, 0x8000, 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 1/10/2015 2:17:26 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 (0x41792, 0xFFFFF6BFFF46C6D8, 0x8000, 0x0)
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 1/10/2015 2:13:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-6015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6804E6C98D8, 0x90400003A0489867, 0xFFFFF6804E6C9918)
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 1/10/2015 1:40:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-5328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xDE (0x2, 0xFFFFC00008F51618, 0xFFFFC00008F515E9, 0x3EEE268C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 driver has corrupted pool memory that is used for holding pages destined for disk.
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 1/10/2015 1:27:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-6375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x402, 0xFFFFC00007FAAF98, 0x8000000386B5EB8A, 0xFFFFC00007FAAF59)
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 1/10/2015 1:15:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-6156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x41284, 0x206E64000, 0x6E17, 0xFFFFF58010804000)
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 1/10/2015 1:01:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010915-6312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x4E (0x99, 0x29E60B, 0x2, 0x20002900029ED37)
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.
Facebook
Twitter
Instagram