General discussion

Windows 8.1 Pro 64-Bit Unreliability

Dear Forum,
I apologize for the length of this post, but I've exhausted my skills in attempts to determine how to fix the increased unreliability of my Windows 8.1 Pro 64-Bit desktop. Here are the details:

BSODs of varying types have been experienced during the last 30 days on my Windows 8.1 Pro 64-bit desktop with the following major components:

Intel i7 4770K (3.50 GHz) (no overclocking)
G.SKILL Ripjaws Series DDR3 Dual Channel SDRAM - 16 GB [2 x (2x4GB) 240-Pin 1600 (PC3 12800)]
Gigabyte Z87X-UD4H-CF (SOCKET 1150) Motherboard
NVIDIA 2047MB GeForce GTX 760 (EVGA)
Samsung SSD 840 PRO 256 GB Series SATA-III (6.0 GB/s) SSD (C-Drive, System)
Western Digital 1 TB Caviar Black SATA-III Hard Drive (F-Drive, Data)
Western Digital 1 TB Caviar Black SATA-III Hard Drive (L-Drive, Data)
Western Digital 750 GB Caviar Blue SATA-III Hard Drive (M-Drive, Data)
Windows 8.1 Pro 64-Bit with Media Center

The basic system - all components except 256 GB Samsung 840 and Windows 8.0 Pro 64-Bit,
which I installed - was purchased from Cyber Power PC in 12/2013. The OS was updated to
8.1 Pro and Update 1 were installed soon after they became available. The system was essentially bullet proof until recently.

During 10/2015, system reliability degenerated with multiple BSODs per day:

DRIVER_POWER_STATE_FAILURE (ntoskrnl.exe (nt+0x152736) (ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
STATUS_SYSTEM_PROCESS_TERMINATED (ntoskrnl.exe (nt+0x14F8A0) (ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
SYSTEM_SERVICE_EXCEPTION (ntoskrnl.exe (nt+0x14F8A0) (wow64cpu.sys (wow64cpu!TurboDispatchJumpAddressEnd+0x59Cool
PFN_LIST_CORRUPT (ntoskrnl.exe (nt+0x14F8A0) (ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
DPC_WATCHDOG_VIOLATION (ntoskrnl.exe (nt+0x14F8A0) (hal.dll (hal!HalPerformEndOfInterrupt+0x1A5)
REFERENCE_BY_POINTER (ntoskrnl.exe (nt+0x14F8A0) (ntdll.sys (ntdll!ZwTerminateProcess+0xA)
IRQL_NOT_LESS_OR_EQUAL (ntoskrnl.exe (nt+0x14F8A0) (ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
SYSTEM_SERVICE_EXCEPTION (win32k.sys (win32k+0x161A1A) (dcomp.sys (dcomp!Ordinal1009+0xA)
SYSTEM_SERVICE_EXCEPTION (win32k.sys (win32k+0x1AF7F) (user32.sys (USER32!InvalidateRect+0x1A)
SYSTEM_SERVICE_EXCEPTION (ntoskrnl.exe (nt+0x14F8A0) ntdll.sys (ntdll!ZwWaitForSingleObject+0xA)
KERNEL_SECURITY_CHECK_FAILURE (ntoskrnl.exe (nt+0x14F8A0) (dxgmms1.sys (dxgmms1!VidMmInterface+0xF9CB)
BAD_POOL_HEADER (ntoskrnl.exe (nt+0x14F8A0) (snapman.sys (snapman+0x227A4)
IRQL_NOT_LESS_OR_EQUAL (ntoskrnl.exe (nt+0x14F8A0) (ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Analysis was done using WhoCrashed, which suggested that errors are unlikely to be hardware
based but are likely to be caused by 3rd party driver. However, I ran memtest86 from
boot CD and Seagate Seatools for Windows to further rule out hardware as root cause. Neither test reported hardware errors.

All software is up to date to the best of my knowledge. Thanks for your support.

Discussion is locked
Follow
Reply to: Windows 8.1 Pro 64-Bit Unreliability
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: Windows 8.1 Pro 64-Bit Unreliability
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Comments
- Collapse -
Small world.

Just last month more than a handful of Seagates that passed the test but the DPC_WATCHDOG_VIOLATION vanished when we removed or cloned the Seagate onto another new drive. While we know Seagate didn't fare well in tests, this is something new. That is the maker's test passes yet ...

I'd remove all the drives, clone a single for the OS onto a new drive and re-test. There are clients that will argue so be ready for them to scream.

- Collapse -
Re: Small world

I plan to follow your approach. The first step will be to clone the HD that holds Outlook 2007 .pst files, since this is my primary mail program. Should the Samsung 840 SSD (C-Drive, System) be cloned to another SSD or a spinning disk? Based on generally good reviews, I intend to stick with WD Black (7200 RPM) drives increasing capacity to 2 TB. Since this is my primary computer, it will be a week or so before performing these tasks. I shall report results on this Forum thread. Thanks for your recommendation, Bob. Happy

- Collapse -
To me it doesn't matter.

The watchdog failure seems to be tracking back to hardware failures. Maybe a driver failure but in cases so far the systems were working without a driver change so we have a few months of tracking this somewhat elusive issue now and what we try next.

Sure beats the heck of what we did before. A lot less time lost as well.

Remember I can't assure you it's this but it's fast enough to try in the shop. The clone machine of a 1TB HDD takes about 20 minutes now and we don't have to babysit that so in the shop, it's a process we use to sniff it out.

It worries me that HDDs are passing tests yet this happens. Maybe another VW story.

CNET Forums