Recent BSOD events - 2 or 3 per day

Hi all,

I'm a newbie here, although I have lurked a bit and tried some of the suggested fixes for my recent problems. Sorry if this is a long post but I try to give a full description.

The system:
DELL Vostro 1500 laptop with Vista Business SP2 + all updates; bought Nov 2007 with Vista installed. It has not been re-installed.
Avast free AV running in real time (Windows Defender turned off).
Malwarebytes Anti-Malware free version installed, kept up to date and used for weekly scans - not running in real time
PrivateFirewall
Browser: Firefox 3.6.14
The computer is regularly checked and cleaned using CCleaner
I have been running Soluto Beta (Soluto) since last June (without any problem as far as I know).

The problem:

In the last few days (I think it started Monday 28 Feb) my Vista system has started giving me BSOD events 2 or 3 times per day. The system freezes, I get the BSOD but not really enough time to read carefully what the info says.

Action taken so far:

* ChkDsk - no problems reported
* Memory check - no problems reported (twice)
* The C:\ drive had about 10% free space. I've cleared some old files, compressed some photos, generally cleaned up. Now it has 61GB free out of 136GB - and the BSOD still occurs.
* Swapped my Advent wireless mouse for a wired USB mouse (see below)
* Used CCleaner to clean up the Registry and release disk space
* Done a defrag using MyDefrag (MyDefrag v4.3.1)

The problem persists.

I am suspicious about:

* new stuff:
(this is my prime suspect)
A couple of weeks ago I bought a USB-to-parallel adaptor cable so I could use my (trusty) old HP Laserjet5L printer from my laptop. This all worked fine from the moment I plugged it in, but after a day or two started to cause problems - not printing; couldn't find the printer; wanted to keep installing drivers, etc. This occurred more or less at the same time as the BSOD problems. However, I have disconnected the cable and removed the printer from the printer list - still get the problems. Nevertheless maybe there is a faulty driver acquired from goodness knows where. I do not know how to find and delete such a driver. It doesn't show up in any of the obvious places and I don't know where to look for it in Device Manager.

Other new stuff:
I bought a new wireless modem/router (Belkin F5D8636uk4A) about 2 weeks ago. I'm only suspicious because it's new - no other reason. My partner's laptop (identical to mine) is working fine.

The mouse: it seems to me that the BSOD always happens at an instant when I am moving the mouse. Maybe. Although I have had the Advent wireless mouse for a couple of years, I stopped using it (but kept using the keyboard) about a year ago. I recently found it again and have been trying it again for the last fortnight. However, as I said above, now I am using the previous wired mouse, and the BSOD keeps on coming.

I think that's about it. I attach a zip file containing the folder"Windows_NT6_BSOD_jcgriff2" and the PerfMon report, as advised, plus a screenshot of the Windows security centre window, because the PerfMon report claims Windows can't see my Avast AV software. The security centre can see it. Although auto-update is not turned on, I always install updates within a day or so (usually within an hour or so) of notification. (I just don't like the darned thing doing it while I'm waiting for the system to boot up).

Any help/advice most gratefully received! Thanks,

Rob

Welcome
We need the mini dump report, please try to upload again
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Hi,
Isn't that what I attached to my first message? The link you point me to suggest I download Windows_NT6_BSOD_v3.03_jcgriff2_.exe which I have already done, and followed the instructions; at least I think so.

My folder "C:\Windows\Minidump" is empty.

Rob

Rob
The most important file is the minidump. I will try to find information so you can enable the files. Then you can post again with the next BSOD
http://support.microsoft.com/kb/931673

OK, thanks. I've downloaded the Windows debug tools and I think I've set it up so it will save a minidump ("small dump") next time it crashes.

I think Sod's Law says that has fixed the problem. :-)

Well, I hope that you dont find out, because if you do that means you had another BSOD

(Sigh) Well, I suppose looking on the bright side I can score one against Sod's Law. Crash today at 11:43am. I have attached a zipped version of the jcgriffe diagnostics as per the advice. I just hope I made the correct settings yesterday ...

I appreciate your help.

Well, another BSOD at about 17:40 today.

I had previously set the dump option to 'Kernel' from 'Small',and the dump file in C:\Windows\Minidump has not been overwritten. However a file MEMORY.DMP was created in C:\Windows, which I have zipped up - although it is still over 100MB so I have not attached it. But I have attached another jcgriffe diagnostic and another Perfmon report - not sure if it is any use without the minidump.

I'll set the dump option back to Small again.

Rob

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack



The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. Each remedy suggested must be performed regardless of placement in this report or other variables. You may have to experience several more BSODs until the final answer is discovered.
Furthermore, the supplemental reports without the minidump give little evidence as to the cause, so in reality, I am relying on one BSOD

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command


Scan with your Anti Virus
Replace your Anti Virus with Microsoft Security Essentials, be sure to use the uninstall tool for your particular AV


Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If passes try a good stick in each slot for 3 passes
If fails do the same for 8 passes.

Run the upgrade advisor to help discover hardware problems
www.microsoft.com/Windows/windows-7/get/upgrade-advisor.aspx

Be sure that all SPs are installed.

Based upon your particular report these steps must be taken. With luck they will sove the problem. If luck is not on your side following these suggestions and those with the next BSOD will help resolve your problem.

Another BSOD this morning just after 10:00am. Files attached. Actions since yesterday:

Ran Windows memory test - no errors
downloaded and ran MemTest86+ overnight: 17 passes, no errors,
ran SFC - no errors reported
Uninstalled PrivateFirewall and Avast AV, replaced by Windows Security Essentials.
The BSOD occurred during the restart after Windows updates completed and WSE installed.
WSE scan complete - no errors.

Next thing I'll try is to remove the memory cards, clean the contacts and reseat them in case they have come loose. Clutching at straws time.

Rob

Just post any BSODs
I take a look after you complete all the suggestions, given.

Hi Rich,

I have attached a zip file with 10 minidumps from the last few days. Of your previous suggestions:

*******************************************************************************
If overclocking restore normal settings. No overclocking at all

SFC /scannow (System Files - SFC Command) - Done: no problems reported

Replace your Anti Virus with Microsoft Security Essentials, be sure to use the uninstall tool for your particular AV. Done. Completed quick and full scans on HDD + external HDD. Only a minor warning of adware, which was removed. Uninstalled PrivateFirewall and Avast AV, replaced by Windows Security Essentials.

Download memtest86 and test RAM. Run for 8 passes. Done (17 passes - no faults reported)
If passes try a good stick in each slot for 3 passes. There is only 1 stick and 1 slot

The memory stick was reseated.

Run the upgrade advisor to help discover hardware problems. Done. No probelms reported, only advisory to update software for scanner, and a few other standard software if W7 is installed ... but it isn't.

Be sure that all SPs are installed. Done. They were installed as they were released. All routine MS updates have been installed.

*******************************************************************************
Thanks for any further advice,

Rob

There were several reports. Some indicated that this driver was the cause. It will be easy enough to find out; just update the driver.

Pcgenfam.sys file description
Productname: Soluto PCGenome
Description: Soluto PCGenome Core Driver
Company: Soluto LTD.

Now, that I looked at the software, my suggestion is to uninstall. Software like that does not help. If you want my suggestions for a quick, efficient computer, after we solve this problem, just ask.

Thanks Rich. I'm in the process of uninstalling Soluto now. I installed it to see if I could reduce the boot time, which was previously around 3 minutes. I guyess it came down to about 1.5 - 2 minutes, in theory. In fact the delayed applications just started to install after that so the saving was not brilliant. It was interesting to see their analysis, though, and how long each app was taking.

Let's hope it sorts out the problem.

Well, over 48 hours now, with no more BSODs. I think the problem has been solved: many, many thanks Rich.

Now that I know what to look for, I see from the web that other Soluto users experienced BSODs. However I had not experienced BSODs until last week so maybe my config was such that the problem only showed up after a recent Windows update, or installing some other software (although I don't recall what tghat might have been). I believe Soluto have a new release which may have fixed the issue; can't be sure.

Thanks again, Rich.

You are very welcome.
I hope that the puter continues to work well for you.