BSOD Windows 8.1

Hello,

I recently completed a system rebuild, and I'm getting intermittent BSODs in Windows 8.1. I've been saving the dump files, and am seeing at least three different errors. Here are the corresponding dumps:

==================================================
Dump File         : 040215-8109-01.dmp
Crash Time        : 2015-04-02 5:34:59 AM
Bug Check String  : NTFS_FILE_SYSTEM
Bug Check Code    : 0x00000024
Parameter 1       : 000000b5`00190645
Parameter 2       : ffffd000`a75b6e58
Parameter 3       : ffffd000`a75b6660
Parameter 4       : fffff800`e5ab913e
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+31eec
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+1509a0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\040215-8109-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 300,775
Dump File Time    : 2015-04-02 5:38:04 AM
==================================================

==================================================
Dump File         : 032415-10640-01.dmp
Crash Time        : 2015-03-24 10:54:27 AM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff802`a36e402c
Parameter 3       : ffffd000`25e46d80
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1509a0
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+1509a0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\032415-10640-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 293,659
Dump File Time    : 2015-03-24 10:55:19 AM
==================================================

==================================================
Dump File         : 032515-12250-01.dmp
Crash Time        : 2015-03-25 1:14:37 PM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff801`4fc4913e
Parameter 3       : ffffd001`8e15a7b8
Parameter 4       : ffffd001`8e159fc0
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3713e
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+3713e
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\032515-12250-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 294,171
Dump File Time    : 2015-03-25 1:16:04 PM
==================================================

Specs:

Case: Corsair Obsidian 750D
Motherboard: ASUS M5A99FX Pro R2.0 (SLI-enabled)
PSU: Corsair HX1000i (Meets / exceeds mobo OEM power requirements for SLI)
SSD: ADATA SX900
CPU: AMD FX 8350
RAM: 32 GB Corsair Vengeance DDR3
GPU: ASUS Strix OC Nvidia GTX 980 (2-WAY SLI)Report.txt
Monitors: 3x ASUS VG248 (Using Display Port with vendor drivers installed). A 50" Panasonic Plasma TV is also connected, via HDMI
Mouse: Razer Taipan
Keyboard: Razer Blackwidow
OS: Windows 8.1

For comprehensive system information, I've attached an Aida64 report.

None of these seem to really find anything, but here's what I've tried:

-SFC: Pass
-CHKDSK / ADATA SDD scan: No serious issues found
-Memtest: Pass
-Updated all drivers, including AMD mobo chipset and BIOS
-Diagnostic reboots with all non-MS services disabled

Major Symptom: Bizarre Nvidia GPU Driver Issues

The active drivers seem to randomly change / disappear. For example, right now, the only thing showing in my Nvidia Control Panel is the stereoscopic 3D setup. If I do a clean install and reboot, I might get all settings in the Nvidia Control Panel, or I might see everything EXCEPT for the SLI configuration menu. Then, if I reboot again, the Nvidia Control might revert to just showing the stereoscopic 3D settings.

Overall Observation:

The system will work fine for several days, then I'll get a cluster of BSODs, then fine again with no action from me.

Question:

What's going on here? Your insights will be very much appreciated.
LVL 2
Bradley DorranceHelp Desk AnalystAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
The first error is for an NTFS disk corruption.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557433(v=vs.85).aspx

It also mentions a pool memory problem which is the subject of the second message.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

The third message implicates memory and possibly drivers.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff559239(v=vs.85).aspx

I would read through the third message, run memtest86, and update all the drivers on your system. Then run chkdsk to see if you have any data errors and also your vendor's hard drive diagnostics to check for hard drive health.
Bradley DorranceHelp Desk AnalystAuthor Commented:
Thank you, John, for your reply.

What's puzzling in all of this is:

1. The system has passed Memtest86, Windows Memory Test etc. with flying colours.
2. Neither CHKDSK nor the ADATA SSD test turned up much of anything.

I'll run some more tests and post some results later.

Regards,
Brad
Natty GregIn Theory (IT)Commented:
format the disk and start over, in bios change ide to achi if you haven't done so already
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

nobusCommented:
what was the reason for the system rebuild?
if it was bad hardware - a rebuild won't help

since you've ran Ram and disk test - it could be the motherboard or video card -or PS
sinc e you have a geforce card, that uses a lot of power - so what PS do you have?
power needed     http://www.geforce.com/hardware/desktop-gpus/geforce-gtx-980/specifications

anayhow - i would start by :

-disconnecting all device not needed
-swapping out parts like   disk PS ram
JohnBusiness Consultant (Owner)Commented:
I would check all the drivers first, particularly BIOS, Chipset and Video to see if new drivers are available.

If that does not solve the issue, then I would also look at backing up and reinstall Windows 8.1. Are you sure the motherboard is Windows 8 certified?
Bradley DorranceHelp Desk AnalystAuthor Commented:
Thank you, everyone, for your interest in this issue. I'll try to answer your suggestions in order:

1. I haven't nuked and paved the SSD yet, but the motherboard BIOS is already set to ACHI.
2. The rebuild was intended to address performance issues in graphics-intensive applications. The only components that are not brand new are the CPU and SSD. As noted above, the PSU is a Corsair HX 1000i. The GPUs and motherboard are both ASUS; the PSU meets / exceeds their power requirements, as stated in the motherboard user manual.
3. I've updated pretty much every driver on the system. However, despite running the AMD chipset driver package, I'm still seeing old Microsoft defaults on the following devices:

Standard SATA AHCI Controller
ASMedia XHCI 1.0 Controller
ATI I/O Communications Processor SMBus Controller

4. The motherboard is definitely Windows 8 certified:

http://www.asus.com/ca-en/Motherboards/M5A99FX_PRO_R20/

5. I ran CHKDSK again; still looks good.

Stage 1: Examining basic file system structure ...
  546304 file records processed.                                                         File verification completed.
  3406 large file records processed.                                      0 bad file records processed.                                      
Stage 2: Examining file name linkage ...
  862822 index entries processed.                                                        Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                      
Stage 3: Examining security descriptors ...
Cleaning up 259 unused index entries from index $SII of file 0x9.
Cleaning up 259 unused index entries from index $SDH of file 0x9.
Cleaning up 259 unused security descriptors.
Security descriptor verification completed.
  158260 data files processed.                                            CHKDSK is verifying Usn Journal...
  37886904 USN bytes processed.                                                            Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 499746815 KB total disk space.
 245860128 KB in 390633 files.
    252932 KB in 158261 indexes.
         0 KB in bad sectors.
    664663 KB in use by the system.
     65536 KB occupied by the log file.
 252969092 KB available on disk.

      4096 bytes in each allocation unit.
 124936703 total allocation units on disk.
  63242273 allocation units available on disk.

Internal Info:
00 56 08 00 c5 45 08 00 7a 0e 0f 00 00 00 00 00  .V...E..z.......
e1 01 00 00 c3 a6 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.
JohnBusiness Consultant (Owner)Commented:
Windows 8.1 works well on commercial, properly engineered hardware. If "nothing is wrong", then you probably need to take another try at re-installing Windows. Install Windows, check BIOS and Chipset, upgrade all other drivers.

If Windows 8 DVD, upgrade batches of updates to about October 2013 and then upgrade to Windows 8.1 (different OS). Then continue with updates. When all done, test and only add applications after thorough testing.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JohnBusiness Consultant (Owner)Commented:
I should note that I have software that had to be upgraded just to run on Windows 8.1. It is not a given that Windows 8 software will run on Windows 8.1
Bradley DorranceHelp Desk AnalystAuthor Commented:
Thanks, John. I do have a Windows 8.1 ISO, as well as the 8.0 image I used prior to upgrading the installation to 8.1. I think I'll install directly from the 8.1 disk this time.
JohnBusiness Consultant (Owner)Commented:
Thanks for the update. Windows 8.1 is a different OS and not a service pack, so a direct install from the Windows 8.1 DVD is  good idea.
nobusCommented:
was everything solved by the 2nd install??
Bradley DorranceHelp Desk AnalystAuthor Commented:
Looking good so far, thanks. I nuked the SSD with DBAN then installed from an up-to-date Windows DVD. No errors or issues.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 8

From novice to tech pro — start learning today.