New
#21
Random BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY
-
-
New #22
I will stop using ASC if and when it is implicated as the source cause of any of my numerous BSOD occurrences.
--Barry Finkel
-
New #23
Hi bsfinkel.
Can you update the VIA VT6421 RAID Controller to version 6.10A dated 13-May-2011?
VIA Drivers Download - VIA Technologies, Inc.
Also, try to update the chipset from Chipset: Intel® Chipset Device Software for Discontinued Intel® Desktop Boards which works for your Intel® Desktop Board DP965L.
Finally WD3200KS-00PFB0 dcm DBCACAJAA Western Digital 320Gb, the HDD needs to be checked .... check it with Data Lifeguard Diagnostic for Windows.
Let us know the results.
And, one more information for you ... the last entry from your event log .....
This condition persists, as a great lot of the earlier events are saying the same thing. And, IMHO, it is all behind your issue, despite of what I have suggested.Event[34999]:
Log Name: System
Source: Microsoft-Windows-FilterManager
Date: 2013-06-21T08:54:54.437
Event ID: 4
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: BarryFinkel-PC
Description:
File System Filter 'CFRMD' (Version 6.1, ?2012?-?07?-?17T00:05:30.000000000Z) failed to attach to volume '\Device\Harddisk0\DR0'. The filter returned a non-standard final status of 0xc01c0016. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.
EDIT: About Advanced System Care ..... it is a crapware. It can cause windows installation damaged beyond repair by normal course of actions, but it does not cause any BSOD ever.
Cautious people keeps away from it, but if you have the ability to control the program at your own (many people have, so you also may have), you can use it. I have TuneUp Utilities installed. I know how deadly it is, and I learned how to control it and use it at my own way. But still I suggest to keep away from those programs, as we dont know the efficiency level of other users.
-
New #24
VIA VT6421 drivers - I was unable to access that driver page, but another page VIA Technical Support FAQ - VIA Technologies, Inc. has this text:
Windows 7
A lot of driver support for VIA chips is built into Microsoft(R)
Windows(R) 7 (32- and 64-bit). If you're looking for Windows 7
drivers, please check these FAQ first.
VIA Chips Driver status for Windows 7
VT6421 Support for IDE, SATA and RAID are included in Windows 7.
No driver updates are currently available.
Installing the latest V-RAID driver will update the RAID
utility only and not the driver.
----------------------------------------------
Intel Chipset - I had previously downloaded that executable and ran it on Aug 26. It was not clear that it updated any drivers. I re-ran it, and it produced a message stating that I already have version 9.40.1017 installed; do I want to revert to 9.1.2.1008? I replied. "No". My records show that I had installed 1017 on Jun 27. I get confused by the Intel chipset web site, so I an not sure that I have the latest chipset drivers installed.
--------------------------------------------------------------
WDC Data Lifeguard Diagnostic - I ran it on each of my three WDC hard drives. I did the quick scan of my SATA boot drive; I ran a full check on my other two IDE drives. No problems were reported. Here are the SMART values for the SATA drive:
Thre- Warr
Attribute Name ID Value shold Worst anty
------------------------------- -- ----- ----- ----- -----
Raw Read Error Rate 1 200 51 200 1
Spin Up Time 3 185 21 182 1
Start/Stop Count 4 100 0 100 0
Re-allocated Sector Count 5 197 140 197 1
Seek Error Rate 7 200 51 200 1
Power On Hours Count 9 20 0 20 0
Spin Retry Count A 100 51 100 1
Drive Callabration Retry Count B 100 51 100 1
Drive Power Cycle Count C 100 0 100 0
Airflow Temperature BE 65 0 46 0
HDA Temperature C2 115 0 96 0
Relocation Event Count C4 198 0 198 0
Current Pending Sector Count C5 200 0 200 0
Offine Uncorrectable Sector Count C6 200 0 200 0
UltraDMA CRC Error Ratge C7 200 0 200 0
Multi Zone Error Rate C8 200 51 200 1
The utility claimed that this SATA disk passed the SMART value test.
---------------------------------------------------
Event Log CFRMD entry - I have seen lots of these in the Event Log before, but I really did not know how to interpret them. For one thing, the Event Log uses a Unix-style disk identifier notation - "'\Device\Harddisk0\DR0", and that does not tell me what disk is involved. Also, the CFRMD.sys routine is part of Comodo, and I renamed that driver file on September 22 after I was no longer using Comodo as my backup utility.
--Barry Finkel
-
New #25
About Intel Chipset, I am not very sure what you are saying. As far as I can remember, I noticed your chipset is old enough, when I checked your data two days ago.
About comodo, if you dont use it, uninstall it. If the drivers are remained there, delete them.
About VIA: See what I have entered:
Attachment 293981
And then what came out:
Attachment 293982
Is not it the driver?
-
New #26
VIA VT6421 Controller Drivers - Win 7
Look at the attached JPEG image - specifically at the notes section. "Please also note that installing this driver on Windiws 7 (32 and 64) will not update the driver, it will only update the RAID utility." And when I look at the readme that is unzipped, I see that Windows 7 is not mentioned in the category "viarAID: rAID dRIVER FILES". This will only update "RAIDTOOL: RAID Management Tool files". And I do not use RAID.
Somehow, when I did a cut-and-paste of some upper-case text, this web form decided that all of the text has to be in upper-case, and I see no option to change back to mixed case.
as for comodo - I have written before. if i know that I will *never* need to restore a file that is on a comodo backup, i will uninstall comodo backup.
About the Intel chipset - I have not found a later chipset than 9.4.0.1017.
--Barry FInkel
-
New #27
You are difficult :)
You know what is your issue. And you have your reason to continue with the problem causer. Then what remains in troubleshooting logically?
-
New #28
I really do not understand your reply. YOu say that I continue to use "the problem causer". I have not seen in any replies an EXACT cause for my various seemingly random BSODs. except for one that pointed to CBUFS.sys and one that pointed to wrkrn.sys. Once that CBUFS driver was pinpointed as a cause, I switched to another backup program and renamed cbufs.sys. The Event Log pointed to a Comodo indexing task (CFRMD) last June. But since I am no longer running Comodo, I do not have those Event Log entries. And when I saw that WebRoot was the cause of a BSOD, I contacted WebRoot, and then gave me new code to install.
Are you saying that my use of Advanced System Care, which attempts to remove old registry entries, is causing my BSODs? If this were the case, then others who use ASC (and there are many) would be experiencing seemingly random BSODs.
And my VIA 6421 IDE card, which has no Windows 7 drivers of its own (it uses the MS-supplied drivers)?
I see BSODs where the Image Name is ntkrpamp.exe, part of Windows kernel. I assume that some of my BSODs are due to errors in MS code that MS has corrected but not released as regular monthly patches. I tried installing one, but it did not update the stream.sys driver as expected.
--Barry Finkel
-
New #29
Barry, my friend, please listen. If you find anything that we are saying that is not clear enough, just ask, the explanation will be there at our best.
ntkrnlmp.exe (or ntoskrnl) is the karnel on which the BSOD took place. All BSODs take place on that very karnel. When the crash dump recording mechanism is not able to detect a prima facie cause to show as "probably caused by", it blames the karnel itself by mistake or by default. It is not the issue, and it can never be an issue.
Advanced System Care (or any other registry cleaner) is not efficient enough to handle Windows 7 registry (there is an exception, CCleaner). They can make various damage. They can wipe up a lot of important system resources (like imageres.dll malfunction or wiping up C:\Windows\Installer) and that damage is beyond repair without a repair install at least. But they does not cause any BSOD at all. You should not use ASC, but it is not contributing to your BSODs.
RAID drivers are always problematic. Everywhere. Specially when you are using VIA raid drivers which is pretty much out of market and not having updates. In such a situation where your disks are not set in a RAID array. So, it is clear that you need not to use RAID drivers, knowing that those are problematic storage controllers, and your BSODs are caused by storage controllers.
BUT, the pointed out issue is Comodo. For sake of the issue you should totally uninstall it. At the same time you have your own necessity to keep comodo there. And it is the point (alongwith VIA) that I said in my earlier post.
Hope it is clear to you now? If not, you may ask again.
Frankly speaking, your issue is determined that is clear. Now, decide what you need. Unfortunately, we cannot provide any real help with the problematic elements present in the system, I think you can understand it.
If you decide to keep the present setup, it is expected that you will experience BSODs.
If you perform a clean installation with RAID disabled and AHCI enabled + minus Comodo, you can expect a crash free computer, hopefully.
Your decision, your action. We just can explain the situation to you. We cannot prevent the BSODs in the present state. We dont have that power or ability.
-
New #30
As Arc has already pointed out, the Windows Kernel is usually blamed by default if a exact driver isn't able to be located, or a driver has incorrectly called or used a Windows API function. Almost every single dump file will point to ntkrnlmp.exe or ntoskrnl.exe.
We can tell you what is happening and what is the problem, but we can't force you to follow our suggestions (from evidence), it's up to you to follow our suggestions when we give them.
Windows 7 is internally completely different from the days of Windows 95 and Windows 98, and even Windows XP. The security of the operating system has improved immensely, and important data structures now have been protected from problematic drivers.
I've been giving you, almost the exact same advice since the summer - Bsod bad_pool_header (19)
Quote
Related Discussions