 | |
| |
| 23 Nov 2012 | #1 |
| | Seemingly random BSOD, thinking possibly RAM, looking for 2nd opinion Hello all, First time posting here, so hello and I appreciate any help or advice you guys may have for me. So it seems I just have crap luck when it comes to computers and BSOD's... I usually build my own PC and thus have had the unfortunate luck in the past 2 years to have gone through one entire pc (all components pretty much fried except the HD's), and now with my new PC build, I have found that it goes through RAM like they're hotcakes.. I'm not sure if it's the RAM I am buying, but it seems like every few months I'm having to replace a couple of the sticks for no good reason other then they are causing start up issues, and BSODs... The BSODs have been getting worse over the last week. A while ago it was once every couple months, then once a month, then it was once a week, now I've had 3 in the past 4 days.. So definitely going to have to get this sorted asap.. Any way, I am no pro when it comes to solving issues like these, but I read through the guide to helping diagnose BSODs, and I have my crash report all zipped up for anyone willing to help. Thanks again for your time and patience! Apoch |
My System Specs | |
| 23 Nov 2012 | #2 |
| | Welcome to SevenForums. 2 dumps, 2 bugchecks. Info: Quote:
Update drivers for C-Media Electronics USB Audio Driver from here: Driver Reference Table Code: 0: kd> lmvm CAHS164
start end module name
fffff880`0382c000 fffff880`039b7000 CAHS164 T (no symbols)
Loaded symbol image file: CAHS164.sys
Image path: \SystemRoot\system32\drivers\CAHS164.sys
Image name: CAHS164.sys
Timestamp: Thu Jun 16 13:10:06 2011 (4DF9AC4E)
CheckSum: 001403C4
ImageSize: 0018B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Quote: - search Google for the name of the driver - compare the Google results with what's installed on your system to figure out which device/program it belongs to - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager). - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program. Code: Start Menu\Programs\DAEMON Tools Lite Public:Start Menu\Programs\DAEMON Tools Lite Public As an alternative, many people recommend the use of Total Mounter or Magic ISO *Let us know if the computer is more stable or not?Then proceed with RAM test. Follow this way: Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes. Quote: 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.  Errors are sometimes found after 8 passes. Do this test overnight, before going to bed.Hope that helps for now. |
| My System Specs |
| 23 Nov 2012 | #3 |
| | Great, thank you very much for your post Koolkat. I will give all of this a go, and then see how my computer runs over the next couple days. I will post back once I have more information. |
| My System Specs |
| . |
| |
| 23 Nov 2012 | #4 |
| | Good Luck  |
| My System Specs |
| 23 Nov 2012 | #5 |
| | Hey Koolkat, Here's a summary of what I've done so far: I ran Anti-Rootkit TDSSKiller after uninstalling DAEMON tools, no threats found. I ran virus checks with MSE and ESET, no threats. I have screenshots from both Speccy and CrystalDisk. I ran chkdsk on both internal drives, and no errors were found. I downloaded Seagates HDD diagnostic, and will give that a go later today. I have not performed memtest yet, but will do so later tonight. I was not able to download the latest driver for my CMedia audio USB, because the driver that was available needed me to log in to CMedia's website, but I could not find a place to register. Perhaps I missed something there? All said, with everything else checking out, it's looking like it's coming down to the RAM (again).. But still, maybe you can see something I haven't. Thanks for your help! Apoch |
| My System Specs |
| 23 Nov 2012 | #6 |
| | Thanks for the snips. Let us know the results of memtest. Good luck |
| My System Specs |
| 26 Nov 2012 | #7 |
| | So, had another crash late last night. Nothing came up in the Seagate HDD diagnostic. I haven't been able to run memtest yet (my wife and I are having a baby any day now), but I'm guessing by the fact that these crashes seem somewhat random, I suspect it's likely the ram causing most of the issues... When I can get around to running it I will post what I find. All that said, the bsod's became less frequent over the past couple days. So something you recommended did actually help. I've attached the new crashdump file. |
| My System Specs |
| 26 Nov 2012 | #8 |
| | Well from the dump's bugcheck it does look like you'll have to rule out memory.. Code: *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, 14a1001, 0, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00000000014a1001
Arg3: 0000000000000000
Arg4: fffff70001080000
Debugging Details:
------------------ Quote: Driver Verifier Use verifier for 36 hours. Then send us the BSOD reports Driver Verifier I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature). In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . Then, here's the procedure: - Go to Start and type in "verifier" (without the quotes) and press Enter - Select "Create custom settings (for code developers)" and click "Next" - Select "Select individual settings from a full list" and click "Next" - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next" - Select "Select driver names from a list" and click "Next" Then select all drivers NOT provided by Microsoft and click "Next" - Select "Finish" on the next page. Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part). If you can't get into Windows because it crashes too soon, try it in Safe Mode. If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created. Driver Verifier - Enable and Disable |
| My System Specs |
 |
Seemingly random BSOD, thinking possibly RAM, looking for 2nd opinion problems?
| Thread Tools | |
| Similar help and support threads for: Seemingly random BSOD, thinking possibly RAM, looking for 2nd opinion | ||||
| Thread | Forum | |||
| BSOD 0x00000124 seemingly random + other possibly related issues | BSOD Help and Support | |||
| BSOD (seemingly random) | BSOD Help and Support | |||
| Seemingly Random BSOD | BSOD Help and Support | |||
| BSOD, seemingly random | BSOD Help and Support | |||
| Seemingly Random BSOD | BSOD Help and Support | |||
All times are GMT -5. The time now is 09:38 PM.
