BSOD Code 1e issue

Hi, I recently got a BSOD with code 1E, WhoCrashed info follows, and the dump file is attached. Any help would be appreciated, and thanks. Other info: I'm running Win 7 x64 with 12GB of RAM, it's a recent and nearly clean Windows install on an SSD which hasn't caused any problems recently (Had to update the firmware on it and after that it's been solid). By "nearly clean" I mean all it has on it is Steam and some games, along with some software that has likewise never caused any problems in the past. The system itself is about a year old build, had some bad RAM in it so I decided to upgrade it to 12 GB and tested the sticks with Memtest. Also new is the SSD, which now has only Windows installed on it, other programs/games/etc are all being installed on dedicated drives. Not sure how much of that info really matters but if any other info is needed, please advise. Thanks again. WhoCrashed Report: ——————————————————————————————————————– windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: AuthenticAMD AMD Phenom™ II X4 955 Processor AMD586, level: 16 4 logical processors, active mask: 15 RAM: 12881256448 total VM: 2147352576, free: 1960103936 ——————————————————————————– Crash Dump Analysis ——————————————————————————– Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 2/14/2013 8:19:19 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\021413-16770-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030CAB45, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 2/14/2013 8:19:19 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030CAB45, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. ________________________________________________________________________________ ___________________________________

I don't know that there will be an easy answer here, or even conclusive, various searches and studying codes lists a few possible causes, and the most dramatic cause suggested was a bad board and\or CPU, and there are no real tests for these, the other possible is bad ram, I appreciate you have recently encountered and rectified this once already, but if the cause of the bad ram has not been sorted, it's possible it could be the same again, you can test ram using memtest, but because ram passes tests it doesn't mean there's no problems. Other possibles are storage, one of the codes suggests there may not be enough space to do something, so check how much free space your drives have, and the last thing I saw suggested a program was trying to load in an incorrect format, but putting this all together, and taking into account you have had bad ram before, I suggest starting with testing that, my guess is your using 4 sticks, I suggest trying running the system with just 2 sticks, and see what happens. I suggest getting a sheet of paper, and number 1 through 4 on it spaced across it's width, then looking at your board, call the stick closest to the CPU stick 1, and carry on so the furthest stick from the CPU is stick 4, this is very important when trying to check ram, so make sure removed sticks are put on the correct place on the paper, you need to note what variation's you try, and the results of it, or you wont know what is doing what, and where, because it could be a single stick of ram, or it could be a bad slot on the board, by doing this you will highlight just where the problem is (assuming there is one of course). So start by testing in pairs, and maintain the dual ram when doing so, basically use the same coloured slots for each pair, so slots 1 & 3, once you have run and noted the first pair of sticks, repeat with the other pair, then start over and use slots 2 & 4, with each pair, if at this stage you have not had a problem, then the ram is probably OK, if it still plays up then you need to start testing with single sticks, again noting results as you go, if something is going on it should stand out quickly this way, so see how this goes.

I was able to test the RAM right after posting that actually, just to try and eliminate that as a possible cause. Tested each stick individually (I'm using 3 x 4GB sticks, all identical) and each stick had no errors. Also worth noting is that the problem hasn't recurred yet. As for HDD space I'm sure I have plenty (Well over a terabyte free on secondary drives, and at least 50GB on the Windows-only SSD) drive). I will try to recreate the problem sometime today and post the results. All I was doing at the time of BSOD was playing Borderlands 2, about an hour and a half in the session I believe. I have recently installed a new webcam, a Logitech C920, is it possible there's a driver issue there? I have used it a few times without any issues, both as a cam and just a mic for in-game chat but I'm not sure if it's too early to rule it out.

I can't say the new hardware is the cause, but it can't be ruled out either, if the issue persists after all is tried, disconnect it and see if it makes a difference is all I can suggest. But with your saying about 3 sticks of ram (should of realised when you said 12gig lol, brain freeze), I can help but wonder if this may be a cause, the recommended way to use ram is in matched pairs, at when boards have dual channel, unless you have a Tri channel board ? Space seems OK, but it depends on usage, I don't do gaming, but my best guess is there is a massive amount of data that gets moved around, and as big as 50gig sounds, it's possible it may not be enough (just trying to think of worst case scenarios), you say the SSD has 50gig free, but out of what size ? And as I don't know how gaming works, would you happen to know where (what drive) the games use for the data ? Although you may have installed to the other drives, I am wondering if it may be using the SSD for such files, just a thought, hope something shows up anyway.

If your OS is on a SSD and your games on a large Sata drive there could be various problems encountered. Worth noting that you will end up with quite a few active game files on your SSD because that is where your OS is and your games need to access the OS. Game FPS and texture speed will be governed by the speed of your SATA drive by the way, not your SSD. If you use imaging software (cloning a drive) for back-up purposes, there can be image restore problems associated with mixed files on both drives.

Outdated SSD Firmware is often the cause of BSOD, especially when using mixed exe files on different drive types.


A few notes on SSDs

What are the cons?
As with everything in life there are some cons to SSDs, but what are they?

Less capacity for the price.
May need a 2.5" to 3.5" adapter.
Constant firmware updates, but I find that is a good thing.
Also, performance loss if used in IDE mode or if your alignment is off, but that is with all HDDs and SSDs.
If you get a SandForce drive you could encounter a few things such as random BSODs, freezing, stuttering and the drive disappearing in the BIOS/UEFI of your mobo, but that should all be fixed with the newest firmware that is out for them.
SSD write performance may degrade when the drive is close to being filled or if you are constantly writing and erasing data to the drive without ample time for GC to take effect. The thing is that SSDs need some "clean" pages when writing data. Otherwise, they have to do a read-modify-write of a "dirty" block instead of just a write to a "clean" page. This process is basically garbage collection at run time and impacts your real time usage rather than preemptive garbage collection. So if you have little free space left and then pound the SSD with a bunch of random writes and do not allow the SSD to clean itself, the can be a noticeable performance degradation.


The Do's and the Dont's

Do's
Treat it as you would any other drive.
Use one as a OS drive over a HDD
Install all your apps/programs to the SSD
Make sure defrag is disabled for our SSD

Dont's
Don't bother to move your page file off the SSD
Don't worry about the amount of writes to your SSD
Don't full format your SSD
Do not defrag a SSD
When you Secure Erase with Parted Magic do not bother use the "enhanced/advanced method"
Do not use DBAN or similar programs to erase your SSD's data. It doesn't work properly. Use Secure Erase instead.
http://www.overclock.net/t/1179518/seans-s…ormation-thread