Windows 7 is crashing on a regular basis while the Laptop is not being used. That is, sitting idle. There maybe some processes running, but haven't had time to look that closely.It is abending with a messageDRIVER_IRQL_NOT_LESS_OR_EQUALI am running W7 on an Acer Travelmate 8200.All was running ok for the first couple of weeks after installing W7. I put on a product from Western Digital called MIONET to look at a WebSphere drive, but this product is not always running when the Laptop Blue Screens.The Abends happen within about 5 minutes of everything initialising.Also, I have found the curser pad "scroll" features don't work under W7 for the Acer.

I had a similar problem on my laptop - turned out to be linked to the wireless card/anti virus. If I disabled the wireless everything worked fine, but somewhat irritating. Then discovered that if I uninstalled AVAST which is the antivirus I installed, and replaced it by AVIRA - problem was solved! Have not had a blue screen in more than a month!

Hi RappoThis blue screen is coming from a hardware driver. Nothing has to be running to cause this, it could be the driver for the display device, NIC device, or....?If you take a good look at the Blue Screen, sometimes you will see the name of the faulting driver. It should be a file name with the .sys extension.Other than this, the only way to identify the faulting driver is to debug the memory dump files. This is something we are not able to do on these forums.One thing you can do is check for updated drivers for all of the installed hardware.Hope this helps.Thank You for testing Windows 7 Beta Ronnie Vernon MVP

I am able to provide basic help with memory dump analysis'Follow the instructions at this link: How to read the small memory dump files that Windows creates for debuggingPost back with the results of the analysis (particularly the output of the !analyze -v command) and we'll see what we can figure out.Please be advised that BSOD analysis is an inexact process - and it may take repeated memory dumps to identify a trend, and may require using other tools (and the risks involved with that). IME it works easily a lot of the time - but there's other times that it's searching for a needle in a haystack.Good luck!- John

Also, check your memory using either the built-in memory diagnostic, or the more thorough and visually communicative Memtest86 (recommended). A coworker who upgraded his sons desktop from XP to Vista SP1 was experiencing the same thing. The culprit turned out to be a bad (a very bad) 1 GB module. Once replaced, the system became as stable as a brick. Do thin in addition to checking your drivers.