Custom Build PC, recurring BSODs

CynanMachae · 08 Apr 2014

I've got this new PC build like 3 weeks ago, at first it seemed it was fine, I maybe got 1 or 2 BSODs in the first 2 weeks, but during the last week I'm getting 1 each day sometimes two, and mostly when I'm only browsing on Chrome but it happened when playing game/watching videos as well.

The check strings are mostly different, only getting two occurrences of System_service_exception and memory_management.
Thanks

koolkat77 · 09 Apr 2014

Norton is contributing to the BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

If this does not provide stability. Test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Apr  8 20:51:48.996 2014 (UTC + 6:00)
System Uptime: 0 days 0:21:41.322
BugCheck 1A, {41284, 50cd001, 8c, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr  7 23:28:57.039 2014 (UTC + 6:00)
System Uptime: 0 days 0:01:05.991
BugCheck 3B, {c0000005, fffff80002eb55f5, fffff88003f5a620, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1d5 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr  7 22:40:11.501 2014 (UTC + 6:00)
System Uptime: 1 days 10:25:15.828
BugCheck A, {28, 2, 0, fffff80002ec9d80}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  NvBackend.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Apr  6 11:02:32.013 2014 (UTC + 6:00)
System Uptime: 0 days 0:25:08.966
BugCheck 24, {1904fb, fffff88006c3f468, fffff88006c3ecc0, fffff880015b764b}
*** WARNING: Unable to verify timestamp for BHDrvx64.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
Probably caused by : BHDrvx64.sys ( BHDrvx64+a8019 )
BUGCHECK_STR:  0x24
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sat Apr  5 08:16:44.194 2014 (UTC + 6:00)
System Uptime: 0 days 3:57:49.520
BugCheck 3B, {c0000005, fffff80002e82ac5, fffff8800aa4a810, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  PowerDVD13Agen
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Fri Apr  4 08:43:35.795 2014 (UTC + 6:00)
System Uptime: 0 days 0:01:24.748
BugCheck 50, {fffffe8007b13430, 0, fffff80002ef0fe5, 7}
Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+215 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

CynanMachae · 09 Apr 2014

Small update, I had already started testing ram (which is 1 Crucial ballistix sport 8gb stick), and I got upwards of 900 errors after 8 passes. I changed the ram slot and while it looked fine at first, I got 10 errors at the 4th pass. While I don't know why theres this huge difference in errors number, I does seems my ram is faulty as well. I don't really have another ram stick for testing tho.

essenbe · 09 Apr 2014

CynanMachae, on first appearance, it appears your ram is defective. I would continue testing the stick in the other 2 slots at least until you get errors. If you get even 1 error, you can stop, your ram has failed. What we are looking for here is whether the ram is bad or the motherboard dim slots are bad. Also, you would be much better off with 2 sticks of ram purchased as a kit. Kit's are tested to work together, where separate sticks, even of the same manufacturer and model won't always work right together. 1 stick of ram will work in single channel mode where 2 sticks in the same channel work in dual channel mode and give an increase in performance. Crucial is very reputable company and you should have no problem with them or if you are within the time frame, you can RMA to where you bought the ram. But, continue with the ram tests on all 4 slots to make sure it is not the board. I would suggest you do the tests soon. Most retail outlets will RMA a defective product within 30 days. You will be much better off doing an RMA with the supplier than with Asus, trust me. That last statement was in case the board is bad. If you have any questions, feel free to ask. I will be most happy to explain anything I can.

essenbe · 09 Apr 2014

One other question. Your system specs list 2 X 4GB sticks of ram but you only have 1 8GB stick you are testing. If your hardware has changed please update it. We go by your hardware on almost every post in order to help you. The correct listing, as detailed as possible would help us to help you. You can look at mine by clicking the 'My System Specs' in the bottom left corner of this post to see what we would like, and like them kept up to date.

CynanMachae · 09 Apr 2014

Woops, sorry about that, actually the 2x4gb was my intent at first when I built my PC, but I switched at the last minute due to a deal on the 8gb (and will probably upgrade to 2 later), so when I filled my profile I probably just didnt remember about that.

Anyway yea, I'll test the other 2 slots right now, I do hope indeed it is the ram and not the mobo because that would complicate things a bit. I already did contact ncix, 30 days from my order were just past, but since some items where backordered and delayed like 2 weeks they are ok with an RMA since I got my stuff like really late.

What I wonder tho, let's say it's the mobo, could it have caused the ram to go bad? (or even the other way around) I really don't know a lot about memtest so the huge number of errors in the slot#1 make me think both could have caused that huge number of errors.

Anyway, thanks for the help so far

essenbe · 09 Apr 2014

The way memtest works is each pass consists of 9 or 10 tests. Each pass and each test, tests a different thing and it takes a full minimum of 8 passes to test the complete ram. That may account for the difference in errors, but is also why we always ask for a minimum of 8 passes. However, if you get even 1 error, you can stop the test, the ram has failed. Period. Now, the ram can fail because it was defective, mishandled or because the dim slot was bad. That's what we want to know. Is it the ram or the board. A bad dim slot can cause the ram to show errors just as a defective ram stick will. Without expensive sophisticated equipment, we have no way to test either the ram or the board dim slots except this test. If you ram tests bad in all 4 slots, I would call it the ram. If it fails in 2 slots and runs without error in the other 2 slots, I would call it the board. That part is pretty much simple logic. However, just my opinion, if, for example, it failed in 3 slots and passed in 1 slot, I would RMA both the board and the ram if at all possible. I may suggest, if you have a friend that is willing to help you, have him run that stick in his computer and run a couple of his sticks in your computer. That would answer all the questions.

I can't answer your last question technically, but I have never heard of a bad ram stick damaging the motherboard and don't think it can unless it is inserted wrong. I have also never known of a bad dimm slot to damage the ram either. And, I have run this test hundreds of times on good and bad ram and boards. So, perhaps not a technical answer but a practical one. No, it won't happen either way.

CynanMachae · 09 Apr 2014

Thanks for the explanation, it did help.

So I tried running memtest on the slots 3 and 4 but I came with a problem. When the ram is inserted in slot 3 or 4, computer starts for like one seconds, then shuts down. It then tries booting again 2 secs later ans then does the same thing in a loop. From what I could see by looking about this problem, it would be caused by the dual channel memory configuration? Ram will work in slot a1 or a2 but not when its alone in b1 or b2. So with only one stick it seems i cant test slot 3 and 4.

I'll check if I can find someone to test with but Im not sure that will be possible soon (and I cant hold on the RMA forever).