Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after Welcome screen


08 Oct 2010   #1
ptb

Windows 7 Pro x64
 
 
BSOD after Welcome screen

Hi i just randomly got a BSOD today as i started up my PC. it has been running perfectly fine for the time i have had it (since begining of the year). i tried booting up into safe and normally but it never made it past the welcome screen and kept looping for about 9 times. on one time it made it past and showed the windows dump/error dialog box but it BSOD'd right after and upon the next boot it was fine. btw all the BSOD went away really quick as well, after a memory check (??) i think finished

anyways i am posting from it now as it has loaded up fine on about the 10th reboot

i have attached the dump

my specs are
AMD Phenom II X2 545 3.0GHz (unlocked to fully stable X4)
Asus M4A785D-M PRO
Corsair TWIN2X4096-8500C5 4GB
ASUS DVDRW
Scythe Shuriken
Western Digital Caviar Blue 640GB
HIS HD5770
Corsair HX520
Antec NSK2400

running Windows 7 Professional x64

hopefully someone can help, thanks

My System SpecsSystem Spec
.

08 Oct 2010   #2
Microsoft MVP

 
 

Only 31 hotfixes listed in your systeminfo file. There's at least 45 to 60 (or more) available for Windows 7. Please visit Windows Update and get the rest of them.

Please uninstall Daemon Tools and Catalyst Control Center as they can cause BSOD's with some Windows 7 systems. Feel free to install a fresh copy (if needed) AFTER we finish troubleshooting.

If you still have the Asus PCProbe Utility installed, please either update it or uninstall it. The driver is from 2007. If it's not installed, please visit the Asus website and install it.

This is trending towards a hardware error - but the pattern isn't quite visible yet. Please run Driver Verifier according to these directions:
Quote:
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:
Code:
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
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct  8 16:24:15.636 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:39.665
Probably caused by : rdyboost.sys ( rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+8a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`07005113 00000000`00000002 00000000`00000001 fffff800`02d7cc43
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct  8 16:22:44.379 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:19.033
BugCheck D1, {8004, a, 0, fffff88000fe057d}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : atapi.sys ( atapi!AtapiProgramTaskFile+29 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments 00000000`00008004 00000000`0000000a 00000000`00000000 fffff880`00fe057d
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct  8 16:14:42.654 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:31.154
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`02b106e0 00000000`0000000d 00000000`00000000 fffff800`020e0ac7
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct  8 16:13:12.352 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:34.226
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+4244e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  explorer.exe
Bugcheck code 000000BE
Arguments fffff8a0`055895c3 80000001`21121121 fffff880`07e6c470 00000000`0000000b
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct  8 16:12:01.965 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:22.994
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+e826d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`000005d7 00000000`0000000d 00000000`00000000 fffff800`02d97302
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
Reply

 BSOD after Welcome screen




Thread Tools




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 02:13 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33