|26 Sep 2010||#1|
| || |
bsod related to another thread
I just had a bsod on my system and I'm pretty sure it's related to my other problem in http://www.sevenforums.com/crashes-d...ctivity-3.html
To respect the rules:
- three days old x86 win 7 retail version
- the components age differ but they've all been tested and work well (one exception - the hdds, and lately I realized the o/s hdd reaches 60 degrees Celsius under load)
|My System Specs|
|26 Sep 2010||#3|
| || |
Please uninstall Daemon Tools, it has some issues with some Windows 7 installations. If desired you can reinstall it AFTER we've finished troubleshooting your issues.
The BSOD appears to reference a Windows component in your video sub-system. As this is a new installation of Windows, it's unlikely that this is at fault. So, I'd have to wonder about your video drivers and video card at this time. Do you have the same problems when booting into Safe Mode?
Your video drivers appear to be current ( nvlddmkm.sys Fri Jul 09 17:15:14 2010 (4C379162) ), so I have to suspect an issue with your video card. In your other post you state that the system has passed hard drive and memory diagnostics, so we won't try them again. But, since you've related issues with overheating of the OS drive, I'd like you to try the Seagate Seatools test on the OS drive. It checks the drive for overheating conditions (it's in the notes, so check carefully). Here's a link to HDD tests: HD Diagnostic (read the details at the link)
Please try these free stress tests:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Prime95 download site: Free Software - GIMPS
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
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.x86fre.win7_gdr.100618-1621 Debug session time: Sun Sep 26 08:58:21.852 2010 (UTC - 4:00) System Uptime: 1 days 1:59:41.909 *** WARNING: Unable to verify timestamp for cdd.dll *** ERROR: Module load completed but symbols could not be loaded for cdd.dll Probably caused by : cdd.dll ( cdd+72c9 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: FIFA10.exe Bugcheck code 1000008E Arguments c0000005 82893f21 b66dfa94 00000000 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
|My System Specs|
|27 Sep 2010||#5|
| || |
So far, prime95 is running fine. I realized I need to clean up my graphics card because it reached 89 degrees Celsius in FurMark and that's not a manufacturing specified temperature , though the framerate didn't drop. I will try a video memory and artifact test later. And regarding the HDD tests I mentioned in the other thread that I already ran the western digital utility extended test on both drives. Are you sure I could test the drives with the seagate tool ?
|My System Specs|
|27 Sep 2010||#6|
| || |
Yes, you can test with the Seatools, we test W-D drives all the time at work with it.
I'm just wondering if the Seatools will mention that the drive has been overtemp - which could affect the issues that you're experiencing.
This isn't absolutely essential, but it will give us a more complete picture of what's going on.
|My System Specs|
|Similar help and support threads for2: bsod related to another thread|
|BSOD browser related/vssc.exe related||BSOD Help and Support|
|BSOD Apparent related to IPOD Touch and/or related services||BSOD Help and Support|
|Another BSOD thread!||BSOD Help and Support|
|Another BSOD 3rd Thread||BSOD Help and Support|
|Yet another BSOD thread||BSOD Help and Support|
|Another Win 7 64-Bit BSOD thread...||BSOD Help and Support|
|Yet another BSOD thread.||BSOD Help and Support|