BSOD Windows 8 help

kennethbradley3 · Mar 1, 2014

http://pcpartpicker.com/p/QUs6 This is my build only thing different is I have windows 8 never had 7. I also have a caviar black instead of blue. I had to Rma the Blue. Also my drive with the OC is now a PNY XLR8 PRO SSD9SC120GCDA-RB. The Caviar Black is just for storage. The Dump files i have gotten so far are

022214-8424-01.dmp 2/22/2014 12:39:53 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffff680`001f1660 00000000`00000000 00000000`00000000 fffff800`7c33a5aa ntoskrnl.exe ntoskrnl.exe+5a440 x64 ntoskrnl.exe+5a440 C:\WINDOWS\Minidump\022214-8424-01.dmp 4 15 9200 296,560 2/22/2014 12:40:37 PM

022314-8595-01.dmp 2/23/2014 11:10:01 PM PFN_LIST_CORRUPT 0x0000004e 00000000`00000099 00000000`0017b1d6 00000000`00000002 0c000130`001327d3 ntoskrnl.exe ntoskrnl.exe+5a440 x64 ntoskrnl.exe+5a440 C:\WINDOWS\Minidump\022314-8595-01.dmp 4 15 9200 296,680 2/23/2014 11:10:41 PM

030114-6848-01.dmp 3/1/2014 11:08:06 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`05a57f03 fffff880`0cd95060 00000000`00000000 dxgmms1.sys dxgmms1.sys+1ef03 x64 ntoskrnl.exe+5a440 C:\WINDOWS\Minidump\030114-6848-01.dmp 4 15 9200 296,632 3/1/2014 11:08:39 AM

030114-6832-01.dmp 3/1/2014 11:09:04 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff802`824dfb58 fffff880`0d22f550 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+5a440 x64 ntoskrnl.exe+5a440 C:\WINDOWS\Minidump\030114-6832-01.dmp 4 15 9200 296,464 3/1/2014 11:09:36 AM

030114-7020-01.dmp 3/1/2014 6:45:58 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 fffff680`00024000 a6c00001`164a8867 fffffa80`097bbc20 ntoskrnl.exe ntoskrnl.exe+5a440 x64 ntoskrnl.exe+5a440 C:\WINDOWS\Minidump\030114-7020-01.dmp 4 15 9200 295,216 3/1/2014 6:46:30 PM

030114-6942-01.dmp 3/1/2014 6:46:38 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041792 fffff680`003a7000 00000000`08000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+5a440 x64 ntoskrnl.exe+5a440 C:\WINDOWS\Minidump\030114-6942-01.dmp 4 15 9200 291,864 3/1/2014 6:48:07 PM

030114-7394-01.dmp 3/1/2014 7:47:10 PM BAD_POOL_HEADER 0x00000019 00000000`0000000d fffff8a0`03928000 b2564cac`6342a4f8 b2564cac`6b42a4f8 fltmgr.sys fltmgr.sys+6144 x64 ntoskrnl.exe+5a440 C:\WINDOWS\Minidump\030114-7394-01.dmp 4 15 9200 296,632 3/1/2014 7:48:07 PM

These all have happened if I shut my computer down and the turn it back on. If I only put it to sleep then I don't have these issues. I have ran memtest and sfc/scannow with no issues. I have updated my bios and graphics card driver I am not sure what other drivers there are. I am very new to this so any advice would be great and thank you.

scout_03 · Mar 1, 2014

test to made http://windows.microsoft.com/en-us/windows-8/resolve-windows-blue-screen-errors

kennethbradley3 · Mar 2, 2014

scout_03 :

I had no luck with using that site, but thanks anyways scout_03

scout_03 · Mar 2, 2014

did you try the win 7 troubleshoothing you never know you could find something . adding this did you try the windows repair and did you memtest all memory sticks .

kennethbradley3 · Mar 3, 2014

scout_03 :

I didn't think to look into the windows 7 troubleshooting since I'm running 8, but I'll check that out. Windows repair was also no use and I've done about 30 passes with memtest to no avail. One thing I did learn is that my ram is not on my motherboard's QVL so maybe that's part of my problem, but I want to eliminate any cheaper fixes first.

scout_03 · Mar 3, 2014

check in the bios since you only have one stick it must be in single channel ,also try the mem ok button on the motherboard .

kennethbradley3 · Mar 4, 2014

scout_03 :

I checked the ram and it is in single channel but it's only showing 1333mhz when it's a 1600mhz could that be an issue? My memok led isn't flashing should I still push the button?

scout_03 · Mar 4, 2014

not it is ok this means it read ram and the work at factory specs use this to read the minidump files in plain text http://www.resplendence.com/whocrashed

kennethbradley3 · Mar 4, 2014

scout_03 :

So this is what I got.
On Sun 3/2/2014 10:31:26 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030214-8814-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xE1 (0xFFFFF800C3F27B18, 0x1, 0xFFFFFA800760CCB0, 0xFFFFFA800760CCB0)
Error: WORKER_THREAD_RETURNED_AT_BAD_IRQL
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 worker thread completed and returned with IRQL 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 Sun 3/2/2014 10:31:26 PM 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: 0xE1 (0xFFFFF800C3F27B18, 0x1, 0xFFFFFA800760CCB0, 0xFFFFFA800760CCB0)
Error: WORKER_THREAD_RETURNED_AT_BAD_IRQL
Bug check description: This indicates that a worker thread completed and returned with IRQL 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 Sun 3/2/2014 12:47:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030114-7394-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x19 (0xD, 0xFFFFF8A003928000, 0xB2564CAC6342A4F8, 0xB2564CAC6B42A4F8)
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.
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 3/1/2014 11:46:38 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030114-6942-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680003A7000, 0x8000000, 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 3/1/2014 11:45:58 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030114-7020-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000024000, 0xA6C00001164A8867, 0xFFFFFA80097BBC20)
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 3/1/2014 4:09:04 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030114-6832-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802824DFB58, 0xFFFFF8800D22F550, 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 Sat 3/1/2014 4:08:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030114-6848-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1EF03)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005A57F03, 0xFFFFF8800CD95060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Mon 2/24/2014 4:10:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022314-8595-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x4E (0x99, 0x17B1D6, 0x2, 0xC000130001327D3)
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 2/22/2014 5:39:53 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022214-8424-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA (0xFFFFF680001F1660, 0x0, 0x0, 0xFFFFF8007C33A5AA)
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.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

scout_03 · Mar 4, 2014

did you overclock the system or any parts in it i would also check all the driver for update specialy the gpu one for this error dxgmms1.sys the other thin use ccleaner and malwarebytes and the last one a full virus on start up if you could without network on .

kennethbradley3 · Mar 4, 2014

scout_03 :

I don't have anything overclocked and I just did every driver on Asus's website under the motherboard for drivers. The chipset kept bringing up a catalyst control which seemed to do nothing and the one for raid had no application so I'm not sure it was any use. I also did the ccleaner and malwarebytes, but not the virus yet. I did a full shut down and no BSOD yet but I might have just gotten lucky this time. I will have to see if I get another.

scout_03 · Mar 4, 2014

if your graphic card is a amd you need to update the driver also for her .

kennethbradley3 · Mar 4, 2014

scout_03 :

That one was Nvidia, but I got it. I am now on my second start up and no BSOD. Hopefully this is good news, it's never made it that far before.

scout_03 · Mar 4, 2014

go on with all the process and come back if something goes wrong .

kennethbradley3 · Mar 4, 2014

scout_03 :

Sounds good and thank you.

scout_03 · Mar 4, 2014

your welcome .

kennethbradley3 · Mar 5, 2014

scout_03 :

I spoke too soon. I just got this on start up.
On Wed 3/5/2014 3:21:58 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!W32pArgumentTable+0x3B44)
Bugcheck code: 0x50 (0xFFFFF901087664F0, 0x0, 0xFFFFF96000084EF8, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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.

scout_03 · Mar 5, 2014

file checker time http://support.microsoft.com/kb/929833/en-us

kennethbradley3 · Mar 6, 2014

scout_03 :

It came up with no problems. I even ran it twice. I have also set it up to do a clean boot, but I am not sure if that will help any or if I should even leave it set up with a clean boot. http://support.microsoft.com/kb/929135

I just got these two this morning from the same BSOD.
On Thu 3/6/2014 2:00:23 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030614-7425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA (0xFFFFF680000AD988, 0x0, 0x0, 0xFFFFF801982E5403)
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 Thu 3/6/2014 2:00:23 PM 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: 0xA (0xFFFFF680000AD988, 0x0, 0x0, 0xFFFFF801982E5403)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

scout_03 · Mar 6, 2014

we will do one thing did you remove the caviar black when you test the system and does it still have a os on also did you put the ssd in ahci in the bios before the install of the os and is it set as first boot device,the other thing you still have that win 7 if the system dont work with win 8 on ssd retry it with the win 7 on the hdd only since the last error we have if set a few post upper .

kennethbradley3 · Mar 6, 2014

scout_03 :

I did not remove the caviar black but I can try it that way. The caviar black has never had an os on it.I'm not sure what your asking for this part " also did you put the ssd i nahci in the bios before the install" while I did the install the black was disconnected so the only drive was the ssd. The ssd is the first boot device, I checked in the bios. I also don't have windows 7, I've only had windows 8 on this machine.

scout_03 · Mar 6, 2014

ssd work better if there are set in bios as ahci ,so unplug the hdd and test ,for the win 7 i was on the list you post for the parts . the other thing you have that 8 pins atx from the psu to the board also check if you connect the cpu fan in the middle connector for it ,the memory should be in a 2 slot, for the ssd it must be in sata 1 and the hdd in sata 2,last point check if the ram led stay she should goes off after boot if not press mem ok button . all of this in the motherboard user manual

kennethbradley3 · Mar 7, 2014

scout_03 :

I apologize for the windows 7 I never had it, I will fix that it the post. As for everything else sata slots were set to ahci, did the sfc/scannow with hdd disconnected no problems there, 8 pin atx is conneted, cpu fan is in middle connector, ram is in slot A2 and I reseated it for good measure, also ram led does go off. The sata slots were mixed. Originally I only had the caviar blue which was connected into the sata 1. After that I had gotten the ssd, which I had just plugged into the first open slot which was sata 5. So after blue the black was just installed in it's place still in sata 1. Now it's corrected ssd in sata 1 and hdd in sata 2. Could mixing those cause BSOD?

scout_03 · Mar 7, 2014

if could had made some issue system always try to look at the first connected device for boot and in bios the ssd is the first one for boot , everything else is set now how it is going .

kennethbradley3 · Mar 7, 2014

scout_03 :

I had just gotten this BSOD this morning after I had checked all of the things in the previous post. I seem to only get these in the morning when I first start my computer after it has sat for an extended period of time. After that I could turn it off and on all day it seems and no BSOD.

On Fri 3/7/2014 7:33:04 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030714-7472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA (0xFFFFF70001084000, 0x0, 0x0, 0xFFFFF800AFBBA215)
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 3/7/2014 7:33:04 PM 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: 0xA (0xFFFFF70001084000, 0x0, 0x0, 0xFFFFF800AFBBA215)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

BSOD Windows 8 help

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Titan

Reputable

Share this page