New
#11
I won't be able to take alook at those until tonight as I'm at work. I will get round to it though.
I won't be able to take alook at those until tonight as I'm at work. I will get round to it though.
Download and run MemTest86+ to test your RAM.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000003452, The subtype of the bugcheck. Arg2: 00000000061e2000 Arg3: fffff700010c0d18 Arg4: 91200001e2416c66
NoteRun MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here.
Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable
Enable Driver Verifier but only enable these options:
Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests
WarningMake a System Restore point before enabling Driver Verifier.
NoteYour system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Last edited by Boozad; 18 Jun 2014 at 14:43.
So I ran MemTest 10 passes and got 0 errors. Upon enabling Driver Verifier, following your instructions and the ones in the link (disabling the option you specified), I got a BSOD on windows start screen and just a loop after that. I got the option to launch startup repair once, and then yeah, just start screen, blue screen, start screen, blue screen. I did set a restore point first so I'm good. I attached the log info from this and the few other bsod's I've had in the past few days. Any other ideas?
Again, I really appreciate the help. I'm pulling my hair out a little bit over this one. I'm an idiot and haven't tried uninstalling that stick of RAM. I'll try that and see if it stops. If it does, is there a reason that installing that perfectly fine RAM would cause an issue like this? Like, if I reinstall windows with all 12GB installed, would that help the OS like, acclimate to the RAM or something? I've never had to do that before, including my old Q6600 that ran on Windows 7.
It's the driver for your NetGear or DLink USB Network Adapter, it's very old and needs updating.
Do you have either of those devices installed?Code:7: kd> lmvm WN111v2x start end module name fffff880`06038000 fffff880`060ed000 WN111v2x T (no symbols) Loaded symbol image file: WN111v2x.sys Image path: WN111v2x.sys Image name: WN111v2x.sys Timestamp: Thu Sep 25 09:27:48 2008 (48DB4B84) CheckSum: 000924FF ImageSize: 000B5000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
I DO! I just updated to the most recent driver (which is from 2010 but says it supports Windows 7). I'll let you know in a few days if everything is peachy :) Thanks for your help!
So a few days in and I have 0 BSOD's. Thanks for the help! I cannot BELIEVE I didn't think about the wireless adapter. I installed it at the same time as the RAM and used the stupid CD that came with it, then forgot to update the driver after. My mind just focused on the RAM, since I was kind of curious already if it was going to cause an issue. I'm an idiot, lol. Thanks again!
Not even kidding, I was discussing car insurance with my girlfriend and had a BSOD while I wasn't looking. Any ideas?
The latest dump file in the logs is dated the 21st which was the last one you uploaded. It looks like Windows didn't create a dump file for that one so there's not much I can do sorry.