Blue Screens Vista home premium 32 bit

[tortofe01]

An Attempt was made to write to read-only memory was the blue screen i got today. I have gotten others and they are not all the same, the computer runs fine once restarted most of the time and it happens most of the time right when windows vista is done loading to desktop. Also it will make programs error out, like games or IE7 sometimes. I have tested my memory over night and nothing showed up as an error.

The blue screen code i got today is:

An Attempt was made to write to read-only memory

0x000000BE (0x97ED73B4, 0x51FA4121, 0x9946C6EC, 0x000000B)

Under load doesnt make it happen more or anything, it just randomly happens, sometimes when i start my computer up, sometimes while im in the middle of something, thats why i thought it sounded like memory to me. Sometimes just sitting at the desktop.

I have also attached many of the last minidumps it has made for me if that helps anybody out.

I have attached all the minidumps that I have gotten and have renamed them the date they happened.

Also I just got the same motherboard, though with a different CPU and different graphic card, right when i booted it up i went to the bios and it has the same bios (not updated) and it doesnt seem to lag like on this computer, does that mean it could be the motherboard? or the CPU or the graphic card perhaps or nothing to worry about?

this computer has the following parts in it:

Motherboard: http://www.newegg.com/Product/Product.aspx...N82E16813131234

graphic card: http://www.newegg.com/Product/Product.aspx...N82E16814130082

power supply: http://www.newegg.com/Product/Product.aspx...N82E16817153052

CPU: http://www.newegg.com/Product/Product.aspx...N82E16819103226

memory: http://www.newegg.com/Product/Product.aspx...N82E16820134117

hard drive: http://www.newegg.com/Product/Product.aspx...N82E16822136075

The new computer has the same hard drive, memory, power supply, and motherboard, differences are that the new one has the 9600gt and the amd 64 5000x2. I have tried the new power supply, while there was no error for the couple hours i used it, the voltages were the same and it checked out fine. When trying the new memory, i did see improvements it seemed on games, no error either, because it only happens randomly sometimes. I do see that like i said when in the bios on the new comp it doesnt have any lag to it just like regular. But on this computer it has a little lag between screens and stuff on bios. Suggestions?

minidumps.zip

[nitroshift]

I had a look at your last minidump (dated 19.03.2008) and windbg says: "Probably caused by : ntkrnlpa.exe ( nt+a9ef2 )". At this point I would say to disable all non-Microsoft start-up items using Autoruns and uninstall any software that install kernel-mode drivers (antivirus, firewall, etc.) and see if the issue happens again. Anyway, I'm sure cluberti can give you an authoritative answer on this, just wait for him to have a look at this thread.

EDIT:

I forgot to welcome you to THE forum!

Edited March 21, 2008 by nitroshift

[cluberti]

Actually, I see a FreePoolWithTag failure in kernel (minidump, can't tell which tag), a MiDeleteAddressesInWorkingSet failure in usermode, a win32k bLockHobj handle lock failure (eip points to an invalid address), 2 ExAllocatePoolWithTag failures in kernel after a call-in from win32k (eax is invalid in both), a SystemFatalException doing a ParseDevice function in drvinst.exe, and a trap on a TimerCallback into NDIS (network).

One thing in common amongst all of these? They've got srtsp.sys loaded on, or just off, the stack, which is the Symantec Endpoint protection product driver. I'd say test the RAM to make sure that it's OK, because these are all over the place, but I'm also very suspicious that the Symantec product isn't causing it - VERY suspicious.

[tortofe01]

Actually, I see a FreePoolWithTag failure in kernel (minidump, can't tell which tag), a MiDeleteAddressesInWorkingSet failure in usermode, a win32k bLockHobj handle lock failure (eip points to an invalid address), 2 ExAllocatePoolWithTag failures in kernel after a call-in from win32k (eax is invalid in both), a SystemFatalException doing a ParseDevice function in drvinst.exe, and a trap on a TimerCallback into NDIS (network).

One thing in common amongst all of these? They've got srtsp.sys loaded on, or just off, the stack, which is the Symantec Endpoint protection product driver. I'd say test the RAM to make sure that it's OK, because these are all over the place, but I'm also very suspicious that the Symantec product isn't causing it - VERY suspicious.

ok i have uninstalled the symantec product, as also somebody else just told me that this could be the issue, i assume u meant that you are suspicious of symantec causing it. I have ran memtest on the RAM once but only for about 2 hours, i will run it a bit longer just to see what happens and will post if i get anymore blue screens. Also while another question while posting here. I tried a different graphic card and the bios lag that i was having went away, would you possibly know why my 8800 causes lag on the bios and the 9600 doesnt?

also thanks for the welcome, glad to be here! =)

Edited March 22, 2008 by tortofe01

[cluberti]

ok i have uninstalled the symantec product, as also somebody else just told me that this could be the issue, i assume u meant that you are suspicious of symantec causing it. I have ran memtest on the RAM once but only for about 2 hours, i will run it a bit longer just to see what happens and will post if i get anymore blue screens.

Yes, I do mean I am suspicious the Symantec driver was causing the bugchecks, but definitely test your RAM to make sure it's OK. Usually when someone gets the same bugcheck code over and over, it isn't RAM, but in your case with the codes being all over the place, it's always good to run a memory test just to be safe.

I tried a different graphic card and the bios lag that i was having went away, would you possibly know why my 8800 causes lag on the bios and the 9600 doesnt?

Not sure why, but it could be video BIOS/RAM shadowing in the BIOS, which you may be able to disable. Otherwise, no.