BSOD playing borderlands 2 Memory managment 0x0000001a

kickasspeanut · 19 Jul 2014

Hey all, had a whole bunch of driver related bsod issues you guys helped me fix a couple of months ago, so I'm hoping you can help again.

Got this memory managment BSOD today and i'm not really sure what caused it. My ram is fairly new and hasn't caused me problems before. I did a bit of poking around and read up a bit on windows virtual memory and was wondering if its connected to that.

I'll attach a screenshot of my virtual memory stats.

HarriePateman · 19 Jul 2014

Hello and welcome to sevenforums, there are no DMP Files here.

Dump Files - Configure Windows to Create on BSOD

kickasspeanut · 19 Jul 2014

My bad SF diagnostics must have spazzed out on me when i clicked grab all.

HarriePateman · 19 Jul 2014

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

Code:

0: 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: 0000000064b2a001
Arg3: 0000000000000462
Arg4: fffff70001080000

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

RAM - Test with Memtest86+

Driver Verifier - Enable and Disable

kickasspeanut · 19 Jul 2014

Happened again while i was gone, I will run the tests you asked me to.

kickasspeanut · 19 Jul 2014

driver verifier ****ed everything up and now even when disabling it in safe mode it just re enables its self and insta bsod's on boot. This has turned my pc into a paper weight.

Golden · 19 Jul 2014

Nonsense - you didn't follow the Driver Verifier instructions properly. Read them again. Driver Verifier does not just turn itself on automatically.

kickasspeanut · 19 Jul 2014

I followed all the instructions in this linkhttps://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

It crashes before getting to my desktop so I do as it says and boot into safe mode. Open driver verifier display current settings so I can see its still set to run.

Then I delete current settings double check they're deleted by displaying settings and making sure its all clear then I reboot and it bsods again saying driver verifier found a problem.

I go back into safe mode and open verifier and display settings and its back to be being turned on. I'm not making this up, its very confusing.

Anyway I saved my self by system restoring. No idea why driver verifier was so stubborn

HarriePateman · 20 Jul 2014

Sorry to hear that.

Did the Driver Verifier result in a BSOD.

kickasspeanut · 20 Jul 2014

Driver verfifer resulted in instant bsod on startup but since it wouldn't turn off and I had to system restore I doubt I have any of the bsod info on it.