Description of bsod code by system errors : Error: (09/09/2015 06:18:07 AM) (Source: BugCheck) (User: ) Description: 0x000000c1 (0xffffcf8189628fc0, 0xffffcf81896284fe, 0x0000000000ef4038, 0x0000000000000032)C:\WINDOWS\MEMORY.DMP090915-12156-01 http://www.carrona.org/bsodindx.html#0x000000C1 Error: (09/09/2015 05:05:36 If you have a restore point, try to load it and see if it helps, it may or may not. Because there are essentially an infinite number of hardware configurations possible, But I have done a diver verifier scan for old/unassigned drivers, done ram checks, and dskchk. Please advise?
If it's happening at random times for no reason it could very well be a bad motherboard. Thanks for your help. Keep in mind, that this method, while it may indicate a hardware issue, may actually be caused by the driver or software related to it.
I would run memtest again on one stick alternately (if there are 2 or more) just to make sure or use the computer directly in windows to check the difference. Also, run something like heaven benchmark for awhile and see if it crashes or not. Instructions on how to run Driver Verifier are here: Driver Verifier Settings Finally, make sure that you have ALL available Windows Updates. Nvidia Qu3bus Almost Not a Noob Joined: Jun 14, 2012 Messages: 2,461 Date Posted: Feb 11, 2014 #18 puggy-88 said: ↑ I'd still just check with a single stick or RAM in
I googled and googled, found lots of similar cases but no solution yet. Random Bsod Windows 7 Register a free account to unlock additional features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. If you're using a disk cleaner (like CCleaner), please stop while we're troubleshooting.Your UEFI/BIOS (version 0601) dates from 2013. Reminds me of when I was in college English!
BSOD Crashes and Debugging Random BSOD Kernel Data In-Page ErrorHi guys im having quite a weird issue with my laptop it is randomly bluescreening and not making any memory dumps. From the Properties screen, select the Tools tab. Do not edit the registry or the start-up programs without technical assistance or how-to. If it doesn't pass on stock clocks then you have some issues going on.
Also, run memory diagnostics to check to see if your RAM is bad http://windows.microsoft.com/en-US/windows-vista/How-do-I-know-if-my-computer-has-a-memory-problem Then run System File Check to make sure there's not an issue with the OS, like a Error: (09/08/2015 09:44:16 PM) (Source: Service Control Manager) (User: ) Description: The Diagnostic System Host service terminated unexpectedly. Random Bsod Windows 10 I've googled a bit on the errors and all the people seem to have indicated running standart things like... Blue Screen Windows 10 Select Roll Back Driver and confirm that you want to roll it back.
If your computer starts successfully, then try to troubleshoot the hardware driver by reinstalling or updating firmware. his comment is here Now that we've got some of that out of the way, let's consider some of the other things that could be causing a "blue screen". jawnTEM, Feb 11, 2014 pirateking97 Noob Joined: Oct 24, 2013 Messages: 390 Date Posted: Feb 11, 2014 #21 jawnTEM said: ↑ I'm gonna go with demon possession lol.Click to expand... Anyway, I suspected a hardware issue, and now I suspect that it's either your video card itself or an issue with it's drivers. Memtest86
RAM can pass all the tests in the world but then decide it's going to go faulty when it leaves the manufacturer. I thought it only switches to single when you use a single stick. That's the right one. http://darrenburnhill.com/random-bsod/random-bsod-124.html jawnTEM One Wild Crazy Mod-der!
Sent from my iPhone using Tapatalk Player177, Feb 11, 2014 jawnTEM and puggy-88 like this. Sent from my iPhone using TapatalkClick to expand... Where PC's are concerned, it could be anything.
You can get there via your Action Center. In testing one stick at a time, this is in order to eliminate the good sticks from the bad. Oftentimes the computer will reboot before you have a chance to examine the contents of the Blue Screen. I had a motherboard a couple years ago that would do the same thing.
It should be 13.12 or 14.1, if you want to try the beta driver. In testing one stick at a time, this is in order to eliminate the good sticks from the bad.