[SOLVED] Frequent BSOD despite reinstalling Windows multiple times - Windows 8.1

Thunderproof · Mar 16, 2014

I recently upgraded my motherboard, processor and video card due to constant blue screens (at least 3-5 a day). Upon changing these parts, I re installed Windows 8.1 (64 bit) and updated all necessary drivers directly from the appropriate manufacturers website.

Unfortunately I still received blue screens even after the fresh install, so I began searching the internet for answers, reading through hundreds of threads, analyzing my dump files, finding out where driver files came from and trying to uninstall or update as necessary. I contacted Microsoft directly and after 2+ hours they couldn't find the problem so I posted on the Microsoft forums. The person that responded was somewhat helpful but I don't think he was aware of all that I had done and so he gave me the usual routine of things to check/do.

Eventually after countless more blue screens I just decided to re install Windows 8.1 AGAIN. Sure enough, more blue screens with only the Nvidia video card driver installed. It doesn't matter what I'm doing or the length of time. The crashes are completely random and give completely different stop codes every time.

The one thing that hasn't changed throughout all my hardware iterations is my 4 year old Corsair 650 watt power supply. It has served me well as *seems* to work fine as it may take hours to crash sometimes. My computer specs are as follows:

Biostar Hi Fi Z87x motherboard
Intel i7-4770K (NOT overclocked right now)
PNY GTX 760
Corsair 650W PSU
GSkill RipJaw 8Gb
Adata SSD boot drive
500Gb HDD

So far I have done the following:

Call Microsoft tech support and they spent almost 2 hours trying to figure it out with no success
I've updated all drivers that my mind can fathom, including re installing potentially troublesome ones
I've run Memtest multiple times for over 6 hours and 6 passes
I've run a video card Memtest on my new video RAM
I've done sfc /scannow (multiple times) with no errors
I've done chkdsk (multiple times) with no errors
I use the windows debugger to troubleshoot along with BlueScreenView
I've used driver verifier as suggested which doesn't seem to crash the system any differently than normal

If you need any more information just let me know! Thanks!
View attachment 7407

Thunderproof · Mar 16, 2014

Also, here is a link to my 4 most recent BSODs since my last windows reinstall. I also have many of the old ones from a previous install with different drivers and what not if that would be helpful to compare to. I'm becoming more and more convinced that my power supply is at fault due to the extremely unstable nature of these crashes. (varying frequency, varying cause, varying length of time, varying application). I hope its software related but with what little software I currently have installed it just doesn't seem likely. Additionally, my power supply is the only thing (I think) that hasn't changed throughout all the hardware/software iterations I have gone through recently. Hopefully we can get to the bottom of this!

https://onedrive.live.com/redir?res...1&authkey=!AAJfL34rrx4xXSk&ithint=folder,.dmp

Patrick · Mar 16, 2014

Hi,

Thanks for making a thread here after contacting me via email, much appreciated.

Right, so all of the four recent DMP files are of different bug checks:

KMODE_EXCEPTION_NOT_HANDLED (1e)

This indicates that a kernel-mode program generated an exception which the error handler did not catch.

-- DEFAULT_BUCKET_ID: CODE_CORRUPTION

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8032595412c - nt!EnlightenedSwapContext_PatchXSave+2
    [ 01:31 ]
    fffff803259541a8-fffff803259541a9  2 bytes - nt!EnlightenedSwapContext_PatchLdt (+0x7c)
    [ 48 0f:eb 42 ]
    fffff8032595422e - nt!EnlightenedSwapContext_PatchXRstor+2 (+0x86)
    [ 09:29 ]
4 errors : !nt (fffff8032595412c-fffff8032595422e)

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

MEMORY_MANAGEMENT (1a)

This indicates that a severe memory management error occurred.

BugCheck 1A, {411, fffff6e000018ab0, 98e000010778f882, fbeff6e000018ab1}

^^ The 1st parameter of the bug check is 411 which indicates a page table entry (PTE) has been corrupted.

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

^^ VRF enabled, however we have no driver found making invalid function calls, etc.

KERNEL_SECURITY_CHECK_FAILURE (139)

This bug check indicates that the kernel has detected the corruption of a critical data structure.

BugCheck 139, {3, ffffd000287b0a80, ffffd000287b09d8, 0}

The 1st parameter of the bugcheck is 3 which indicates that a LIST_ENTRY was corrupted. Code 3, LIST_ENTRY corruption. This type of bug check can be difficult to track down and indicates that an inconsistency has been introduced into a doubly-linked list (detected when an individual list entry element is added to or removed from the list).

SYSTEM_PTE_MISUSE (da)

This indicates that a page table entry (PTE) routine has been used in an improper way.

Right away this is 99.9% a hardware error, just by looking at what we have here. VRF not detecting any drivers, and the loaded modules list is clean as a whistle.

1. Uninstall your video card drivers, and then physically remove your video card. After you've done this, use integrated graphics if available and its latest drivers, or a secondary video card and its latest drivers.

2. If #1 fails, run with 1 DIMM at a time in different DIMM slots to ensure we don't have faulty DIMM slots.

We'll start with that for now.

Regards,

Patrick

Thunderproof · Mar 16, 2014

Removed the video card. Running on integrated graphics for now. Fingers crossed it was the video card, it would make for an easy return. I'll report back with any new details. Thanks for you help so far!

Patrick · Mar 16, 2014

My pleasure, keep me updated!

Regards,

Patrick

Thunderproof · Mar 16, 2014

Well, it sure didn't take long to crash after uninstalling the video card drivers and removing the video card! I added the dump file to the shared folder.

Patrick · Mar 16, 2014

Can you directly link me just so I don't end up downloading the wrong one, please?

Regards,

Patrick

Thunderproof · Mar 16, 2014

Here you go. When I add new ones, I move the previous ones to the folder but it may not have updated yet. Also, I'm really not thinking RAM is an issue but if I must I'll be willing to test again. I've run Memtest quite a few times with no errors (I previously had errors and got new sticks from the manufacturer). Hope this helps!

https://onedrive.live.com/redir?res...638&authkey=!ANAjgh6oGo5lPTc&ithint=file,.dmp

Patrick · Mar 16, 2014

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This indicates that a system thread generated an exception which the error handler did not catch.

BugCheck 1000007E, {ffffffffc0000005, fffff8016a4462a8, ffffd000209b0508, ffffd000209afd10}

^^ The 1st parameter of the bug check is c0000005 which indicates an access violation occurred:

Code:

4: kd> .exr 0xffffd000209b0508
ExceptionAddress: fffff8016a4462a8 (nt!FsFilterPerformCallbacks+0x0000000000000264)
   ExceptionCode: c0000005 (Access violation)

^^ The violation occurred in nt!FsFilterPerformCallbacks.

-- FAILURE_BUCKET_ID: X64_0x7E_VRF_nt!FsFilterPerformCallbacks+264

^^ Verifier enabled yet again.

Let's do as I said here now (even if Memtest passes with all sticks installed for at least ~8 passes):

2. If #1 fails, run with 1 DIMM at a time in different DIMM slots to ensure we don't have faulty DIMM slots.

Regards,

Patrick

Thunderproof · Mar 17, 2014

Is it fine if I go ahead and plug my video card back in and reinstall the drivers?

Patrick · Mar 17, 2014

Yes, go ahead! Your GPU doesn't appear to be the problem as we're still crashing on integrated.

Regards,

Patrick

Thunderproof · Mar 17, 2014

So I plan on testing the RAM tomorrow and it should be a lengthy process. In the meantime I swapped my power supply with my roommates identical one and I'm running with it right now. All is well so far, and I'm trying to "break" it as best as possible through multitasking and some light gaming. I'll report back with results. I'm keeping my fingers crossed that its the power supply as it's still under warranty so I could get a brand new one after 4 years :)

Patrick · Mar 17, 2014

Great, keep me updated.

Right, so that was my next recommendation (PSU). If PSU turned out to be okay, it is likely a faulty motherboard.

Regards,

Patrick

Thunderproof · Mar 17, 2014

Just had another blue screen

At this point I don't know if I really need to post anymore logs. This one said hardware was at fault after running the debugger. I'll go through the RAM now and report back.

Patrick · Mar 17, 2014

With the RAM, so we're absolutely sure, as annoying as it will be, patience and doing it properly will give us the best results.

Here's what I would do:

1. Clear the CMOS so we're 100% sure there's no improper BIOS setting(s), such as a DRAM timer being incorrect, or unstable.

2. After that, use the system.

3. If you crash, run Memtest with all sticks installed in their proper slots for NO LESS than ~8 passes.

4. If you pass, remove all sticks and run on 1 stick. If you crash, remove move the stick to a different slot. If you crash again, repeat. Do this with all sticks/all slots.

Regards,

Patrick

Thunderproof · Mar 17, 2014

It appears I have figured out the issue. After not being convinced it could be anything other than the RAM I sought to figure out what could be wrong other than "bad RAM". The instability that I have been having was extremely similar to what I had with true bad RAM that showed errors almost immediately on Memtest. Well, after researching my RAM it would appear that running it at 1600MHz (alleged stock speed) caused the instability. I don't know if it was an issue with dual channel compatibility, the memory controller or physical limitations of the RAM itself but all I know is that many other people have had trouble with this same RAM. The almost universal fix seems to be either to increase the voltage from 1.5 V to 1.6 V or to lower the frequency to 1333MHz. I opted to avoid messing with the voltages as that could cause its own set of issues. This is a very subtle issue and one that is hard to find or reproduce as Memtest shows no signs of issues. I'll probably avoid RMAing the RAM if it truly is a universal issue and be content with the lower speeds (so long as everything stays stable).

Thanks for your help! It got me thinking about the RAM. Ultimately I was too impatient to want to test each stick so thoroughly but I knew it was most likely the RAM. I'll mark this thread as solved as soon as I'm fully convinced it is 100% stable. At this point, 8 hours is more than double as long as I've gone without a crash in 2 weeks so I'm taking little wins as I go. I'll report back with any new issues or with a solved indication. Thanks again!

Patrick · Mar 17, 2014

Great, very glad to hear.

If it's of any consolation, my RAM isn't stable at 1600MHz at factory advised timings/voltage either.

Regards,

Patrick

Thunderproof · Mar 20, 2014

Thanks again! Everything seems stable and working well!

Patrick · Mar 20, 2014

My pleasure!

Great to hear, thanks a lot for the update.

Regards,

Patrick

[SOLVED] Frequent BSOD despite reinstalling Windows multiple times - Windows 8.1

Member

Member

Sysnative Staff

Member

Sysnative Staff

Member

Sysnative Staff

Member

Sysnative Staff

Member

Sysnative Staff

Member

Sysnative Staff

Member

Sysnative Staff

Member

Sysnative Staff

Member

Sysnative Staff