|09 Nov 2010||#1|
| || |
Windows 7 BSOD report
Windows 7 . . .
- Ultimate Edition x64
- Not the original OS installed, I believe I was using Vista previously
- Full retail ver.
- Age of system/hardware is about a year and a half? Year old?
- OS installation may be about six months old, I installed it after a fresh format
In possibly related news, I noticed some three months ago or so that my 12gb of installed RAM is now registering as 8gb. I'm pretty sure it originally detected 12gb. When I boot up into BIOS, I only see 8gb. When I run CPU-Z I see 12gb. Other than PHYSICALLY HAVING 12 darn gigs of RAM I'm unsure whether the RAM itself is bad, bent mobo cpu pin (doesn't seem any are bent), or what... and now this BSOD has me very curious of my machine's intentions
The performance monitor didn't seem to register my anti-virus, which is Avast! Free version
(I'm not sure if this info is in the dump file or not)
RAM Info: DDR3, triple channel
nb frequency 2128 MHz
DRAM frequency 532MHz
|My System Specs|
|09 Nov 2010||#2|
| || |
Not much info in the attached files. Please do the following:
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 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)
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/Windows 7 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:
Delete these registry keys (works in XP, Vista, Windows 7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Nov 9 13:17:09.114 2010 (UTC - 5:00) System Uptime: 0 days 0:02:00.316 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 ) BUGCHECK_STR: 0x1a_41790 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: aspell.exe Bugcheck code 0000001A Arguments 00000000`00041790 fffffa80`04cb2ee0 00000000`0000ffff 00000000`00000000 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
|My System Specs|
|Similar help and support threads for2: Windows 7 BSOD report|
|Report .rar witch SF Diagnostic Tool file BSOD Windows 7 Ultimate x86||BSOD Help and Support|
|BSOD Plannetside 2 (steam) black screen> reboot> BSOD crash report||BSOD Help and Support|
|Yet another BSOD report||BSOD Help and Support|
|Bsod report||BSOD Help and Support|
|Random BSOD... Help please (BSOD dump & system health report attached)||BSOD Help and Support|
|Windows won't shut down! BSOD report included||BSOD Help and Support|
|BSOD windows 7 64 bit home prem. *report files included*||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
й Designer Media Ltd
All times are GMT -5. The time now is 11:17 PM.