BSOD - BCcode d1, system health report and NT6_BSOD files attached

My HP Pavilion dv7 is a little over a year old. Original OS was OES, but I had to reinstall it a few months ago and it was fine for a while. Now BSoD is back again, almost daily. Complete computer info was provided when I registered for this forum, but I'd be happy to provide it again.

Zipped NT6 and System Health check files are attached.

Here is the BSOD info:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 000000000000001C
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF88001A9F87E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


Here is the info from the Event Viewer on the Critical Event that occurred today.

System

- Provider


[ Name] Microsoft-Windows-Kernel-Power


[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}



EventID 41


Version 2


Level 1


Task 63


Opcode 0


Keywords 0x8000000000000002

- TimeCreated


[ SystemTime] 2012-01-02T17:08:29.392015700Z



EventRecordID 3471423


Correlation

- Execution


[ ProcessID] 4


[ ThreadID] 8



Channel System


Computer Shelley-HP

- Security


[ UserID] S-1-5-18

- EventData

BugcheckCode 209

BugcheckParameter1 0x1c

BugcheckParameter2 0x2

BugcheckParameter3 0x1

BugcheckParameter4 0xfffff88001a9f87e

SleepInProgress false

PowerButtonTimestamp 0

Any help you could provide would be greatly appreciated.
Thanks,
Shelley

Crashes Related to KmxAMRT.sys Antivirus File System Filter Driver for XP/2003 from Computer Associates. For XP/2003 NOT for win 7. Needs to be removed and replaced at least to test.

Microsoft Security Essentials - Free Antivirus for Windows

zigzag3143 said:

Crashes Related to KmxAMRT.sys Antivirus File System Filter Driver for XP/2003 from Computer Associates. For XP/2003 NOT for win 7. Needs to be removed and replaced at least to test. Microsoft Security Essentials - Free Antivirus for Windows

Computer Associates says the package is compatible with Windows 7 Professional 64-bit, which is what I have. I've had the CA package since day 1 without a previous problem. Why would this problem start to occur recently? Do you suggest I uninstall the entire program and reinstall it? or ?

skarber said:

zigzag3143 said:

Crashes Related to KmxAMRT.sys Antivirus File System Filter Driver for XP/2003 from Computer Associates. For XP/2003 NOT for win 7. Needs to be removed and replaced at least to test. Microsoft Security Essentials - Free Antivirus for Windows

Computer Associates says the package is compatible with Windows 7 Professional 64-bit, which is what I have. I've had the CA package since day 1 without a previous problem. Why would this problem start to occur recently? Do you suggest I uninstall the entire program and reinstall it? or ?

If CA says it is compatible it probably is (I do wonder about the files description though).

Anyway. It isnt one of the most frequently seen malware apps but in this particular case it is a direct connection.

BSOD's are Always a combination of events so it may have been fine untill the last thing you installed made the interaction unstable.

I would un-install it completely to test as often just disabling it does not turn it off.

You can always re-install it (if you like) when the problem is solved.

Thank you zigzag3143. I've completely uninstalled CA, and loaded Microsoft Security Essentials. I'll watch for a week or so. If the BSoD problem does not reoccur, I will come back and report the problem as solved. Thanks again!

skarber said:

Thank you zigzag3143. I've completely uninstalled CA, and loaded Microsoft Security Essentials. I'll watch for a week or so. If the BSoD problem does not reoccur, I will come back and report the problem as solved. Thanks again!

Fingers crossed, good luck.

A week later and no problem since uninstalling CA. Your help was great!

Thanks again,
Shelley

skarber said:

Thank you zigzag3143. I've completely uninstalled CA, and loaded Microsoft Security Essentials. I'll watch for a week or so. If the BSoD problem does not reoccur, I will come back and report the problem as solved. Thanks again!