Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Daily BSOD while doing anything or at Shutdown/Restart


08 Sep 2013   #1

Windows 7 Professional x64
 
 
Daily BSOD while doing anything or at Shutdown/Restart

I upgraded my computer back in July and have had a fairly daily BSOD. Many of the earlier BSOD pertained to my ATI Graphics Card when I was playing games. I would last about 20-30 minutes before it would crash. I of course replaced the card and got an NVIDIA GTX 760 and that has resolved my issues when playing games (so anything related to ATI in the minidump is solved). I have gotten a couple NVIDIA crashes when I installed the new card, but I downgraded to the most stable 314.22 drivers and those have now become few and far between.

However, at the same time I was also getting BSOD for my onboard network card. I went and googled around and found that the card is pretty unreliable with driver support being non-existent and all recommendations were to buy a separate NIC, which I did (Intel Gigabit CT PCI-E Network Adapter). However, even with the new NIC I still get many afd.sys, tcpip.sys, ndis.sys, and e1q62x64 crashes. I have uninstalled and reinstalled the drivers multiple times and have used the installer from Intel to get the latest drivers, to no avail. If I do not get a BSOD all day (usually about 9-10 hours) there is a 100% chance that a crash occurs the second I press shut down and it almost always relates to the NIC and if not, it will be memory_corruption. I googled around and found out it mainly has to do with memory leak in drivers, which the dump file also suggest in the Windows Debugging Tool.

If I don't get an error related to my NIC, it is always more general like ntkrnlmp.exe, ntoskrnl.exe, memory_corruption, or BAD_POOL_HEADER (19). Since I was getting these errors and they were not hinting to the problem, I used Driver Verifier following the guide on this site. I originally could not even get to the log in screen and had to launch in safe mode. Those dump files had to do with Daemon Tools, which I uninstalled. This let me get to the log in screen and I was able to use my computer for an about 5-6 hours. While Driver Verifier was on, I had one instance where the NVIDIA drivers failed and recovered, but other than that two other BSOD pointed to my sound card, so I uninstalled and reinstalled and updated to the latest drivers (ASUS Xonar DGX). I will note here that I have third party drivers (UNi Xonar 1.71) instead of the default ones. I have tried both kinds and still gotten a BSOD, so I am currently still on the third party drivers. I have not attempted Driver Verifier again, but if it still required after this post, I will attempt at it again.

I have also ran Memtest86 and had 17 passes with no errors (G.SKILL Ripjaws X Series 8GB (2 x 4GB)). With that I also reseated both of my RAM sticks and reseated my graphics card (changed power cables as well) and moved the sound card and NIC to different slots as well. It did not fix the issue, but I am much more confident that all of the hardware is installed properly.

I followed the guide for BSOD posting instructions and have added a zip file from the SevenForums Diagnostic Tool. Hopefully, this information can help.

Edit: Added most recent BSOD. This time it is something to do with ataport.sys. Something about it misaligned.




Attached Files
File Type: zip SF_08-09-2013.zip (2.79 MB, 7 views)
File Type: zip 090813-27471-01.zip (26.7 KB, 0 views)
My System SpecsSystem Spec
.

09 Sep 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Thanks for the information you have provided

Firstly:

Install and perform full scans with:
information   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:
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:
information   Information


Select Individual Settings, and then enable all the options apart from the Low Resources Simulation.
My System SpecsSystem Spec
10 Sep 2013   #3

Windows 7 Professional x64
 
 

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.
My System SpecsSystem Spec
.


10 Sep 2013   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Okay, thanks for the update
My System SpecsSystem Spec
26 Oct 2013   #5

Windows 7 Professional x64
 
 

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...
My System SpecsSystem Spec
27 Oct 2013   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

That's great news, I'm glad you were able to solve your issue
My System SpecsSystem Spec
Reply

 Daily BSOD while doing anything or at Shutdown/Restart




Thread Tools



Similar help and support threads for2: Daily BSOD while doing anything or at Shutdown/Restart
Thread Forum
BSOD shutdown then restart BSOD Help and Support
Solved BSOD only at restart/shutdown BSOD Help and Support
BSOD at shutdown/restart of pc BSOD Help and Support
Solved BSOD on shutdown/restart BSOD Help and Support
BSOD when shutdown or restart Graphic Cards
BSOD when shutdown/restart BSOD Help and Support
Shutdown / Restart = BSOD BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:04 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33