Daily BSOD while doing anything or at Shutdown/Restart

Thanks for the information you have provided :)

Firstly:

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

   Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

• Good and Free system security combination.

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff80003395340, fffff880033cb718, fffff880033caf70}

Probably caused by : afd.sys ( afd!AfdFreeEndpointResources+275 )

Code:

4: kd> !error 0xc0000005
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

Code:

fffff880033cb718 -- (.exr 0xfffff880033cb718)
ExceptionAddress: fffff80003395340 (nt!ObDereferenceSecurityDescriptor+0x0000000000000020)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

Some code or driver has used a null pointer, which is a illegal operation, since you can't use pointers to point non-existent memory addresses or data which isn't there.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Select Individual Settings, and then enable all the options apart from the Low Resources Simulation.

Okay, I attempted to install Malwarebytes and MSE. Malwarebytes went fine and found 4 files that contained malware, but those were not on my C drive. I still removed the infected parts.

However, when I attempted to run MSE, I had three crashes happen very quickly during the scan. The first one happened fairly quickly and the BSOD showed iusb3xhc.sys as the problem. I was already on the latest drivers, so I just tried to do a scan again and this time I got to almost all the way to the end of my 2nd HDD when I got a BSOD again, this time with just memory_corruption. I tried for a third time and didn't get very far in before I got graphical glitches and my computer froze. By this point I was flustered and thought to myself, I have gone through many iterations of reinstalling software over and over again, switching graphics cards and removing other software and hardware that trying to fix the issue by this point is going to be harder than starting fresh. So I decided to reformat. Through the middle of the reformat, I did realize I could have tried to run MSE in Safe Mode, but it was too late by that point.

I am going to keep my drivers and installation to a minimum for the next couple days and see if the problem is fixed. I have been able to leave the computer on for about 17 hours so far so, if I can leave the computer on for 72 hours without a BSOD, I will mark it as solved. If not, I will post a new SevenForum Diagnostic with updated computer and driver changes.

Thank you for the help so far.

Okay, thanks for the update :)

Okay, it has been well over a month since my last reply, but I did a lot during that time. So my problems weren't going away and I ended up RMAing everything. It took about 2 weeks to get everything back, and I put it all back together about 2 weeks ago. It went fine for three days, but then it BSOD on me again. At this point, I knew there had to be something that wasn't set up correctly, since these were all new parts.

So, first I did the dangerous thing and updated the BIOS, and that went fine (thankfully). However, when I was looking at the BIOS updates, I noticed that the two latest updates mentioned RAM compatibility. Then it hit me, I never checked out the RAM to see if it was compatible. Now, it ended up being compatible, but it got me thinking that maybe the settings are not correct, because I remembered seeing timings and voltages on the RAM information online. So I go in CPU-Z and find two problems with it. For one, I was running it on single channel, which is completely my fault, as I didn't have them in slots 2 and 4 for this motherboard to be running in dual. However, what was even more important was that I noticed it set the timings as 11-11-11-28, which were incorrect. The RAM calls for 9-9-9-24, so I found a guide on how to change it in the motherboard BIOS and set it to the correct amount. I also set it for 1600 MHz manually (even though it was correct) and set the voltage to 1.5V (it was at 1.488 on auto).

I have been BSOD free for the past 9 days since updating the BIOS and changing the RAM slots and settings, so I am going to assume my problem is solved. I am not sure if the BIOS update helped, but it was most likely the incorrect RAM timings that were doing it this whole time. It was a pain for my first non-OEM computer, but I did learn a lot, so it was all worth it. I am just glad I don't have to be seeing the color blue anymore...

That's great news, I'm glad you were able to solve your issue :)