Unknown BSOD Errors On Gaming Machine.

Intimidating · 16 Jul 2017

So,

I have been trying to pinpoint the exact cause of these Blue Screens and I don't know what's causing the problem.

Just recently it was working fine, now its doing it commonly. I have tried several methods to no avail. I do have some dumps of them so I'll upload them here.

Also to note. It does this while gaming, trying to install something or a graphics driver.

Specs:
Intel i5-3770K, GTX 670, 1TB HDD, 120GB SSD, Windows 7 Home Premium x64, 16GB of DDR3 RAM.

BSOD Dumps:
http://www.filedropper.com/071617-21496-01
http://www.filedropper.com/071617-24850-01
http://www.filedropper.com/071617-26364-01
http://www.filedropper.com/071617-27362-01
http://www.filedropper.com/071617-27986-01
http://www.filedropper.com/071617-29265-01
http://www.filedropper.com/071617-36410-01

ICIT2LOL · 16 Jul 2017

Hello and welcome Intimidating mate your specs what there is of them are showing you are running Windows 8 if you are then it is bets if you post in the sister forum listed at the top of this page.

If you are running 7 then please follow this
SYSTEM SPECS
Now before we can help we do need to know what is in your machine so please do this System Info - See Your System Specs - Windows 7 Help Forums
or either enter the specs of your system in your forum profile the specs will appear when we click on that little box bottom left of the post screen it is for me the preferable option as it is easy. As you may appreciate it is very hard when you don’t know what one is working with for example a diesel or petrol engine.
(pretyped to save time)

Now to go on to send dump files please follow these
https://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
&
Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Help Forums

Intimidating · 16 Jul 2017

For some reason It wouldn't let me post it here so I have put in in a zip and used an uploading service

https://ufile.io/hrjqk in a .zip file

SPECS are updated on my profile page.

ICIT2LOL · 16 Jul 2017

Sorry mate but still cannot open the dumps and the specs I know you have put them in yur profile because they usually appear at System spec at bottom let of these reply screen and what there is is minimal. But the real issue is getting hold of those dump files.

Just a by the by is this a build of yours and are you overclocking??

Intimidating · 16 Jul 2017

Not overclocking.

Well since you cant open the dumps I could give out these. Would they be of help to you if I gave the errors out?

Logs:
071617-27362-01.dmp 7/16/2017 4:43:05 PM BAD_POOL_HEADER 0x00000019 00000000`00000003 fffff880`02b9a940 00000000`00000000 00000000`00000000 win32k.sys win32k.sys+c7b91 x64 ntoskrnl.exe+70e40 D:\Tools\New folder\071617-27362-01.dmp 4 15 7601 293,480 7/16/2017 4:44:04 PM

071617-26364-01.dmp 7/16/2017 4:03:02 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff880`83fe0ae9 00000000`00000001 fffff800`036bebbc 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+70e40 x64 ntoskrnl.exe+70e40 D:\Tools\New folder\071617-26364-01.dmp 4 15 7601 293,640 7/16/2017 4:04:34 PM

071617-27986-01.dmp 7/16/2017 3:30:39 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000000 00000000`00000007 00000000`00000001 fffff880`047c314d dxgmms1.sys dxgmms1.sys+c14d x64 ntoskrnl.exe+70e40 D:\Tools\New folder\071617-27986-01.dmp 4 15 7601 293,600 7/16/2017 3:36:44 PM

071617-24850-01.dmp 7/16/2017 11:41:43 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffa82`10374860 00000000`00000002 00000000`00000000 fffff800`0363730a ntoskrnl.exe ntoskrnl.exe+70e40 x64 ntoskrnl.exe+70e40 D:\Tools\New folder\071617-24850-01.dmp 4 15 7601 293,496 7/16/2017 12:02:22 PM

071617-29265-01.dmp 7/16/2017 9:05:55 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`039511d3 fffff880`06b275f0 00000000`00000000 volmgr.sys volmgr.sys+118c x64 ntoskrnl.exe+70e40 D:\Tools\New folder\071617-29265-01.dmp 4 15 7601 293,376 7/16/2017 9:07:26 AM

071617-36410-01.dmp 7/16/2017 8:45:36 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00005003 fffff700`01080000 00000000`000067aa 00005e03`0200cf54 ntoskrnl.exe ntoskrnl.exe+70e40 x64 ntoskrnl.exe+70e40 D:\Tools\New folder\071617-36410-01.dmp 4 15 7601 293,640 7/16/2017 8:49:56 AM

Sorry if it's a bit frustrating :)

Intimidating · 16 Jul 2017

Ok got some logs:

System Information (local)
--------------------------------------------------------------------------------
Computer name: MATT-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH Z77
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17121587200 bytes total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 16/07/2017 7:13:13 PM your computer crashed
crash dump file: C:\Windows\Minidump\071617-21496-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8000391863B, 0xFFFFF88006EC4450, 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.

On Sun 16/07/2017 4:43:05 PM your computer crashed
crash dump file: C:\Windows\Minidump\071617-27362-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x3, 0xFFFFF88002B9A940, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. This problem might also be caused because of overheating (thermal issue).
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 16/07/2017 4:03:02 PM your computer crashed
crash dump file: C:\Windows\Minidump\071617-26364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x50 (0xFFFFF88083FE0AE9, 0x1, 0xFFFFF800036BEBBC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_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 invalid system memory has been referenced.
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 Sun 16/07/2017 3:30:39 PM your computer crashed
crash dump file: C:\Windows\Minidump\071617-27986-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880047C314D)
Bugcheck code: 0xD1 (0x0, 0x7, 0x1, 0xFFFFF880047C314D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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.

On Sun 16/07/2017 11:41:43 AM your computer crashed
crash dump file: C:\Windows\Minidump\071617-24850-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0xA (0xFFFFFA8210374860, 0x2, 0x0, 0xFFFFF8000363730A)
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.

Intimidating · 16 Jul 2017

Ok update so I'm currently running MemTest and first 20mins elapsed. It found 57056 RAM errors so.. now I think I know what the cause is.

Ill keep you updated and see if it bsods again, after ordering a x4 kit ofc

Might be a week or two.

ICIT2LOL · 16 Jul 2017

Yes mate that last lot of data showed up the memory now it is pinning it down to the stick /s that is/ are he problem .
As you have error you can stop the test

I am assuming you have either x4GB or 2x8GB so you will have to put one stick ata time in slot one and test again when the bad stick/s show up they will need replacing remembering you must have replacements that closely match the sticks you have in there for example the MHz the stick/s run at and the timings if you don't it can cause the system to be quite unstable.

Now you have to look at the sticks for that info but it is quite easy to see. See my pic some RAM sticks are marked as PC something or other an example would be PC012800 which denotes 1600MHz RAM

Now the other thing you might need to keep in mind is what your board manufacturer recommendations though I find them not that essential and if possible buy the RAM in matched pairs that ensures the timings etc are close to each other .

As for brands I personally prefer Corsair G Skill and Crucial but the choice and budget are yours of course but please do not get it from EBay sites unless it is a reputable store.

One last thing to keep in mind if the sticks all test up ok in slot one then it is possible for one of the other slots to be bad but it is unusual.

Edit: once you have it up and running again have a read of this
USING OPTIMISE TUTORIAL
Just a little something that will make your machine a little faster and more efficient is this Optimize Windows 7 - Windows 7 Help Forums
It is my bible when installing an OS on my machines and also when I am fixing friends and family machines too.
Now if you go through it slowly you will find lots of tweaks and they are all really thoroughly done by the authour Brink a fellow who is in my mind brilliant and if you need to ask questions he is just the most obliging person around.
The other thing is that you may lose some of the "bling" such as transparency (you don't have to I find it unnecessary) and all the tweaks are reversible.
If you do get stuck just post back in that tutorial and you will get help. Another bonus using this tutorial is that it helps you find your way around your machine and Windows 7!
Just one tip I would say you start with is do this Registry - Backup and Restore - Windows 7 Help Forums do this and it will save you a lot of grief if you are ever doing things in the registry and even if you don't it is a good back up to have if your system ever gets corrupted.
(pretyped to save time)

Intimidating · 17 Jul 2017

Well after testing all sticks 1 by 1 no errors. After reseating all of them, no error. I have yet to test slot by slot, but its a bit odd now its not giving errors.

**axe0** · 17 Jul 2017

Intimidating said:

For some reason It wouldn't let me post it here so I have put in in a zip and used an uploading service

https://ufile.io/hrjqk in a .zip file

SPECS are updated on my profile page.

Please read BSOD Posting Instructions & How to upload files