I had another bsod, but I mistakenly posted the info in the old thread, then remembered I should start a new one. The old thread is here post #12 I believe.
EDIT: this may also help
Attachment 122673
Last edited by essenbe; 11 Dec 2010 at 16:04.
Unfortunately the last DMP didnt identify the offending driver.
What AV are you running? Are you overclocking? running a raid?
Please run driver verifier to find the offending driver
Beyond that, please run Verifier with these settings:
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).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 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:
Code: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
Using Driver Verifier to identify issues with Windows drivers for advanced users
I restarted with driver verifier started and no blue screen. I do not overclock, am not using raid ( it is enabled in BIOS) and am using MSE now. I used to use Norton 360 but read here that it can cause bsods. I have an SSD. I uninstalled Norton, did a secure erase of the SSD, reinstalled Windows 7 (custom install) and downloaded MSE. I have very little on this drive at this point. If you like I can give you a list of installed programs. BTW, without raid enabled in Bios my CD/DVD will not work - don't ask me! but that's the way it is.
If I understand you, at this point I do not keep restarting, just use in normally but leave it running. is that correct?
I have not crashed yet. But, I don't think I was able to download this file to you. I seem to have problems with 7zip, but anyway here it is.
Attachment 122691
Try copying the dump to your desktop, then right-clicking on it and selecting Send to > New compressed folder.
did you not get the folder I attached? I thought I knew my way around a computer O.K., but I sure didn't see tat one!
Attachment 122715
see if this works
It came through okay, though I am not equipped to extract .7z files. I can work with .rar and .zip files, however.
I suspect hardware is the cause here. Try testing RAM first: RAM - Test with Memtest86+
Then do CPU: https://www.sevenforums.com/tutorials...t-prime95.html
Next Furmark: Video Card - Stress Test with Furmark
...Summary of the dumps:
Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Dec 11 16:09:37.092 2010 (UTC - 5:00) System Uptime: 0 days 1:50:19.419 Probably caused by : luafv.sys ( luafv!LuafvNormalizeNameComponentEx+fa ) BUGCHECK_STR: 0xC5_2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0xC5_2_luafv!LuafvNormalizeNameComponentEx+fa ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Am I reading that right? Is it saying that it was caused by laufv.sys. According to what I can find on my computer it says that lufav is a UAC File Virtualizatio File System. I have no idea what that means. I have run memtest86 4 times now. In the last thread I explained that about 2 weeks ago I ran it and found 2 bad sticks and removed them. I have tested the remaining 2 sticks several times, in fact I ran it for about 3 hours this morning with no errors.
What do you suggest? should I keep running this verifier test or stop it and run the other tests, and if so which one do you think is most likely the cause? BTW, I do not have a graphics card. I am using integrated graphics.
Are you testing both sticks at the same time, or individually?
Go ahead and disable driver verifier: Driver Verifier - Enable and Disable
I still recommend Prime95 and Furmark; it does seem like a hardware problem.
Quote