Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY

09 Nov 2013   #11
bsfinkel

Windows 7 Professional 32-bit
 
 

I have not uninstalled ASC6 (except to replace it with the newer 7.0.5). I have not had a BSOD that I can attribute to anything ASC did.

As for recent BSODs (after the READONLY_MEMORY BSOD that is the subject of this problem report:

11/03/2013 00:52 BSOD: (74) MEMORY MANAGEMENT (1a) 41289 third occurrence
11/04/2013 01:13 BSOD: (75) BAD_POOL_CALLER (c2) 7 second occurrence
11/06/2013 08:55 BSOD: (76) NTFS_FILE_SYSTEM (24) 001904fb third occurrence
11/08/2013 11:33 BSOD: (77) DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) storport.sys first occurrence

These are all different, and I see no pattern. That is why I call my BSODs "seemingly random".
--Barry Finkel


My System SpecsSystem Spec
.
10 Nov 2013   #12
x BlueRobot

 

Could you please upload the resulting dump files?
My System SpecsSystem Spec
10 Nov 2013   #13
bsfinkel

Windows 7 Professional 32-bit
 
 

I have uploaded the current output of SF diagnostic tool. And as an extra "bonus" there is a BSOD from this morning:

11/10/2013 05:41 BSOD: (78) BAD_POOL_HEADER (19) i20 mage name=win32k.sys

That is my tenth BAD_POOL_HEADER (19) Arg1=00000020 BSOD. I am not sure that they are all caused by the same driver/program. This was the first one with this image name.
--Barry Finkel
My System SpecsSystem Spec
.

11 Nov 2013   #14
x BlueRobot

 

Code:
BugCheck 19, {20, fe437160, fe4371a8, 4a090001}

Probably caused by : win32k.sys ( win32k!WMsg_midl_user_free+10 )
Code:
1: kd> dt nt!_POOL_HEADER fe437160
   +0x000 PreviousSize     : 0y000000001 (0x1)
   +0x000 PoolIndex        : 0y0000000 (0)
   +0x002 BlockSize        : 0y000001001 (0x9)
   +0x002 PoolType         : 0y0100101 (0x25)
   +0x000 Ulong1           : 0x4a090001
   +0x004 PoolTag          : 0x6c6d7355
   +0x004 AllocatorBackTraceIndex : 0x7355
   +0x006 PoolTagHash      : 0x6c6d
Code:
1: kd> dt nt!_POOL_HEADER fe4371a8
   +0x000 PreviousSize     : 0y000000000 (0)
   +0x000 PoolIndex        : 0y0000000 (0)
   +0x002 BlockSize        : 0y001001100 (0x4c)
   +0x002 PoolType         : 0y0100011 (0x23)
   +0x000 Ulong1           : 0x464c0000
   +0x004 PoolTag          : 0x35616c47
   +0x004 AllocatorBackTraceIndex : 0x6c47
   +0x006 PoolTagHash      : 0x3561
We can see that the _POOL_HEADER data structure has become corrupt, the Pool Header of next entry's PreviousSize field doesn't match the BlockSize field of the pool entry which which was being checked within the pool page.

This is pretty much caused by drivers.

There's still a few programs and drivers on your system, which were causing problems in your previous thread.
My System SpecsSystem Spec
11 Nov 2013   #15
bsfinkel

Windows 7 Professional 32-bit
 
 

I am not sure what you mean. "There's still a few programs and drivers on your system, which were causing problems in your previous thread." The drivers that have definitely been implicated on previous BSODs have been removed or replaced. These are cbufs.sys, wrkrn,sys, and the nVIDIA graphics driver. Other BSODs are probably caused by bad drivers, but we have not implicated a specific driver in any of the unresolved BSODs. One of my brothers is "convinced" that my problems are due to the VIA IDE card in my computer. He says that because I changed motherboards last May, and, besides the video card, that is the only other card in my machine. I do not agree with him.

Here are the non-MS drivers as seen by verifier:

amdxata.sys - AMD Storage Filter Driver
bdisk.sys - COMODO
cbreparse.sys - COMODO Cloud
cbvd.sys - COMODO
vdbus.sys - COMODO BackUp Virtual Disk Bus Driver
dump_atapi.sys - ?? IDE Port Driver
dump_dumpata.sys - ?? Parallel ATA
dump_dumpfve.sys - ?? Full Volume Encryption Crashdump Hibernate Filter
e1e6232.sys - Intel(R) PRO/1000 Adapter NDIS 6 deserialized driver
eubakup.sys - EaseUS-Backup
eubkmon.sys - EaseUS-Backup
ndis.sys - Microsoft
vsmraid.sys - VIA RAID Driver

The vsmraid.sys driver is for my VIA IDE card, but I do not use the RAID feature. The VIA web site says that the IDE drivers in use for Windows 7 is the MS-supplied driver. I have just renamed the four COMODO drivers, as I no longer use COMODO. I will reboot to see if there are problems with the renames. The other drivers seem to be needed on my system. And I don't agree with the statement - It is not necessary to test MS drivers; they do not cause problems.
It could be a MS driver that has caused one or more of my BSODs. I did a Google search last week on one of my BSODs, and I saw a hotfix for stream.sys (kb2661796). I downloaded the hotfix, and when I run it it asks me for a directory into which to unzip. Then it completes immediately. There is nothing new in the unzip directory, nor has stream.sys been updated. I have rebooted after the "install". I have no idea what is happening when I install that hotfix. I have no idea how many driver hotfixes have been written by MS for Windows 7 Professional, but have not been released on patch Tuesdays because they are not pervasive problems. This one hotfix was from early 2012.
--Barry Finkel
My System SpecsSystem Spec
12 Nov 2013   #16
bsfinkel

Windows 7 Professional 32-bit
 
 

One quick update - the reboot after the rename of the four COMODO files had two problems. First, a "BAD_POOL_HEADER (19)" BSOD during shutdown (I have experienced this before), then a repeasted "(7b)" BSOD during reboot. After multiple reboots into XP to un-rename and re-rename, I determined that bdisk.sys is need to boot, and I have to determine why this COMODO driver is needed. None of the four COMODO drivers is currently in the verifier list. The other three COMODO drivers have been successfully renamed, and can't be loaded.
--Barry Finkel
My System SpecsSystem Spec
13 Nov 2013   #17
x BlueRobot

 

I don't understand, why you won't simply remove the Comodo program if your not using it?
My System SpecsSystem Spec
13 Nov 2013   #18
bsfinkel

Windows 7 Professional 32-bit
 
 

It is true that I no longer use Comodo Backup to make backups of my disks. But I do have prior backups, and there may be a time in the future when I may need to restore a file from one of those backups.
--Barry Finkel
My System SpecsSystem Spec
14 Nov 2013   #19
x BlueRobot

 

Just download a better backup program, and then create new backups.
My System SpecsSystem Spec
14 Nov 2013   #20
bsfinkel

Windows 7 Professional 32-bit
 
 

I HAVE installed a new backup program, and I am using it. But, if I have to restore a file back from last July, for example, that file will NOT be on a backup tape created today or last week. That is why I have not uninstalled Comodo Backup. I have renamed the driver file that caused at least one of my BSODs, so that driver file will not be loaded and will not cause another BSOD. If the offending program were any other program, I would have no qualms about uninstalling it. My main concern right now is to determine the causes of my seemingly random BSODs. Besides the one caused by cbufs.sys and the ones caused by nVIDIA graphics driver timeouts, I have nor determined a definitive cause for any of my other BSODs. I do not know enough about the internals of Windows 7 nor all of the various windbg commands to be able, on my own, to look at a dump (full or mini) and pinpoint the offending program.
--Barry Finkel
My System SpecsSystem Spec
Reply

 Random BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD problems in the past 2 days. Random errors at random times
Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty...
BSOD Help and Support
BSOD at seemingly random times, memory dump blaming random drivers
I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into...
BSOD Help and Support
Random BSOD at random moments on Toshiba L500 laptop; graphics card?
My GF has had a Toshiba L500 laptop for 4 years now. It's a great model and it worked well...till now. It started about two weeks ago, with 1 blue screen every 1-2 days. I haven't reinstalled her windows for about a year, so i figured that was the problem. Four days ago it started blue...
BSOD Help and Support
Attempted_write_to_readonly_memory bsod
I had a game minimized idling (which ive done for a long time) and came back to this BSOD This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xBE (0x80000, 0x9810000417680025, 0xFFFFF8800944B330, 0xA) Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY...
BSOD Help and Support
Random BSOD with random error code at random moment
Hello Ok now i'm out of solution so i come here hoping that someone could help me I always had bsod hapening randomly but not like the this week I got 2 bsod/day when i'm playing, when i'm staring at my monitor or even when i'm sleeping with random error code like 0x1e, 0x24, 0x3b, 0x4a or 0xa...
BSOD Help and Support
Random BSOD Attempted_WRITE_TO_READONLY_MEMORY
Hi i got 8 repeated BSOD and then suddenly after a restart today the computer stopped bsoding... for now. I was just wondering if anyone saw something out of the minidumps i attatched that i did not see.
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App