Hi all,
I get a BSOD but I do not know the root cause.
The content of the minidumps is more or less meaningless to me. I do not know where to start searching. Also the event logs are not very helpful to me.
According to the BSOD - Posting Instructions I created the required file and attached them to this post.
Thanks for your help!
The perfmon report states that your Bluetooth is disabled. Is this deliberate? If so, why?
25 memory dumps from 20 May to 21 Nov 2010 (6 months)
MSINFO32 places the blame for some of your BSOD's on your Intel graphics card. Please do the following:
- download the latest Win7 version of the drivers for your graphics card from the manufacturer's website
- uninstall the current drivers on your system
- install the freshly downloaded drivers
- monitor for further BSOD's
More to follow once the memory dumps finish running.....
This is possibly a driver issue or possibly a hardware issue. So, let's try this....
I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Please update your webcam driver (the current one is from 2008). Please remove the LogMeIn/Remotely Anywhere program as it's drivers date from 2007 and 2008.H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)
Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
There are some very unusual drivers on your system. It may be worth your time to submit them to Jotti's malware scan to see if they are infected. They are most likely located in C:\Users\Annette\AppData\Local\Temp\ (the AppData directory is hidden so you'll have to enable viewing of hidden files/folder in Windows explorer)
Here's the list:
If that doesn't flush out the culprit, then please run Driver Verifier according to these directions:003A4E5.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
003333F.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
0039B83.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
003E3AA.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
00358F9.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
003691E.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
0036E6B.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
0038BFA.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
0036D52.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
0032922.tmp Thu Aug 26 19:59:43 2010 (4C76FFEF)
002EDD7.tmp Mon Jul 19 09:13:48 2010 (4C444F8C)
002E704.tmp Mon Jul 19 09:13:48 2010 (4C444F8C)
002B4BE.tmp Mon Jul 19 09:13:48 2010 (4C444F8C)
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced usersCode:Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Hi usasma,
thanks for the detailed analysis and the advice.
Here some comments from my site:
1. Memtest: I performed an overnight memtest already before my post. I used Memtest86+ for that, exactly like suggested. --> no errors
2. I also did HD tests. Not exactly like described but I performed chkdsk and found no errors, thus I downloaded the WD diagnostic tool and performed a full test. --> no errors
3. Malware: I run a full virus scan with my anti virus tool (MS Essentials), but I did not run the suggested Malware test yet. I will still do that.
4. Strange tmp files: Unfortunately the listed tmp files are not on my system. anymore.
I do not know how they could disappear, but they are gone.
5. Driver Verify: This sounds like a real adventure, for real cowboys. :) And I do not know if I'm brave enough to do that.
6. LogMeIn: I found another graphic driver, it was called "LogMeIn Mirror Driver". The LogMeIn unsinstaller did not remove this driver, thus I did it explicitly from the Hardware manager. I did this some days ago and had no BSOD since than. So I will give it a view more days, maybe this was the culprit. If not, I will perform the Driver Verifier cowboy :) stuff.
7. Bluetooth: I disabled this device for now, since it showed any issue in the Hardwaremanager. Since I am not using blue tooth I disabled it to see if the BSOD stops.
What do you think?
Thans
Strange Temp Files - well, they're supposed to be Temporary, so it's reasonable if they're deleted.
Driver Verifier - it's supposed to sound intimidating because on the rare occasions that it won't boot back up, it's a royal pain to get back into Windows.
Here's hoping that it was the LogMeIn driver.
Good luck!
Hi usasma,
I gave the driver verifier a try, because the BSOD's still happen.
I activated the verifier with the settings described above and stressed the Netbook for 3 days. No BSOD, but when I plug in a SD card the mouse pointer disappears and the system hangs. When I disable the verifier I can again plug in the same SD card and can use it. Activating the verifier again, the system hangs again when I plug in the SD card. I assume, that the driver responsible for the SD card reader is maybe buggy, but how to verify the assumption and how to solve the problem. Any suggestions?
Happy new year.
Please generate the reports again and post them for us to have a look at. Since Driver Verifier didn't point out the issue, we'll have to look at the reports to see if something was mentioned in one of the logfiles.
Quote