Windows 8 New Mother board - Random BSODs

TacticalQuit

New Member
Joined
Apr 29, 2014
Messages
29
I posted once before about this issue with an older set of parts. I followed the suggestions in it and after removing norton, the problems went away. I'll post it here in case it helps.

I got a new mobo/proc and now the Bsod demon is back.

New System Specs are:
Z97 Maximus VII Hero
i7 4790k
4x Corsair Vengeance 1600MHz
2x R9 290x gfx card
2x Samsung 840 Pro 128GB on RAID0
1x 3TB HDD

Windows 8.1 update 1

I'm getting random blue screens out of no where. When I got the board, I kept getting SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (ACPI.sys) in a boot loop, but those seem to have gone away. I also now have a DAC attached, but as it uses no drivers I'm not sure if it could be the problem.

Any help would be very much appreciated
 

Attachments

Last edited:
Solution
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a01f59f21af71c, b3b72be0449a2df7, fffff8001fc07ea4, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
Hi...
Sort by date Sort by votes
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a01f59f21af71c, b3b72be0449a2df7, fffff8001fc07ea4, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
Hi,
both dump files were of the same bugcheck although probable causes were different. This bugcheck can be caused by:

In your case you probably have a driver causing these issues or a possible hardware issue.

Checking through the driver stack your drivers look in pretty good shape apart from:

SaiK0CFA.sys Tue Jul 20 17:26:29 2010: Possibly a Saitek mouse or keyboard? 2010 is a little old for Windows 8.1 (windows 8.1 hates old drivers) and I would try and update whichever device it is. ( I now see it's a Cyborg RAT 9 latest driver is 2012 version, I think):
http://www.cyborggaming.com/download.htm

lvuvc64.sys Tue Oct 23 03:12:08 2012: Logitech USB Video Class Driver (WebCam) check for update:
Link Removed

Check you haven't got any corruption in Windows by the system file checker. Open an admin command prompt and type:
sfc /scannow
Press enter and await results.

Check your GPU memory is ok by running this test:
Link Removed

If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Can you post the make and model of your PSU please.

Post any new dump files.
 
Upvote 0 Downvote
Solution
Link Removed

I updated the mouse driver, it was old. and I installed the Logitech driver, but I'm fairly certain it was already up to date.

Ill run the last 3 tests later today.

Thank you for taking the time to help me with this.
 
Upvote 0 Downvote
I ran sfc /scannow, and I havent had any issues with bsod. I think it must have been the mouse driver. I'll run memtest86 tonight, but I'm fairly certain this problem has been solved. Thank you very much .
 
Upvote 0 Downvote
Hi Tactical,
to be honest if the bsod's haven't occurred since changing the driver I'd hold off on the Memtest86. If they do return then consider running it. Hope all goes well and post back if issues reoccur..
 
Upvote 0 Downvote
I got another BSOD. I'm going to start memtest86, I'll post back with the results.

I was messing around with the clock and voltages, because I thought the problem was fixed, but I tested my settings with prime95 and found it to be stable. You'd think if it was going to crash because of the clock, it would be when running prime, not just sitting downloading a game.
 

Attachments

Last edited:
Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a01f591f18b606, b3b72bdf7197ecd1, fffff800803c2d00, 1}

Probably caused by : memory_corruption

Followup: memory_corruption
Hi,
yup looks like you could do with running Memtest86 if only to eliminate the RAM as a possible suspect. I'll await your results.
 
Upvote 0 Downvote
Try and run the test overnight (12hrs minimum as some errors don't crop up until the 12hr) if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.
 
Upvote 0 Downvote
Hello. I ran the vmt test on both gfx cards. no errors.
I'm not sure what to think. The Bsods are very infrequent now. The majority of them happened before updating that mouse driver. I've only had the one since.
Am I expecting too much that I shouldn't get any bsods?

I'll post any more dumps I get.
 
Upvote 0 Downvote
Well you shouldn't have any blue screens at all really. They basically happen to stop the machine from doing more damage to itself from either bad code or hardware faults.
I went back to the last dumps you sent and had another look through.

Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {7ff9d5c118aa, 0, ffff, ffffd00020fc6b80}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+24b )

Followup: MachineOwner
The above Bugcheck is caused by either drivers or file system. Try running this command in a admin command prompt:
Similar to the System File Checker is the DISM Tool. This will, if possible, download files to repair missing or corrupt data. Open the admin command prompt and type:
DISM /Online /Cleanup-Image /RestoreHealth (or copy and paste it)
Press enter and await results.

I also checked through your driver stack again and noticed this driver which I must have missed before:

WinRing0x64.sys Sat Jul 26 14:29:37 2008: Many different programs center around the using of the WinRing libraries (RealTemp, Corsair Link2 (known BSOD issues w/Win8), Razer GameBooster, Fusiontweaker. As I mentioned previously win 8.1 hates old drivers see if you have something related to the above and either remove or update.
 
Upvote 0 Downvote
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was
repaired.
The operation completed successfully.

I don't have any of those installed. I used to have Realtemp and Corsair Link2 installed, but I removed them a while ago
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Solved
Windows 8 Frequent Random BSoDs: Critical Structure Corruption and Possible RAID Issues on Windows 8.1
Replies
4
Views
2K
kemical