FWIW, I woke up today to a BSOD on one computer caused by pxrts.sys. It took a couple reboots to get Prevx to load after that. A daily scheduled scan had already run. The STOP error was 0X0000008E. I've researched the common causes for this STOP error... memory failing, missing Service Pack or some hardware component needs replacing. Just thought I'd post it, like I said, FWIW.
Hi Page, Could you look through the folder C:\Windows\Minidump\ and send any .dmp file to report@prevxresearch.com? pxrts.sys is one of our components so it looks like there is an incompatibility on your PC which we are definitely keen on fixing! Thanks for the help
Okay Joe, the same BSOD this morning. I'll send the minidump to the address you noted, with a link to this thread. Good luck, and thank you.
Hi Page, I've found the issue - bit of a bizarre one! It will be fixed in the next build Thanks for the crash dump!
That's good because the BSODs are coming each day now. I have 4 Event Viewer errors saved that appear to be from around the time the blue screen happened, if you are interested.
BSOD with 3.0.5.98 after one day. This time no mention of pxrts.sys. STOP: 0X000000F4 I have a minidump file that I will email to report@prevxresearch.com. Thanks
I don't see Prevx referenced in this minidump at all, however, could you let me know if you've been using hibernation and resuming from there?
Hi Page, Sorry that you are having so much trouble if going back to 3.0.1.65 does not solve the problem you should run Check Disk as DavidCo said it could be a Hard Drive problem and running Check Disk could find and repair errors http://www.techspot.com/vb/all/windows/t-65491-STOP-0x000000F4-Error.html and here http://support.microsoft.com/kb/330100 In my case I'm using Windows 7 it says Error Checking! TH
Thanks for you help and concern, TH. I have run chkdsk a couple of times on that HD just recently as part of Puran's Boot Time Defrag. No problems showing... with files, indexes, security descriptors or usn journal. I am now running the additional 2 passes that scan for and attempt to recover any bad sectors. No Event Viewer errors have pointed at the HD or have suggested I run chkdsk, so I have been looking elsewhere. 3.0.1.65 never gave me a blue screen. I'll see if that is the case now that I have reverted back. I don't want to blame Prevx if Prevx is not at fault. Just trying to get to the bottom of this.
It's all good... A disk check has been scheduled. Windows will now check the disk. Cleaning up minor inconsistencies on the drive. Cleaning up 2 unused index entries from index $SII of file 0x9. Cleaning up 2 unused index entries from index $SDH of file 0x9. Cleaning up 2 unused security descriptors. CHKDSK is verifying Usn Journal... Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 0 KB in bad sectors.
Heck no. I said "I'm going to go back to 3.0.1.65 and see if the blue screens continue", and you guys mentioned chkdsk, so I posted that the chkdsk is all good. I have to give 3.0.1.65 at least a week test to see if and BSODs occur. (I don't think that they will.) I can say right now that with 3.0.1.65 back on that machine, all of the sluggishness on boot-up, and the intermittent failures to load both Prevx processes are once again gone. I've rebooted about a dozen times since putting 3.0.1.65 back on, and Prevx loads each and every time, whereas with every build after 3.0.1.65, it was hit and miss... in addition to the bsods and the occasional message that Prevx has encountered a problem and must shut down. The difference in performance on the computer is noticable. And I want the blue screens to go away!
I have emailed another minidump to you, Joe. This BSOD came yesterday with 3.0.1.65. I wanted to see if I could eliminate hardware failure from the picture, so in addition to the chkdsk I ran the other day, today I ran a Microsoft Windows Memory Diagnostic tool that will also identify hardware failure besides memory. The computer passed all 8 tests with no failures. My understanding is that there might still be a hardware problem that these tests aren't uncovering, but at least I have conducted a few basic tests that have come up clean. I tried changing a few things like reseting the page file (based on Event Viewer errors) and I hope to hear back from Joe on the recent minidump as to whether or not he sees any Prevx-related issues in there. Next step (if blue screens continue) is to remove Prevx from that machine.
