I have a bit of a problem with Windows 7, the BSOD appears first, then restart, and at start Event Viewer always pop-out to try to find a solution of the problem via Internet, but still NOTHING It always happens when I try to download something from the Internet, no mater WHAT, when i start reading (downloading) e-mails via Microsoft Outlook, or starting download with FlashGet, or Mozilla Firefox or EVEN with incorporated Microsoft Internet Explorer... Aat the same moment when download manager starts-BSOD. Regardless of site, or download manager I use, the same situation Though it is not happening every time I start downloading, but I noticed that it happens ONLY then, and it happens sometimes even after the restart, when I restart a download from the Internet - the same situation Currently I have Vista 64bit on one of the HDD, and on the other Windows 7 to 64bit. Of hardware I have: Core 2 Duo 8400 in the 3.0 GHz Gigabyte P43 DS3 motherboardASUS HD3650 VGA AtiRadeon ... Classical use of software programs, nothing experimental, no BETA software... exept Win7 RC...

When you have BSOD system generate *.dmp files which are very helpful to diagnose this kind of problem and includes more informations than alone blue screen.These files are stored in C:\Windows\Minidump -you have debug them by using this tool:http://www.microsoft.com/whdc/devtools/debugging/default.mspx More info:http://support.microsoft.com/kb/969028

Thanx, but I'm not so good in this program, I don't really know what to do with it? Should I just leave it on until BSOD or to start him immediately after BSOD (restart)? I'm use this PC for storage my music and to reproduce it, some gaming naturally, but rarely. Also I have problem with WMP, when is once started I could ONLY switch it off from task manager in process tab, because it just WONT completely shut down, program sometimes freezes, and after that when i shut it down I have to end task from task manager, or else it's process stays on and forcing my CPU to go to 80 or 90%... I have LOT"S of music, around 200Gb and this crazy program STILL can't import all songs, even after leaving it on for a few days, I have to say that older WMP was better... 4 Sure this one is much more nicer, some of solutions are really good, but still I have problems with it... Freezing, refusing to shut down completely, forcing mu CPU to go the max... That's NOT cool

1.Download Process Explorer http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx and make log File>>Save As 2.Pack the whole folder C:\Windows\Minidump both packed folder with dump files and log from PE upload on http://www.speedyshare.com/

I upload it, You can find it at: http://www.speedyshare.com/916660636.html Thanks in advance, for help with BSOD and Windows media player. Thank s

This is strictly hardware trouble -there is no doubt! [quote] Microsoft (R) Windows Debugger Version 6.10.0003.233 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [G:\Usr\Nowy folder\Minidump\070109-26754-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7100 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c42e90 Debug session time: Wed Jul 1 03:29:16.237 2009 (GMT+2) System Uptime: 2 days 10:28:44.907 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck E3, {fffffa80053be050, fffffa800538e060, fffffa8005c732d0, 3} Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Ntfs.sys *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : ntoskrnl.exe ( nt+7ef80 ) Followup: MachineOwner --------- [/quote] You have to diagnose disk,motherboard your PSU -what's your PSU? -this is important Unfortunately I'm not expert in hardware -anyone with more experience in this field may help you