BSOD MEMORY_MANAGEMENT ntoskrnl.exe 0x0000001a

[LAE]

This is unbearable.

Win7-64b

Had constant mem management bsods when putting together a new system, ran verifier and mem test for going on 13hrs and both came up fine.
Replaced the motherboard and still had the same errors, thought it might be a corrupt install so clean installed win7 64-bit and it was fine for a day or so and now the errors are popping up again.

3 Bsods this morning:

SYSTEM_SERVICE_EXCEPTION 0x0000003b
MEMORY_MANAGEMENT ntoskrnl.exe 0x0000001a
NTFS_FILE_SYSTEM 0x00000024

in that order.

Thought it might be a corrupt hdd but not ive just no idea. I think i have no choice but to replace the ram. It happens at random, and often would happen a couple minutes into ever start up, as soon as everything was loaded and i started using the computer it would bsod. Then when restarting all would be fine.

Any ideas?

 

[zigzag3143]

This is unbearable.

Win7-64b

Had constant mem management bsods when putting together a new system, ran verifier and mem test for going on 13hrs and both came up fine.
Replaced the motherboard and still had the same errors, thought it might be a corrupt install so clean installed win7 64-bit and it was fine for a day or so and now the errors are popping up again.

3 Bsods this morning:

SYSTEM_SERVICE_EXCEPTION 0x0000003b
MEMORY_MANAGEMENT ntoskrnl.exe 0x0000001a
NTFS_FILE_SYSTEM 0x00000024

in that order.

Thought it might be a corrupt hdd but not ive just no idea. I think i have no choice but to replace the ram. It happens at random, and often would happen a couple minutes into ever start up, as soon as everything was loaded and i started using the computer it would bsod. Then when restarting all would be fine.

Any ideas?

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-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/Win7 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[LAE]

As I said in my original post, I ran verifier and memtest (13hrs) and both came up clean. I'm at wrk at the moment but ill run the sticks again individually and in all slots.

Surely its hardware considering the clean install??

 

[LAE]

Now this is weird, i used the cd memtest n left it running on the different ram sticks, the 3rd however did not want the computer to start. It couldn't make it past post. Nice ive found the dodgey one.

swapped em out put the other two back in and started the computer up. EXTREMELY slow, seriously taking 2-4minutes to open simple programs and some webpages aren't fully opening.
I figured it might be the verifier getting to work and left it be, fell asleep and come back to a restarted computer.

bsod:
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION 0x000000d6

so the verifier has found something. Both a dodgy stick and a dodgy driver?

100511-110901-01.dmp is the last verifier induced bsod. what to do now?

 

[LAE]

anyone?

tried the ram that i thought was bad in the other slots and it worked, then tried it back in the first and it worked fine. So confused now.
Memtests show nothing, i really have no idea what the problem is now. corrupt hdd?

The computer is running extremely slow now, 10+minutes to loadup, all programs are taking 30sec-1min to load.
This shouldn't be a slow computer, I7 3.4 cpu, 6gb ddr3 ram, good hdd, good gfx card.

wtf is going on?? only saving grace now is that there has been no bsods.

EDIT: ok so verifier was still running forgot to disable it, it has returned to normal speed but im still wary of the bsod's. i want it sorted. shall i return the ram?

 

[zigzag3143]

Now this is weird, i used the cd memtest n left it running on the different ram sticks, the 3rd however did not want the computer to start. It couldn't make it past post. Nice ive found the dodgey one.

swapped em out put the other two back in and started the computer up. EXTREMELY slow, seriously taking 2-4minutes to open simple programs and some webpages aren't fully opening.
I figured it might be the verifier getting to work and left it be, fell asleep and come back to a restarted computer.

bsod:
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION 0x000000d6

so the verifier has found something. Both a dodgy stick and a dodgy driver?

100511-110901-01.dmp is the last verifier induced bsod. what to do now?

While not driver verifed most recent crash was Related to CFRMD.sys Safe Delete Filter from COMODO Security Solutions Inc.

I would remove and replace comodo with Microsoft Security Essentials

How to uninstall Comodo Firewall?

Virus, Spyware & Malware Protection | Microsoft Security Essentials