Windows 7 They're back!~ BSOD's, that is.

teeBee · Oct 12, 2014

So it's been some time since my last BSOD thread. A lot has changed, and a lot has stayed the same. Here's a quick rundown:
Since my last post I was problem free up until the end of the month, then the BSOD's came back. I tried fixing them myself for a while, but finally gave in and started looking for parts to replace/add to my setup. I've since then added a new cooling system that keeps my CPU at ~30°C when idle and ~45°C when under load, peaking to ~49°C when I ran the CPU burn in test. I added 8 more gigs of RAM, a new HDD and an SSD, added a new audio card, and plugged in the remainder of the fans (while also adding one on the side). I scraped the old HDD, and was on the fence with scrapping the GPU, but money constricted me. So this meant that I would need to reinstall windows (which was highly recommended in the previous thread!) on the SSD. The setup went excellently, and for 2+ months my computer was happy..

Since 9/26/2014 I have had constant BSOD's every day, each with the same bug check string. I've looked around, ran chkdsk's and memtests, but I just don't have the time anymore to try and 'fix' this alone. So here we are again.

Think you can help me?

EDIT: Adding a bit more info..

I think I installed the newest drivers for my GPU the day before or after the BSOD's came rolling in. I've since then reverted to what I used at the start.

I have recently begun sleeping my computer instead of shutting it down, and whenever I wake it a message comes up saying that the GPU has stopped working and has restarted successfully(?).

I also installed ArcheAge, which installs HackShield, which installs drivers that run and do whatever while I'm not on ArcheAge. Why is this important? This is around the exact same time the BSOD's started occuring.
The BSOD's usually only happen while playing video games such as PlanetSide 2, Star Citizen, and ArcheAge. Sometimes they happen while simultaneously watching a video on youtube/twitch. (Should note, I've never seen it BSOD through idling or specifically watching videos.)
I've ran a full mem. test for 8 hours and it reported no errors. I'm thinking about running one for a lot longer.
I have recently updated my BIOS.
Since wiping and installing the 337 drivers (the original drivers that were installed on this computer) the BSOD's have begun to black my screens(2) for a few moments, until finally displaying the blue screen.

kemical · Oct 14, 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa88122a1c10, 0, fffff8800ffb0750, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+6dc )

Followup: MachineOwner

Hi,
Bug check 0x50 usually occurs after the installation of faulty hardware or in...

teeBee · Oct 17, 2014

This is new. Go this one through playing with the Unreal Engine 4 on max settings.-And streaming it at the same time.

kemical · Oct 18, 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000133166, fffff8800cb5fbe0, 0}

Probably caused by : win32k.sys ( win32k!zzzAttachToQueue+29e )

Followup: MachineOwner

Hi,
looking your dump file I see the process that was being used at the time of bsod is OBS.exe or Open Broadcaster Software. Does this ring any bells with you? I would also view any third party software you currently have running (discounting games) as suspicious. Try uninstalling apps like the Evolve app you have and anything else that is similar. If the bsod stops you could always add them back one at a time and see if any start the bsod off again.

If the above comes to nothing then perhaps it's time to try the driver verifier. This link will show you what you need to do in order to run the verifier:
http://www.reviversoft.com/blog/2013/09/using-driver-verifier-to-fix-a-blue-screen-of-death/

teeBee · Oct 18, 2014

kemical said:
... looking your dump file I see the process that was being used at the time of bsod is OBS.exe or Open Broadcaster Software. Does this ring any bells with you?

Yeah, I stream using OBS

kemical said:
I would also view any third party software you currently have running (discounting games) as suspicious. Try uninstalling apps like the Evolve app you have and anything else that is similar. If the bsod stops you could always add them back one at a time and see if any start the bsod off again.

Will do. Haven't used Evolve in quite some time anyway.

kemical said:
If the above comes to nothing then perhaps it's time to try the driver verifier. This link will show you what you need to do in order to run the verifier:
http://www.reviversoft.com/blog/2013/09/using-driver-verifier-to-fix-a-blue-screen-of-death/

We'll have to see. Will post back later this week.

kemical · Oct 19, 2014

Ok teebee understood and I'll await your next post.. Hope all goes well..

teeBee · Oct 22, 2014

3 without driver verifier on, 1 with.

Had a BSOD right after loading back into windows from another BSOD. :/

kemical · Oct 22, 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {20e, fffff88007d77615, fffff9810710aee0, 0}

*** WARNING: Unable to verify timestamp for DirectIo64.sys
*** ERROR: Module load completed but symbols could not be loaded for DirectIo64.sys
Probably caused by : DirectIo64.sys ( DirectIo64+2615 )

Followup: MachineOwner

Hi,
The driver that verifier caught was a PassMark BurnInTest driver so probably worth removing said application. In fact I'd be suspicious of any third party app you've got running.. The other dump files contained a Bugcheck 1A memory corruption, another was too corrupted to read and the other was our old friend Bugcheck 50.
I know you've already tested the RAM but try booting with only one stick installed. If you still get a bsod then swop sticks and try again. Sometimes bad ram won't be caught even by memtest86 and this is a sure way of finding out.

Windows 7 They're back!~ BSOD's, that is.

teeBee

Member

Attachments

kemical

teeBee

Member

Attachments

kemical

Essential Member

teeBee

Member

kemical

Essential Member

teeBee

Member

Attachments

kemical

Essential Member

Similar threads