[SOLVED] CPU/PSU Fan Spin For a Second and Stop on New Build

[Wrench97]

just to prevent new variables from throwing a wrench in the works.

Hey don't blame me for this!! :lol:


I've seen before where the driver date on the manufacturers(Asus) web site refers to the date it was posted and not the date of the driver, or there was a slight modification in the driver package for that date, it may or may not have anything to do with the driver itself.

 

[ickymay]

Your fans starting then shutting down is in keeping with a Ram fault (amongst others) and the blue screens are feasibly ram especially if the Bluescreen causes blamed vary a lot.

It should be noted that your Ram is not on the gigabyte QVL ?

In building premium systems I rarely go for ram above 1600mhz currently as the gain for faster is nominal at around 2-3% measured against the added instability.

If you want to maximise processing bandwidth I suggest PATRIOT 4GB PXD38G2133C11K as opposed to two 8GB sticks or go for Kingston who have very good quality control in place at the moment and also have a cooperative deal with gigabyte.

Re cooling I would strongly suggest a liquid cooled setup for the CPU with a four pin WPM fan to bring your idle noise level down and reduce temperatures to cope with whatever you throw at your i7.

As far as the power button reset is concerned it is not a myth and still works for many if not all motherboards as there will be latent power stored in the caps cleared only by power button on for 30 seconds.

the 30 seconds rule is the standard amount of time for any ic to reset all of its gates to 0.

the recommended reset time as advised by support and test engineers for Intel motherboards is 14 minutes due to caps and gates in advanced ic's that are designed to hold power for that time by design.

All of this is of course my own opinion based on my personal experiences and i reserve the right to be wrong :r1:

 

[Digerati]

As far as the power button reset is concerned it is not a myth and still works for many if not all motherboards as there will be latent power stored in the caps cleared only by power button on for 30 seconds.

the 30 seconds rule is the standard amount of time for any ic to reset all of its gates to 0.

the recommended reset time as advised by support and test engineers for Intel motherboards is 14 minutes due to caps and gates in advanced ic's that are designed to hold power for that time by design.

Do you have ANY supporting evidence for ANY of this? Where are these "standards" you talk about? How can a gate hold power? 14 minutes? Sorry, but no way!

 

[ickymay]

alright angry duck theres no need to shout ...........

While building a premium system for a customer November-December last year against my advice he pre bought an Intel motherboard and Corsair ram.

I fought with the system attempting to get it to post but it continually struggled even with a differing variety of Ram types, sometimes managing it with a single 4GB stick and when I changed the timings to something a bit less aggressive would also boot and install windows.

I also noticed that while changing ram types the motherboard did not reset and the time didnt change and a AHCI setting despite removing the battery and holding the power button to completely drain power.

After two days with this issue I raised a ticket with Intel and an engineer called me back and we went through the problems.

He constantly assured me that 14 minutes holding the power button was neccesary to reset and I must admit I was very sceptical.

As it proved more than once this did in fact work for a proper reset and I have no doubt or reason to question this as the facts where in front of me in practice.

The industry standard for the 30 second reset is something I was taught as an electrician working with early Eproms in the late 1980s and 90s and has been reinforced up until the present day by many training courses when building servers and domestic systems by official bodies such as Comptia.

In practice when a normal battery pull doesn't work this power button drain down has worked for me on numerous occasions but does vary in effectiveness across different Motherboards.

 

[Will]

I had a laptop problem a few years ago - the USB drive stopped working. I was told by someone to take out the battery and hold the power button for 30 seconds - as soon as I'd done that the USB drive worked again. The same problem repeated itself again about a year later - same solution fixed it.

I have only basic knowledge about computer hardware, would this more likely have just been the result of removing the battery?

 

[Digerati]

So, no supporting evidence? Okay.

Please note I am not shouting, just making a point because as a certified master electronics technician for nearly 4 decades who has taught electronics, electronics maintenance and computer repair, I don't go by hearsay, and I get frustrated when rumors are propagated without any supporting evidence.

EPROMS?? What do ERPROMs have to do with resetting the motherboard or the BIOS? Are you suggesting EPROMS store power too? How? And I ask again, how can a gate in a transistor hold power?

against my advice he pre bought an Intel motherboard and Corsair ram.

Against your advice? Huh? Intel has been making quality motherboards for 20 years. And Corsair RAM has consistently made quality RAM for years too, and was one of, if not the first to warranty all their RAM for life.

If a circuit or device takes 14 minutes to fully discharge, it's broken.

 

[Digerati]

@Will Watts - notebooks are different from PCs in how resets are handled because the reset also affects the charging and battery monitoring circuits. And sadly, notebooks are often very proprietary so what works for a Sony notebook may not work for a Toshiba. But in any case, 30 seconds makes a whole lot more sense than 14 minutes.

 

[writhziden]

Your fans starting then shutting down is in keeping with a Ram fault (amongst others) and the blue screens are feasibly ram especially if the Bluescreen causes blamed vary a lot.

It should be noted that your Ram is not on the gigabyte QVL ?

In building premium systems I rarely go for ram above 1600mhz currently as the gain for faster is nominal at around 2-3% measured against the added instability.

If you want to maximise processing bandwidth I suggest PATRIOT 4GB PXD38G2133C11K as opposed to two 8GB sticks or go for Kingston who have very good quality control in place at the moment and also have a cooperative deal with gigabyte.

Re cooling I would strongly suggest a liquid cooled setup for the CPU with a four pin WPM fan to bring your idle noise level down and reduce temperatures to cope with whatever you throw at your i7.

As far as the power button reset is concerned it is not a myth and still works for many if not all motherboards as there will be latent power stored in the caps cleared only by power button on for 30 seconds.

the 30 seconds rule is the standard amount of time for any ic to reset all of its gates to 0.

the recommended reset time as advised by support and test engineers for Intel motherboards is 14 minutes due to caps and gates in advanced ic's that are designed to hold power for that time by design.

All of this is of course my own opinion based on my personal experiences and i reserve the right to be wrong :r1:

The blue screens blame Windows files, but the stack shows the hard disk storage controller drivers in every instance. Two of the three blue screens have been identical. The one off was a display card driver 0x3B crash, but still had storage drivers on the stack. I can provide the full analysis I did later (I'm responding from work, so I don't have my analysis at hand).

When this first happened with the first two blue screens, my first intuition was the problems were due to software since it occurred after Windows updates were installed. I still think that may be the case. In the past two weeks, I have had no problems with the new chipset drivers.

Liquid cooling is out of the question from a personal standpoint. I don't want something in my computer that can take out multiple components if it fails (other than the PSU, but I have a top quality PSU to hopefully prevent that). We had water cooling in a nearly identical system at work, and it led to a damaged display card when it leaked.

The QVL is not the end-all for memory compatibility. It only contains what they were able to test in their limited schedules for testing. If I continue to have problems that point to hardware, I do plan on replacing my RAM with something they recommend in that list. For now, I am making sure this is not software before worrying about replacing more hardware. The bad RAM module is the most likely cause for my issues in the begginning, and it probably led to at least one of my first two blue screens. The video card related crash was likely due to that bad module since it was doing CUDA acceleration at the time. Having done some CUDA programming, I know there is a lot of RAM to video RAM swapping at the beginning of the run, and the crash occurred right when CUDA started being used.

The other two crashes all point to a Intel chipset/Intel storage controller issue. Given the 2011 date on the chipset, I am inclined to think that was the cause, but I won't rule anything out until the system is up and running for more than a couple weeks without problems. It took 30 days before my first blue screen showed up, so this is a very intermittent issue if it even still remains.

 

[Digerati]

Liquid cooling is out of the question from a personal standpoint. I don't want something in my computer that can take out multiple components if it fails (other than the PSU, but I have a top quality PSU to hopefully prevent that). We had water cooling in a nearly identical system at work, and it led to a damaged display card when it leaked.

I wish now we kept track of how many systems with various alternative cooling solutions came across my bench that were damaged (often fatally) by lackadaisical maintenance - it has been many.

Sadly, what typically happens is users who implement liquid cooling are very diligent, at first, at periodically checking for leaks, fluid levels, mold, bacteria, etc. But sadly, after a year or 18 months, they get tired of the inspections and start skipping them more and more as the system ages. The irony there is, as the system ages, routine inspections should increase, not decrease. Before too long, tubing becomes less flexible, vibrations from other fans, drive motors, accidental bumps and heavy footfalls cause fittings to work loose, and coolant begins to leak. If the leaks occurs near the CPU and/or motherboard, disaster is often the result.

Coolant leaks can be particularly bad in cases that mount the PSU on the bottom of the case - for obvious reasons.

A common misconception is that cooler is better. That is not true. While too much heat is certainly a bad thing, there is nothing to suggest that a CPU at 30°C runs better, is more stable or lasts longer, than a CPU running at 50°C or even 60°C. That is NOT to say you can consistently run a CPU near its thermal limits - you can't because stability may suffer and aging may increase (including aging of the socket and surrounding components). That is why my personal threshold is 60°C. If CPU temps stay above that level, it is time to clean the interior of heat trapping dust, check fans, or consider adding additional fans to the case.

 

[writhziden]

Outdated and Problematic Drivers:

You should update/replace/remove the following drivers. Any drivers that are known to cause BSODs, please remove the software or remove the drivers and then remove the device; steps to do so are given after the list of outdated drivers.

dvb7700all.sys Wed Dec 19 22:00:35 2007 (4769F6F3)
YUAN DVB-T/Analog Hybried TV Tuner
http://www.carrona.org/drivers/driver.php?id=dvb7700all.sys

HECIx64.sys Thu Sep 22 10:38:44 2011 (4E7B6494)
Intel Management Engine Interface
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys

​

To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if no driver updates are available for the device. If it does not make sense to remove the device, i.e. the device is a motherboard, please ask us for further assistance.

Uninstall or change a program

Open Device Manager​

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

[font=lucida console]**************************Sat Jun 22 12:56:55.631 2013 (UTC - 6:00)**************************
[COLOR=RED][B]dvb7700all.sys              Wed Dec 19 22:00:35 2007 (4769F6F3)[/B][/COLOR]
[COLOR=RED][B]HECIx64.sys                 Thu Sep 22 10:38:44 2011 (4E7B6494)[/B][/COLOR]
e1i63x64.sys                Wed Feb 29 20:25:14 2012 (4F4EEC1A)
athrx.sys                   Wed Mar 21 21:26:22 2012 (4F6A9BDE)
uimx64.sys                  Sun May 27 17:05:54 2012 (4FC2B352)
UimFIO.SYS                  Sun May 27 17:05:56 2012 (4FC2B354)
Uim_IMx64.sys               Sun May 27 17:06:01 2012 (4FC2B359)
uim_vimx64.sys              Sun May 27 17:06:07 2012 (4FC2B35F)
intelppm.sys                Mon Nov  5 20:55:02 2012 (50988A16)
nvhda64v.sys                Sun Feb 24 22:27:35 2013 (512AF647)
dump_storahci.sys           Fri Mar  1 19:15:44 2013 (513160D0)
nvlddmkm.sys                Sun May 12 13:09:45 2013 (518FE8F9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 07:11:27.880 2013 (UTC - 6:00)**************************
bxvbda.sys                  Mon Jul 23 17:30:50 2012 (500DDEAA)
evbda.sys                   Tue Jul 24 06:22:19 2012 (500E937B)
nvlddmkm.sys                Fri Jan 18 06:22:15 2013 (50F94C87)
[/font]

http://www.carrona.org/drivers/driver.php?id=dvb7700all.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=athrx.sys
http://www.carrona.org/drivers/driver.php?id=uimx64.sys
http://www.carrona.org/drivers/driver.php?id=UimFIO.SYS
http://www.carrona.org/drivers/driver.php?id=Uim_IMx64.sys
http://www.carrona.org/drivers/driver.php?id=uim_vimx64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=bxvbda.sys
http://www.carrona.org/drivers/driver.php?id=evbda.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

​

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

[font=lucida console]**************************Sat Jun 22 12:56:55.631 2013 (UTC - 6:00)**************************
Loading Dump File [C:\Users\writh ziden\Downloads\BSODDmpFiles\2013_06_16\writhziden\Windows7_Vista_jcgriff2\062213-8703-01.dmp]
Windows 8 Kernel Version 9200 MP (12 procs) Free x64
Built by: [B]9200[/B].16581.amd64fre.win8_gdr.130410-1505
System Uptime:[B]0 days 4:58:34.253[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!CmpKcbCacheLookup+287 )[/B]
BugCheck [B]3B, {c0000005, fffff80226262a3f, fffff8800afca690, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80226262a3f, Address of the instruction which caused the bugcheck
Arg3: fffff8800afca690, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID: [B]0x3B_nt!CmpKcbCacheLookup[/B]
CPUID:        "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: [B]3200[/B]
  BIOS Version                  F2
  BIOS Release Date             07/16/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 07:11:27.880 2013 (UTC - 6:00)**************************
Loading Dump File [C:\Users\writh ziden\Downloads\BSODDmpFiles\2013_06_16\writhziden\Windows7_Vista_jcgriff2\061613-16718-01.dmp]
Windows 8 Kernel Version 9200 MP (12 procs) Free x64
Built by: [B]9200[/B].16581.amd64fre.win8_gdr.130410-1505
System Uptime:[B]0 days 1:05:40.532[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!FsRtlLookupPerStreamContextInternal+79 )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff8024f6b01c9, fffff88003e98cc8, fffff88003e98500}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8024f6b01c9, The address that the exception occurred at
Arg3: fffff88003e98cc8, Exception Record Address
Arg4: fffff88003e98500, Context Record Address
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]AV_nt!FsRtlLookupPerStreamContextInternal[/B]
CPUID:        "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: [B]3200[/B]
  BIOS Version                  F2
  BIOS Release Date             07/16/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

Opened log file 'C:\Users\WRITHZ~1\AppData\Local\Temp\SysnativeBSODApps\18467\kdc\outkdOutput1.1.txt'

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\writh ziden\Downloads\BSODDmpFiles\2013_06_16\writhziden\Windows7_Vista_jcgriff2\062213-8703-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
Machine Name:
Kernel base = 0xfffff802`25e05000 PsLoadedModuleList = 0xfffff802`260d1a20
Debug session time: Sat Jun 22 12:56:55.631 2013 (UTC - 6:00)
System Uptime: 0 days 4:58:34.253
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80226262a3f, fffff8800afca690, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+287 )

Followup: MachineOwner
---------

8: kd> !niemiro.rawstack; q
0xfffff880`0afc9048  0xfffff880`037dfbc0 dump_diskdump!ExecuteSrb+0xfc
0xfffff880`0afc9088  0xfffff880`037dff6c dump_diskdump!DiskDumpWrite+0x190
0xfffff880`0afc90c8  0xfffff880`03bc7a00 dump_storahci!AhciGetNextIos+0x3c
0xfffff880`0afc90d0  0xfffff880`01a0a30a crashdmp!StrBeginningDump+0xa
0xfffff880`0afc9108  0xfffff880`01a05097 crashdmp!CrashdmpWriteRoutine+0x4f
0xfffff880`0afc9138  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc9148  0xfffff880`01a032dc crashdmp!WritePageSpanToDisk+0x200
0xfffff880`0afc9160  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc9180  0xfffff880`01a05048 crashdmp!CrashdmpWriteRoutine+0x0
0xfffff880`0afc9188  0xfffff880`01a0512c crashdmp!CrashdmpWritePendingRoutine+0x0
0xfffff880`0afc91a0  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc91a8  0xfffff802`25ecdb51 nt!vsnprintf+0x11
0xfffff880`0afc9278  0xfffff802`26095520 nt!NtVhdBootFile+0x15d0
0xfffff880`0afc92b8  0xfffff880`01a02e2a crashdmp!WriteBitmapDump+0x25e
0xfffff880`0afc92c0  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc92c8  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc92d0  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc9338  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc9350  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc9358  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc93f8  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc9400  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc9408  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc9428  0xfffff880`01a02985 crashdmp!DumpWrite+0x1c5
0xfffff880`0afc9430  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc9438  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc9440  0xfffff880`01a0a3e0 crashdmp!Context+0x30
0xfffff880`0afc9450  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc9468  0xfffff880`01a01a4e crashdmp!CrashdmpWrite+0x9e
0xfffff880`0afc9480  0xfffff802`260de1c0 nt!IopTriageDumpDataBlocks+0x0
0xfffff880`0afc9488  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc9498  0xfffff802`25f78347 nt!IoWriteCrashDump+0x5e3
0xfffff880`0afc94b0  0xfffff802`260d8dc0 nt!KeBugCheckAddPagesCallbackListHead+0x0
0xfffff880`0afc9510  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afc9518  0xfffff802`260d8dc0 nt!KeBugCheckAddPagesCallbackListHead+0x0
0xfffff880`0afc9528  0xfffff802`260d8dc0 nt!KeBugCheckAddPagesCallbackListHead+0x0
0xfffff880`0afc9588  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc9598  0xfffff802`25f77bb0 nt!IoSetDumpRange+0x0
0xfffff880`0afc95a0  0xfffff802`25f77b10 nt!IoFreeDumpRange+0x0
0xfffff880`0afc95b8  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afc95d8  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afc9638  0xfffff802`25f81b00 nt!KeBugCheck2+0x9c1
0xfffff880`0afc9640  0xfffff802`26098520 nt!EtwpBugCheckCallback+0x0
0xfffff880`0afc9648  0xfffff802`260d8db0 nt!KeBugCheckReasonCallbackListHead+0x0
0xfffff880`0afc9650  0xfffff802`260d8db0 nt!KeBugCheckReasonCallbackListHead+0x0
0xfffff880`0afc9678  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc96e8  0xfffff802`25f81ebc nt!KiBugCheckProgress+0x0
0xfffff880`0afc9878  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afc9890  0xfffff802`26116410 nt!KiInitialPCR <PERF> (nt+0x311410)+0x0
0xfffff880`0afc98b0  0xfffff802`25e5e453 nt!KiSystemServiceCopyEnd+0x13
0xfffff880`0afc98b8  0xfffff802`25e5f440 nt!KeBugCheckEx+0x0
0xfffff880`0afc9968  0xfffff802`25edc640 nt!MiRebalanceNode+0xb0
0xfffff880`0afc9d18  0xfffff802`25e5e453 nt!KiSystemServiceCopyEnd+0x13
0xfffff880`0afc9d58  0xfffff802`25e5f544 nt!KeBugCheckEx+0x104
0xfffff880`0afc9d98  0xfffff802`25e5e769 nt!KiBugCheckDispatch+0x69
0xfffff880`0afc9db0  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afc9ed0  0xfffff802`25e5e453 nt!KiSystemServiceCopyEnd+0x13
0xfffff880`0afc9ed8  0xfffff802`25e5e0bc nt!KiSystemServiceHandler+0x7c
0xfffff880`0afc9ee8  0xfffff802`25e3a9d6 nt!_GSHandlerCheck_SEH+0x76
0xfffff880`0afc9ef0  0xfffff802`2603be80 nt!MiAddViewsForSection+0xf4
0xfffff880`0afc9f18  0xfffff802`25ecb47d nt!RtlpExecuteHandlerForException+0xd
0xfffff880`0afc9f48  0xfffff802`25ef3364 nt!RtlDispatchException+0x458
0xfffff880`0afc9fa0  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afc9fc0  0xfffff802`26116410 nt!KiInitialPCR <PERF> (nt+0x311410)+0x0
0xfffff880`0afc9fc8  0xfffff802`2600d3f0 nt!HV_EVENTLOG_IOMMU_INIT_WARNING_BAD_ACPI_TABLE+0xc
0xfffff880`0afca000  0xfffff802`25e5e453 nt!KiSystemServiceCopyEnd+0x13
0xfffff880`0afca008  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca010  0xfffff802`26116410 nt!KiInitialPCR <PERF> (nt+0x311410)+0x0
0xfffff880`0afca030  0xfffff802`25e5e040 nt!KiSystemServiceHandler+0x0
0xfffff880`0afca038  0xfffff802`2600d3f0 nt!HV_EVENTLOG_IOMMU_INIT_WARNING_BAD_ACPI_TABLE+0xc
0xfffff880`0afca1a8  0xfffff802`2607510e nt!ExAllocatePoolWithTag+0xfe
0xfffff880`0afca1b8  0xfffff802`25e8a756 nt!RtlSetBits+0x86
0xfffff880`0afca1e8  0xfffff802`25edc640 nt!MiRebalanceNode+0xb0
0xfffff880`0afca538  0xfffff802`25e5e1c0 nt!KiSystemCall64+0x0
0xfffff880`0afca540  0xfffff802`2626515c nt!CmpBuildHashStackAndLookupCache+0x46d
0xfffff880`0afca548  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca550  0xfffff802`26135928 nt!KiInitialPCR <PERF> (nt+0x330928)+0x0
0xfffff880`0afca558  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca560  0xfffff802`261359f4 nt!KiInitialPCR <PERF> (nt+0x3309f4)+0x0
0xfffff880`0afca568  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca570  0xfffff802`26135724 nt!KiInitialPCR <PERF> (nt+0x330724)+0x0
0xfffff880`0afca578  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca580  0xfffff802`26134554 nt!KiInitialPCR <PERF> (nt+0x32f554)+0x0
0xfffff880`0afca588  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca590  0xfffff802`26134cec nt!KiInitialPCR <PERF> (nt+0x32fcec)+0x0
0xfffff880`0afca598  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca5a0  0xfffff802`2613348c nt!KiInitialPCR <PERF> (nt+0x32e48c)+0x0
0xfffff880`0afca5a8  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca5b0  0xfffff802`26133498 nt!KiInitialPCR <PERF> (nt+0x32e498)+0x0
0xfffff880`0afca5b8  0xfffff802`25e05000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`0afca5c0  0xfffff802`26116410 nt!KiInitialPCR <PERF> (nt+0x311410)+0x0
0xfffff880`0afca5c8  0xfffff802`25ecccbe nt!KiPreprocessFault+0x7e
0xfffff880`0afca5f0  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afca5f8  0xfffff802`26262a41 nt!CmpKcbCacheLookup+0x289
0xfffff880`0afca658  0xfffff802`25ecd1d6 nt!KiDispatchException+0x455
0xfffff880`0afca788  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afca7d8  0xfffff802`2607510e nt!ExAllocatePoolWithTag+0xfe
0xfffff880`0afca7e8  0xfffff802`25e8a756 nt!RtlSetBits+0x86
0xfffff880`0afca818  0xfffff802`25edc640 nt!MiRebalanceNode+0xb0
0xfffff880`0afca998  0xfffff802`2627ef43 nt!RtlpCopyAces+0x2d3
0xfffff880`0afcaab8  0xfffff802`26282ca0 nt!RtlpInheritAcl2+0x1a0
0xfffff880`0afcab28  0xfffff802`25ecb67f nt!RtlGetExtendedContextLength+0x1f
0xfffff880`0afcab38  0xfffff802`2607520a nt!ExAllocatePoolWithTag+0x1fa
0xfffff880`0afcac08  0xfffff802`2628316b nt!RtlpCombineAcls+0x18b
0xfffff880`0afcac38  0xfffff802`25ed8207 nt!RtlSidDominates+0xa3
0xfffff880`0afcac68  0xfffff802`2623c1eb nt!SeOpenObjectAuditAlarmWithTransaction+0xeb
0xfffff880`0afcad18  0xfffff802`25e5e842 nt!KiExceptionDispatch+0xc2
0xfffff880`0afcad28  0xfffff802`2623560e nt!ObpIncrementHandleCountEx+0x28e
0xfffff880`0afcad48  0xfffff802`25edecdc nt!RtlpOwnerAcesPresent+0x9c
0xfffff880`0afcae68  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afcaef8  0xfffff802`25e5cd4a nt!KiGeneralProtectionFault+0x10a
0xfffff880`0afcb028  0xfffff802`2608b000 nt!ExNode0+0x0
0xfffff880`0afcb048  0xfffff802`26563bb9 hal!HalSendSoftwareInterrupt+0x29
0xfffff880`0afcb068  0xfffff802`26262a3f nt!CmpKcbCacheLookup+0x287
0xfffff880`0afcb098  0xfffff802`25e8f0c9 nt!KiDeferredReadyThread+0x2d9
0xfffff880`0afcb178  0xfffff802`2626506d nt!CmpBuildHashStackAndLookupCache+0x37d
0xfffff880`0afcb5e8  0xfffff802`26250469 nt!CmpParseKey+0x319
0xfffff880`0afcb658  0xfffff802`2623fb01 nt!PsReferenceEffectiveToken+0x61
0xfffff880`0afcb888  0xfffff802`262377bc nt!ObReferenceObjectByHandleWithTag+0xac
0xfffff880`0afcb918  0xfffff802`26237cc5 nt!ObReferenceObjectByHandle+0x25
0xfffff880`0afcb950  0xfffff802`26250150 nt!CmpParseKey+0x0
0xfffff880`0afcb968  0xfffff802`2622e8c5 nt!ObpLookupObjectName+0x806
0xfffff880`0afcbab8  0xfffff802`2623e238 nt!ObOpenObjectByName+0x258
0xfffff880`0afcbb18  0xfffff802`25e9634f nt!MiResolveProtoPteFault+0x4cf
0xfffff880`0afcbb48  0xfffff802`2626b719 nt!CmKeyBodyRemapToVirtualForEnum+0x29
0xfffff880`0afcbb88  0xfffff802`26204540 nt!CmCreateKey+0x42e
0xfffff880`0afcbd78  0xfffff802`262047b9 nt!NtCreateKey+0x29
0xfffff880`0afcbdc8  0xfffff802`25e5e453 nt!KiSystemServiceCopyEnd+0x13
0xfffff880`0afcbe38  0xfffff802`25e5cffd nt!KiPageFault+0x27d
[B][COLOR=RED]0xfffff880`0afcbf48  0xfffff880`01761d5d Ntfs!NtfsCommonCreateCallout+0x1d[/COLOR][/B]
0xfffff880`0afcbf78  0xfffff802`25e59b27 nt!KxSwitchKernelStackCallout+0x27
quit:

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Opened log file 'C:\Users\WRITHZ~1\AppData\Local\Temp\SysnativeBSODApps\18467\kdc\outkdOutput2.1.txt'

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\writh ziden\Downloads\BSODDmpFiles\2013_06_16\writhziden\Windows7_Vista_jcgriff2\061613-16718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
Machine Name:
Kernel base = 0xfffff802`4f60b000 PsLoadedModuleList = 0xfffff802`4f8d7a20
Debug session time: Sun Jun 16 07:11:27.880 2013 (UTC - 6:00)
System Uptime: 0 days 1:05:40.532
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8024f6b01c9, fffff88003e98cc8, fffff88003e98500}

Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupPerStreamContextInternal+79 )

Followup: MachineOwner
---------

8: kd> !niemiro.rawstack; q
0xfffff880`03e98058  0xfffff802`4f6b5ec9 nt!IopFreeIrp+0x119
0xfffff880`03e98068  0xfffff802`4f6b5ec9 nt!IopFreeIrp+0x119
[B][COLOR=RED]0xfffff880`03e98198  0xfffff880`01c634fb Ntfs!NtfsInitializeIrpContext+0x12b
0xfffff880`03e981e8  0xfffff880`01c6a995 Ntfs!NtfsFsdWrite+0x3f5
0xfffff880`03e98218  0xfffff880`01ad657f fltmgr!GetContextFromStreamList+0x19c
0xfffff880`03e983a8  0xfffff802`4f6b015d nt!FsRtlLookupPerStreamContextInternal+0xd
0xfffff880`03e983b0  0xfffff880`01b08552 fltmgr!FltMgrFsRtlGetFileNameInformation+0xb2
0xfffff880`03e983b8  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e983c0  0xfffff802`4f91f104 nt!KiInitialPCR <PERF> (nt+0x314104)+0x0
0xfffff880`03e983c8  0xfffff880`01ad2000 fltmgr!FltpGetNormalizedFileNameCallout <PERF> (fltmgr+0x0)+0x0
0xfffff880`03e983d0  0xfffff880`01afa168 fltmgr!__PchSym_ <PERF> (fltmgr+0x28168)+0x0
0xfffff880`03e983d8  0xfffff880`01ad2000 fltmgr!FltpGetNormalizedFileNameCallout <PERF> (fltmgr+0x0)+0x0
0xfffff880`03e983e0  0xfffff880`01afa300 fltmgr!__PchSym_ <PERF> (fltmgr+0x28300)+0x0
0xfffff880`03e983e8  0xfffff880`01ad2000 fltmgr!FltpGetNormalizedFileNameCallout <PERF> (fltmgr+0x0)+0x0
0xfffff880`03e983f0  0xfffff880`01afc10c fltmgr!__PchSym_ <PERF> (fltmgr+0x2a10c)+0x0[/COLOR][/B]
0xfffff880`03e983f8  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e98400  0xfffff802`4f9409b0 nt!KiInitialPCR <PERF> (nt+0x3359b0)+0x0
0xfffff880`03e98408  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e98410  0xfffff802`4f93f918 nt!KiInitialPCR <PERF> (nt+0x334918)+0x0
0xfffff880`03e98418  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e98420  0xfffff802`4f93f8d0 nt!KiInitialPCR <PERF> (nt+0x3348d0)+0x0
0xfffff880`03e98428  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e98430  0xfffff802`4f93f90c nt!KiInitialPCR <PERF> (nt+0x33490c)+0x0
0xfffff880`03e98438  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e98440  0xfffff802`4f93f8e8 nt!KiInitialPCR <PERF> (nt+0x3348e8)+0x0
0xfffff880`03e98448  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e98450  0xfffff802`4f93f8f4 nt!KiInitialPCR <PERF> (nt+0x3348f4)+0x0
0xfffff880`03e98458  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e98460  0xfffff802`4f93f8dc nt!KiInitialPCR <PERF> (nt+0x3348dc)+0x0
0xfffff880`03e98468  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e98470  0xfffff802`4f938c88 nt!KiInitialPCR <PERF> (nt+0x32dc88)+0x0
0xfffff880`03e984c8  0xfffff802`4f6d31d6 nt!KiDispatchException+0x455
0xfffff880`03e98558  0xfffff802`4fa6ecdd nt!IopQueryNameInternal+0x15d
0xfffff880`03e985f8  0xfffff802`4f6b01c9 nt!FsRtlLookupPerStreamContextInternal+0x79
0xfffff880`03e98608  0xfffff802`4fa88ca0 nt!RtlpInheritAcl2+0x1a0
0xfffff880`03e98688  0xfffff802`4f6b5ec9 nt!IopFreeIrp+0x119
0xfffff880`03e98698  0xfffff802`4f6b5ec9 nt!IopFreeIrp+0x119
0xfffff880`03e987a8  0xfffff802`4f6da6cf nt!KiDeliverApc+0x15f
0xfffff880`03e98828  0xfffff802`4f6978a5 nt!IopfCompleteRequest+0xe05
[B][COLOR=RED]0xfffff880`03e988b8  0xfffff880`01c62c89 Ntfs!NtfsCleanupIrpContext+0x149
0xfffff880`03e98908  0xfffff880`01c63203 Ntfs!NtfsExtendedCompleteRequestInternal+0x113
0xfffff880`03e98948  0xfffff880`01d13510 Ntfs!NtfsCommonQueryInformation+0xe07
0xfffff880`03e98998  0xfffff802`4f6d167f nt!RtlGetExtendedContextLength+0x1f
0xfffff880`03e98a28  0xfffff880`01d18632 Ntfs!NtfsFsdDispatchSwitch+0x232
0xfffff880`03e98aa8  0xfffff880`01d13646 Ntfs!NtfsFsdDispatchWait+0x57
0xfffff880`03e98b88  0xfffff802`4f664842 nt!KiExceptionDispatch+0xc2
0xfffff880`03e98cd8  0xfffff802`4f6b01c9 nt!FsRtlLookupPerStreamContextInternal+0x79
0xfffff880`03e98d18  0xfffff880`01ad32e9 fltmgr!FltpPassThrough+0x169
0xfffff880`03e98d68  0xfffff802`4f662d4a nt!KiGeneralProtectionFault+0x10a
0xfffff880`03e98d78  0xfffff880`01ad30b6 fltmgr!FltpDispatch+0xb6
0xfffff880`03e98dd8  0xfffff802`4fa83c9b nt!IopGetFileInformation+0xdb
0xfffff880`03e98e58  0xfffff802`4fa6ecdd nt!IopQueryNameInternal+0x15d
0xfffff880`03e98ed8  0xfffff802`4f6b01c9 nt!FsRtlLookupPerStreamContextInternal+0x79
0xfffff880`03e98f08  0xfffff802`4fd73e3b hal!KeQueryPerformanceCounter+0x4b
0xfffff880`03e98f38  0xfffff880`01ad5d12 fltmgr!FltpGetStreamListCtrl+0x62
0xfffff880`03e98f40  0xfffff880`01af7010 fltmgr!WPP_GLOBAL_Control+0x0
0xfffff880`03e98fa8  0xfffff880`01ad7e8e fltmgr!FltpGetFileNameInformation+0x22e
0xfffff880`03e98fc8  0xfffff880`01ad8cbc fltmgr!FltpAllocateInitializeNameGenerationContext+0x13c
0xfffff880`03e99028  0xfffff880`01b08534 fltmgr!FltMgrFsRtlGetFileNameInformation+0x94[/COLOR][/B]
0xfffff880`03e99098  0xfffff802`4fae94d2 nt!EtwpEnumerateAddressSpace+0x13a
0xfffff880`03e99118  0xfffff802`4fa9337f nt!PsGetNextProcessThread+0xd3
0xfffff880`03e99138  0xfffff802`4fad1a2f nt!EtwpThreadEnumCallback+0x2b
0xfffff880`03e99148  0xfffff802`4fad1a04 nt!EtwpThreadEnumCallback+0x0
0xfffff880`03e99190  0xfffff802`4fad1b01 nt!EtwpProcessThreadImageRundown+0xb5
0xfffff880`03e99198  0xfffff802`4fad1c69 nt!EtwpProcessEnumCallback+0x109
0xfffff880`03e991a8  0xfffff802`4fad1b01 nt!EtwpProcessThreadImageRundown+0xb5
0xfffff880`03e991c8  0xfffff802`4fad1cc7 nt!EtwpProcessEnumCallback+0x167
0xfffff880`03e991e0  0xfffff802`4f95d200 nt!KiInitialProcess+0x0
0xfffff880`03e99230  0xfffff802`4fad1b60 nt!EtwpProcessEnumCallback+0x0
0xfffff880`03e99238  0xfffff802`4fad14c5 nt!PsEnumProcesses+0x31
0xfffff880`03e99248  0xfffff802`4fad1b60 nt!EtwpProcessEnumCallback+0x0
0xfffff880`03e99268  0xfffff802`4fad1b14 nt!EtwpProcessThreadImageRundown+0xc8
0xfffff880`03e992d8  0xfffff802`4fad16e6 nt!EtwpKernelTraceRundown+0x146
0xfffff880`03e99308  0xfffff802`4fad2c7d nt!EtwpLogGroupMask+0x79
0xfffff880`03e99368  0xfffff802`4f89eb20 nt!EtwpGroupMasks+0x20
0xfffff880`03e99388  0xfffff802`4fad190b nt!EtwpUpdateGroupMasks+0x167
0xfffff880`03e99410  0xfffff802`4f89ed80 nt!WmipLoggerContext+0x0
0xfffff880`03e99428  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e99438  0xfffff802`4fad156b nt!EtwpUpdateLoggerGroupMasks+0x7b
0xfffff880`03e99488  0xfffff802`4f60b000 nt!`string' <PERF> (nt+0x0)+0x0
0xfffff880`03e99498  0xfffff802`4f9fca30 nt!EtwpStartLogger+0x8b0
0xfffff880`03e994c8  0xfffff802`4faaec90 nt!EtwpLogger+0x0
0xfffff880`03e994d8  0xfffff802`4f9e8f66 nt!RtlpQueryRegistryValues+0x1e2
0xfffff880`03e99520  0xfffff802`4fa20101 nt!FsRtlKernelFsControlFile+0x2e25
0xfffff880`03e995a8  0xfffff802`4fb32be0 nt!EtwpStartAutoLogger+0x6cc
0xfffff880`03e995c0  0xfffff802`4f8a24ce nt!PerfDiagGlobals+0x2e
0xfffff880`03e995c8  0xfffff802`4fa62332 nt! ?? ::NNGAKEGL::`string'+0x2
0xfffff880`03e99668  0xfffff802`4f8a24cc nt!PerfDiagGlobals+0x2c
0xfffff880`03e996d0  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e996e0  0xfffff802`4fa62120 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99708  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99718  0xfffff802`4fa62140 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99740  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99750  0xfffff802`4fa62160 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99778  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99788  0xfffff802`4fa62180 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e997b0  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e997c0  0xfffff802`4fa621a0 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e997e8  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e997f8  0xfffff802`4fa621c0 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99820  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99830  0xfffff802`4fa61570 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99858  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99868  0xfffff802`4fa621e0 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99890  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e998a0  0xfffff802`4fa62210 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e998c8  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e998d8  0xfffff802`4fa62230 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99900  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99910  0xfffff802`4fa62250 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99938  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99948  0xfffff802`4fa62270 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99970  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99980  0xfffff802`4fa622b0 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e999a8  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e999b8  0xfffff802`4fa622c0 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e999e0  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e999f0  0xfffff802`4fa622e0 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99a18  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99a28  0xfffff802`4fa622f0 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99a50  0xfffff802`4fb3245c nt!EtwpQueryRegistryCallback+0x0
0xfffff880`03e99a60  0xfffff802`4fa62310 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99ac8  0xfffff802`4fa61730 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99ad0  0xfffff802`4f891000 nt!ExNode0+0x0
0xfffff880`03e99ae8  0xfffff802`4f66ecbc nt!ExpBuiltinPriorities+0x4
0xfffff880`03e99af0  0xfffff802`4fa61610 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99b08  0xfffff802`4fb32d9b nt!PerfDiagpRestartCKCL+0x67
0xfffff880`03e99b18  0xfffff802`4fa61610 nt! ?? ::NNGAKEGL::`string'+0x0
0xfffff880`03e99b38  0xfffff802`4fb32187 nt!PerfDiagpProxyWorker+0x137
0xfffff880`03e99b70  0xfffff802`4f891110 nt!ExNode0+0x110
0xfffff880`03e99b78  0xfffff802`4f6a32b1 nt!ExpWorkerThread+0x142
0xfffff880`03e99b90  0xfffff802`4fb32050 nt!PerfDiagpProxyWorker+0x0
0xfffff880`03e99bc8  0xfffff802`4f6b5ec9 nt!IopFreeIrp+0x119
0xfffff880`03e99bf8  0xfffff802`4f95d880 nt!KiInitialThread+0x0
0xfffff880`03e99c08  0xfffff802`4f638045 nt!PspSystemThreadStartup+0x59
0xfffff880`03e99c20  0xfffff802`4f6a3170 nt!ExpWorkerThread+0x0
0xfffff880`03e99c58  0xfffff802`4f6ec766 nt!KiStartSystemThread+0x16
0xfffff880`03e99c60  0xfffff802`4f903180 nt!KiInitialPCR+0x180
0xfffff880`03e99c70  0xfffff802`4f95d880 nt!KiInitialThread+0x0
quit:

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[writhziden]

Alright, crashes are now pointing to hardware with memory conflicts as the prime suspect. Memtest86+ comes back clean, so I'm now wondering if I need to purchase RAM from the QVL. I'd prefer not to have to buy a second set of RAM as that is nearly $500 I've shelled out for RAM alone...

BugChecks include 0x50 and 0x109, which are most commonly linked through faulty/incompatible RAM.

I also had a strange occurrence the other day: The system would not turn on from sleep mode. I had to push the PSU switch to off, wait 5 seconds, and push it back to on before the system would boot. Given the sleep state, this could still mean RAM is the issue, but I can't rule out a bad PSU as a possibility, as well.

Thoughts?


EDIT: I have included my BSOD collection files for anyone who would like to analyze further.

EDIT2: BIOS voltages:

• 12.096 V
• 5.010 V
• 3.42 V

 

[Digerati]

Well, those voltages are well within tolerances, but not conclusive. There could be too much ripple or problems running under load. If you suspect it may be a PSU issue (or not convinced your current PSU is not the problem) I would swap in a known good PSU - at least for a few days to see how it goes.

I agree the problem coming out of sleep could be a RAM issue, but a simple power anomaly during sleep can cause that too. If it happens again soon, I would be suspicious. If not, then just a fluke.

As for RAM and the QVL, you MUST buy RAM that matches the specs of tested/listed RAM, but there are just too many brands and models within brands for motherboard makers to test them all. So you should not have to buy listed RAM (in fact, I rarely do). CPUs are another story. You should buy a listed CPU as it is easy for motherboard makers to test the limited number of CPUs the specific board, chipset, and socket supports.

The problem with all software based memory testers is they really are not conclusive either. If they report RAM errors, the RAM is bad. But they don't always identify bad RAM as bad, so you can run MemTest or (and) Windows Memory Diagnostics Tool and not find errors, but still have memory problems.

So before buying new RAM, I recommend running with one RAM stick at a time and see what happens. I have seen where each stick runs great solo, but refuses to play well when additional RAM is installed.

Or, if you have a spare $1500 laying around, you can get a real memory tester and be certain.

 

[Wrench97]

Another thing to keep in mind, the newer Intel CPU's have the memory controller on the CPU not the motherboard chip set as in the past.
I have seen setups with aftermarket coolers mounted uneven causing more pressure on one side of the socket effectively lifting the contacts on the other and causing what appeared to be ram issues but was actually a CPU/Socket contact issue.

 

[writhziden]

Well, those voltages are well within tolerances, but not conclusive. There could be too much ripple or problems running under load. If you suspect it may be a PSU issue (or not convinced your current PSU is not the problem) I would swap in a known good PSU - at least for a few days to see how it goes.

I agree the problem coming out of sleep could be a RAM issue, but a simple power anomaly during sleep can cause that too. If it happens again soon, I would be suspicious. If not, then just a fluke.

First time it has happened, and nothing again so far. I'll be monitoring. I do not currently have a spare PSU rated for testing, but there is a nearby shop that I could take it to for a quick test if needed and hopefully a reasonable price for testing.

As for RAM and the QVL, you MUST buy RAM that matches the specs of tested/listed RAM, but there are just too many brands and models within brands for motherboard makers to test them all. So you should not have to buy listed RAM (in fact, I rarely do). CPUs are another story. You should buy a listed CPU as it is easy for motherboard makers to test the limited number of CPUs the specific board, chipset, and socket supports.

Agreed on both, and the CPU is listed as supported, so that is not an issue. I have read reviews about this board having some finicky issues with certain RAM, specifically Corsair, but whether those reviews are accurate is difficult to know. It really depends on the knowhow of the users making those claims.

The problem with all software based memory testers is they really are not conclusive either. If they report RAM errors, the RAM is bad. But they don't always identify bad RAM as bad, so you can run MemTest or (and) Windows Memory Diagnostics Tool and not find errors, but still have memory problems.

So before buying new RAM, I recommend running with one RAM stick at a time and see what happens. I have seen where each stick runs great solo, but refuses to play well when additional RAM is installed.

That was along the lines of what I was thinking. I plan on re-applying my thermal compound this weekend and will try testing two modules at a time to see how the system behaves.

Or, if you have a spare $1500 laying around, you can get a real memory tester and be certain.

Hardy har har. I wish I had that much money just laying around.

Another thing to keep in mind, the newer Intel CPU's have the memory controller on the CPU not the motherboard chip set as in the past.
I have seen setups with aftermarket coolers mounted uneven causing more pressure on one side of the socket effectively lifting the contacts on the other and causing what appeared to be ram issues but was actually a CPU/Socket contact issue.

I actually read this from one of your posts at TSF, so I was aware of this going into building. I initially assembled the heatsink mounts incorrectly and had the problem you describe, so I took it apart and was more careful. The system was never turned on with the uneven contacts, and no pins were bent in the process that I can see, so I think it's good there. I'll double check this weekend when I re-apply the thermal compound, though.

One issue I am having is I cannot get the heatsink to mount tightly to the CPU. No matter how well I assemble it and follow the directions, it feels too loose to me. Screws are as tight as I am comfortable having them without risk of damaging the board, so I'm at a loss as to how to rectify this. I'm strongly considering taking the whole thing to the nearby shop and see if they can give me any advice as to what I might be doing wrong.

The last PC I built was a Pentium 4, so the mounts were snap-fit and securely attached to the fan leaving less chance of making mistakes. Of course, they were also a pain to snap into place and remove, if need be, later. I see pros and cons to both options.

 

[Digerati]

I have read reviews about this board having some finicky issues with certain RAM, specifically Corsair, but whether those reviews are accurate is difficult to know. It really depends on the knowhow of the users making those claims.

FTR, I don't pay much attention to "user reviews". For one, happy people don't complain and rarely write reviews. Most reviews at retail outlets are solicited, and received at, or near time of purchase. I like to live with a product for a couple weeks before writing reviews. And finally, a proper review should be done in a controlled environment by experienced users/technicians/reviewers, using proper test equipment - AND with competing models to use as comparisons. Otherwise, it is mostly just personal opinion - like my Ford F150 is better than your Chevy or RAM - although that fact is clearly true!

If, however, there are many user reviews that complain about the exact same thing suggesting a trend, I will likely pay attention to that.

I have heard about some issues with Corsair RAM too. But Corsair is one of the biggest RAM makers so to me, it seems logical there would be examples of problems. But I do not believe they have a higher percentage of failures than Crucial, Mushkin, Kingston or other name brands.

I also think it important to note that it is almost, if not completely impossible to find RAM that is not warrantied for life. Until Man can create perfection 100% of time, there will always be some samples that fail, but chances are if RAM is bad, it is because the user was careless with ESD (or forgot to unplug from the wall while inserting/removing), or there is a problem with the memory controller (perhaps fixed by a BIOS update).

 

[writhziden]

I am first going to try replacing my 2007 USB TV Tuner (with 2007 drivers) with a PCI-E tuner card that has Windows 8 drivers.

I had no issues running the old USB tuner on my HP with Windows 8, but I have noticed the new system periodically loses the tuner connection, so it is a possible cause for the blue screen crashes. Not likely, but I'd prefer a PCI-E card to the USB to free up two USB ports anyway, so I'm willing to upgrade whether it fixes my problems or not.

Interestingly, sometimes with the USB tuner installed, my system will take an extra 30-45 seconds before it recognizes any USB devices. I am unable to login during that window due to having a USB keyboard and mouse unless I unplug the tuner and plug it back in. With that type of behavior, it does make me suspect it as a possible cause of my crashes. Again, not a prime suspect, but still worth looking into.

 

[writhziden]

Blue screen still occurred this past weekend with the new TV tuner. I think RAM is the next step, so I'll remove a stick this week and see how the system behaves for a while.

 

[Digerati]

But it went 3 weeks without a BSOD?

 

[writhziden]

Two and a half weeks, but still in line with your question is a fairly long period of time. This is a very minor annoyance; it occurs once every 2-4 weeks so far (minus one time that it occurred within a few days of each other).

There have been 6-7 blue screens so far, and only two occurred when I was actively doing something on the system. The others occurred during sleep cycles or scheduled tasks from Windows/Windows Media Center.

Given that this happens so infrequently, the only thing that really makes sense is a bad RAM module or slot, or at least that is my current hypothesis. With 24 GB of RAM, the likelihood of data being written/read from the bad blocks on a module would be pretty small, so an infrequent crash is not beyond the scope of that hypothesis.

 

[Digerati]

This is a very minor annoyance

Maybe a minor annoyance now, but potentially much more than that. With a bit a bad timing/bad luck, a sudden crash could result in data loss, or a corrupt boot drive.

Given that this happens so infrequently, the only thing that really makes sense is a bad RAM module or slot, or at least that is my current hypothesis.With 24 GB of RAM...

I agree. I would try running with one stick at a time and see what happens.

Corsair Enthusiast Series 650-Watt 80 Plus Bronze Certified Power Supply Compatible with Core i3, i5, i7 and platforms - TX650 - Tested on old system and works fine

Does the old system have a PSU you can put in this system? How long did you run this PSU on your old system?

It doesn't appear your PSU is bad, but then again, with everything working fine for 2 1/2 weeks at a time, eliminating suspects will be difficult. I would still want to try a different PSU in this system - to conclusively eliminate this Corsair as the culprit.

What is your PSU plugged into? Ideally, a "good" UPS with AVR (surge and spike protectors are little more than fancy and expensive extension cords - so IMO, ALL computers should be on a "good" UPS with AVR - but that's for another discussion). If using a S&S protector, try a different one. And if you have not done so already, make sure you wall outlet is properly wired. Everyone should also have access to a AC Outlet Tester. I recommend one with a GFCI (ground fault circuit interrupt) indicator as it can be used to test bathroom and kitchen outlets too. These testers can be found for your type and voltage outlet, foreign or domestic, at most home improvement stores, or even the electrical department at Walmart.

Finally, you might want to contact Gigabyte and tell them of your problems - and to get on record with them for possible warranty replacement of the mobo. They may have or may create a beta BIOS update for you (if you are willing to mess with beta testing). I am sure they don't have a lot of users running with that much RAM.

As I mentioned before, Gigabyte is my preferred brand of motherboards - but they have not been 100% trouble-free. But for me, after-purchase support says a lot about a company Gigabyte, and has always been good to me there. In fact, a few years ago when leaky capacitors plagued motherboards, Gigabyte replaced for free a 3 1/2 old motherboard (6 months after the warranty expired) - that made me a loyal Gigabyte owner.