New build, multiple random BSOD with various error codes

alexb1187 · 04 Apr 2014

Did a longer test on memtest86+ still no errors. Screenshot attached. After rebooting, the pc was idle and I walked away for about 30 minutes. When I came back, there was a blue screen waiting for me. Logs attached.

Arc · 05 Apr 2014

Test all your HDDs. Specially the Seagate 3 TB one, named as Gargantuan Disk.
SeaTools for DOS and Windows - How to Use

Change the SATA cables.

Scan the system for possible virus infection with the following programs. IT IS A MUST.

Let us know the results.
_____________________________________

Code:

fffff800`04435b80 fffff880`0114425e ataport!IdeCompleteScsiIrp+0x62
fffff800`04435bb0 fffff880`0113ee32 ataport!IdeCommonCrbCompletion+0x5a
fffff800`04435be0 fffff880`01147821 ataport!IdeTranslateCompletedRequest+0x236
fffff800`04435d10 fffff880`01147120 ataport!IdeProcessCompletedRequests+0x4d5
fffff800`04435e40 fffff800`02c9830c ataport!IdePortCompletionDpc+0x1a8

Code:

Event[34999]:
  Log Name: System
  Source: Disk
  Date: 2014-03-21T00:00:19.855
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: PillarOfAwesome
  Description: 
An error was detected on device \Device\Harddisk5\DR5 during a paging operation.

alexb1187 · 05 Apr 2014

All HDDs passed the tests (the SSD did not, but that was only due to Seagate not recognizing the serial code). I ran the long tests on the 3TB drive, but the short tests on the rest. Please note that I ran the application within windows, not the bootable image option.

I changed the sata cable.

Both virus scanning applications found no issues. I did a full scan with Windows Defender Offline (and a quick scan, but the full was obviously more comprehensive).

I will let you know if I get another blue screen. For now, I am hopeful.

alexb1187 · 05 Apr 2014

Well that was short lived. I was browsing the web and got this blue screen.

Arc · 06 Apr 2014

alexb1187 said:

Well that was short lived. I was browsing the web and got this blue screen.

It is a stop 0x3B.

Code:

BugCheck 3B, {c0000005, fffff880016cf272, fffff8800c2aac80, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

But having no more information that it is caused by a memory corruption.

It also appears that you ran memtest, without any error.

alexb1187 said:

Memtest86+ ran through 8 passes without error.

Seeing the frequency of the BSODs and the frequencies of the changing bugcheck codes and probable causes, it will be the best for you to perform a clean install. Follow it: I Clean Reinstall - Factory OEM Windows 7

It will at least discriminate between the hardware issue and software issue. If the issue is a software issue, the clean install is supposed to cure it.

alexb1187 · 06 Apr 2014

I am opposed to doing a fresh install of windows simply because I did a full clean install around 2 months ago (when I first built the computer). And I have been getting these blue screens this whole time. I am fairly certain this isn't a software issue anymore.

So, and I understand this is just speculation, what hardware do you think may be the problem? At this point I'm only confident in the memory and the videocard (since I have tested both extensively).

andrew129260 · 06 Apr 2014

Apologies for I have not read over this whole thread, but Can you remove all ram sticks except one, and run the mem test on that? If that one ram stick works well, can we use the system as normal with one stick of ram and see how things go?
(since you do not want to do a clean install)
Alternatively, you could make a system image with windows 7 backup and restore center, or the free macrium.
Image your system with free Macrium
Then you can do a clean install, add no software (just updated drivers) and use just internet explorer for a while, or test with prime 95 and see if any bsods occur. If they do, it defiantly is not a software problem.
Once that is discovered its not a software issue, you can then restore the system image and everything is back to normal and the way it was before we messed with your system. If it is a software problem, we can narrow it down to see what program it is that is causing it.

alexb1187 · 06 Apr 2014

Hi Andrew,

Thanks for joining the thread. I have run memtest on each individual stick in each slot (took lots of testing), but never got any errors.

alexb1187 said:

I also ran memtest86+ for days, testing each stick and each slot. I let memtest run past pass 8 each time. The last run I did was with all sticks in all slots, and I let it run to pass 21. No errors.

Since then, I have tested all sticks at once to pass 10 without error.

If you think it will help, I will run with only one stick. Let me know.

andrew129260 · 06 Apr 2014

Yes, please try only 1 stick and follow the suggestions posted in post 37 to continue to receive more help. If you have any questions on what was asked, it is perfectly fine to ask for help on those. Thank you.

alexb1187 · 06 Apr 2014

I haven't gone down to one stick yet, since there were some things I wanted to do before I limited my ram. I just got this blue screen. This one behaved slightly different, in that it went to a blue screen with just one line of text for a second. The line looked like it said "[something] hardware failure", then went to the normal blue screen. I will go down to one RAM stick now, and will let you know what happens.