Hi tootdAy, Thanks for posting your question. This is a Windows Vista support forum.
If you have disabled "Always ask before opening this type of file" during file downloads. To reset the default behavior so that explorer will prompt you to open or save the file type, perform the following steps
1. Open the Control Panel Folder Options applet.
2. Select the File Types tab.
3. Scroll down to the extension type that you want to reset.
4. Select the extension type, and then click Advanced.
5. Check the "Confirm open after download" check box, then click OK. 6. Click Close to the Folder Options dialog box.
If you do not get the prompt for downloads at all then try to the steps below
1. In Internet Explorer, click Tools, and then click Internet Options.
2. Click the Security tab.
3. There are four security zones listed: Internet Local intranet Trusted sites Restricted sites 4. Click the zone where you want to change the settings.
5. Under Security level for this zone, click Custom Level. 6. Under Downloads, under Automatic prompting for file downloads, click Enable, and then click OK two times.
Hope the above information helps.
Regards. Sharath Govindappa Visit our Microsoft Answers Feedback Forumhttp://social.answers.microsoft.com/Forums/en-US/answersfeedback/threads/ and let us know what you think.
Windows Error Reporting - To Fix Calling out the "File Download" dialog box
Go to Start button.
Open Control Panel.
Go to Windows Error Reporting.
Click on System and Maintenance, then click Problem Reports and Solutions.
Next, click Change Settings located on the left side panel of the Problem Reports and Solutions window.
Select an option to configure how you want Windows to look for a solution to your problems. You may allow Windows to do it automatically or ask you every time to check if problem occurs.
Next, click the Advanced settings link.
Select Off to turn off Error Reporting.
Recommended Method to Repair the Problem: Calling out the "File Download" dialog box:
How to Fix Calling out the "File Download" dialog box with SmartPCFixer?
1. Download Error Fixer . Install it on your system. Click Scan, and it will perform a scan for your computer. The errors will be shown in the list.
2. After the scan is finished, you can see the errors and problems need to be fixed. Click Fix All.
3. The Fixing part is done, the speed of your computer will be much higher than before and the errors have been fixed.
Hello, I've just purchased a new computer with Windows 7. I'm an old XP user so I'm not nearly as comfortable troubleshooting in this new environment. Anyways, I've had an issue with this week old machine where it crashes after I return to using the computer after periods greater than an hour. At first, this occurred every time I left the machine undisturbed for longer than an hour. I had disabled the sleep mode and this had no effect. After the first couple of days, I talked to the computer store where I purchased it, and they swapped out the 2 sticks of memory sighting that it may be the problem. For the next 7 days, I had not encountered an issue again and believe the issue was solved. However, tonight, it appears that the issue is back. I have zipped all the dumpfiles here https://skydrive.live.com/redir.aspx?cid=8dcaaf7c70974bd9&resid=8DCAAF7C70974BD9!138 I don’t know how to read the info in these files beyond the part that tells me ntoskrnl.exe +7fd00 is to blame for the latest bluescreen issue. Please note that the first 3 dump files occurred prior to the memory swap. Also note that there were multiple more crashes prior to the memory swap but not all generated a dump file. I was hoping someone would be able to help me out. I don't believe I have the knowledge base to solve this alone. I have updated all the drivers via windows update and have even manually updated the video driver in an attempt to troubleshoot. Also, I should mention that I had installed office 2010 via Microsoft’s Home User Program (HUP) so I’d like to avoid reinstalling a fresh copy of windows 7 as I’m not sure I can reinstalled Office again with the same license (I don’t know how all that licensing stuff works) Any assistance or advice would be greatly appreciated. Thanks, Jason
Anwsers to the Problem Blue Screen Errors: ntoskrnl.exe
On a new computer you really need to contact the System Maker and Seller for replacement or warranty repair. Keep in mind that the more you do the more they will say it is something you have done. Added that you want this documented in case there are any down the road issues.
Check this thread for information on using BlueScreenView, MyEventViewer, and other methods to troubleshoot BlueScreens - top 3 methods (+1 other). http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990
Error message on a blue screen on a computer that is running Windows 7 or Windows Server 2008 R2: "STOP: 0x0000000A" http://support.microsoft.com/kb/979444 Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2 and that has iSCSI storage: "0x0000000A" http://support.microsoft.com/kb/979711
Those and 5 other KB Articles are available http://support.microsoft.com/search/default.aspx?mode=a&query=0x0000000A&spid=14019&catalog=LCID%3D1033&1033comm=1&res=10
Drivers could be at fault however disk issues or antivirus/antispyware/security products are just as likely to be the root cause as they can force a driver to corrupt or go out of bounds. The video driver or something affecting it would be very suspect.
Be sure the drivers, BIOS, and low level chipset drivers are all updated by manually checking at the System maker and device makers's sites.
Below I will post a generic bluescreen troubleshooter and in the next message how to update drivers and BIOS as well as do memory checks.
----------------------------------- BCCode: 0A 0x0000000A Cause This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS. If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. Resolving the Problem If a kernel debugger is available, obtain a stack trace. To resolve an error caused by a faulty device driver, system service, or BIOS Restart your computer. Press F8 at the character-based menu that displays the operating system choices. Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error. Try disabling memory caching of the BIOS. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer. Make sure the latest Service Pack is installed. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks. If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List. Comments Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools. BCCode: 0A 0x0000000A <-- read this link http://www.faultwire.com/solutions-fatal_error/IRQL-NOT-LESS-OR-EQUAL-0x0000000A-*1025.html ================================================================== BCCode: 24 0x00000024 Remove ALL power and reseat the cards, memory, and cables (on both ends when possible) - actually remove and replace - do not just snug.
The primary cause of this Bug_Check is disk issues however it can be caused by memory problems and even antivirus/antispyware/security programs.
Cause One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error. Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Resolving the Problem To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use the kb (Display Stack Trace) command. To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. RunChkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition. To resolve a nonpaged pool memory depletion problem: Either add new physical memory to the computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume. BCCode: 24 0x00000024 <-- read this link http://www.faultwire.com/solutions-fatal_error/NTFS-FILE-SYSTEM-0x00000024-*1051.html?order=votes
============================================================= BCCode: 7E 0x0000007E which is also 0x1000007E
Check these KB articles : "Stop 0x0000007E" or "Stop 0x00000050" Stop error message in Windows 7 or Windows Server 2008 R2 http://support.microsoft.com/kb/979538 "Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" error when the GPU is under heavy load conditions in Windows 7 or Windows Server 2008 R2 http://support.microsoft.com/kb/983615
--------------------------------------------------------------------------------------------- References to Vista also apply to Windows 7.
BCCode: 7E 0x0000007E which is also 0x1000007E This error is usually a driver issue and display adapter (video) driver is the most suspect though it could be others. Antivirus/antispyware/security programs, hardware (heat) and major software issues can also cause the error. When you get to the driver section of the troubleshooter use my generic methods in the next message and then return to the troubleshooter if needed.
Have you added hardware recently or updated drivers? Be sure to look in Control Panel - Windows Updates to see if any drivers were updated there. Other lessor possibilities include antivirus/anti- spyware/security programs.
When you get to the driver and memory sections of the troubleshooter refer to the next message to update drivers and test memory and then refer back to the troubleshooter if needed.
BCCode: 7E 0x0000007E which is also 0x1000007E Cause The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated. Common exception codes include the following:
0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered. 0x80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system. 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred. For a complete list of exception codes, see the Ntstatus.h file that is located in theinc directory of the Microsoft Windows Driver Kit (WDK). Resolving the Problem If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem. If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is started with the /DEBUG switch. If exception code 0x80000002 occurs, the trap frame supplies additional information. If you do not know the specific cause of the exception, consider the following issues: Hardware incompatibility. Make sure that any new hardware that is installed is listed in the Microsoft Windows Marketplace Tested Products List. Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you must start the computer by using the Recovery Console to access the file. If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the computer by using the Recovery Console and then deleting the offending system service file. Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E. You can also disable memory caching of the BIOS might to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer. The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and.chkfiles that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version. BCCode: 7E 0x00000007E which is also 0x1000007E <-- read this link http://www.faultwire.com/solutions-fatal_error/SYSTEM-THREAD-EXCEPTION-NOT-HANDLED-0x0000007E-*1141.html?order=votes ===============================================================
Look in the Event Viewer to see if anything is reported about those. http://www.computerperformance.co.uk/vista/vista_event_viewer.htm MyEventViewer - Free - a simple alternative to the standard event viewer of Windows. TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file. http://www.nirsoft.net/utils/my_event_viewer.html
Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen info that would help. Such as the BCC and the other 4 entries on the lower left. And any other error information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.
As examples :
BCCode: 116 BCP1: 87BC9510 BCP2: 8C013D80 BCP3: 00000000 BCP4: 00000002 or in this format : Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo) tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000
This is an excellent tool for posting Blue Screen Error Information
BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table - Free http://www.nirsoft.net/utils/blue_screen_view.html
Many BlueScreens are caused by old or corrupted drivers, especially video drivers however there are other causes.
You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or Recovery Options if your system has that installed by the maker.
How to Boot to the System Recovery Options in Windows 7 http://www.sevenforums.com/tutorials/668-system-recovery-options.html
You can try a System Restore back to a point before the problem started if there is one.
How to Do a System Restore in Windows 7 http://www.sevenforums.com/tutorials/700-system-restore.html
Start - type this in Search Box -> COMMAND find at top and RIGHT CLICK - RUN AS ADMIN
Enter this at the prompt - sfc /scannow How to Repair Windows 7 System Files with System File Checker http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista cbs.log (and Windows 7) http://support.microsoft.com/kb/928228
The log might give you the answer if there was a corrupted driver. (Does not tell all the possible driver issues).
Also run CheckDisk so we can rule out corruption as much as possible.
How to Run Check Disk at Startup in Windows 7 http://www.sevenforums.com/tutorials/433-disk-check.html
Often updating drivers will help, usually Video, Sound, Network Card (NIC), WiFi, 3rd party keyboard and mouse, as well as other major device drivers.
Manually look at manufacturer's sites for drivers - and Device Maker's sites. http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm Installing and updating drivers in Windows 7 (updating drivers manually using the methods above is preferred to ensure the latest drivers from System maker and Device makers are found) http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html
How To Disable Automatic Driver Installation In Windows Vista - Drivers http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/ http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx
StartUp Repair from Recovery Options or Windows 7 disk
How to Run a Startup Repair in Windows 7 http://www.sevenforums.com/tutorials/681-startup-repair.html How to Boot to the System Recovery Options in Windows 7 http://www.sevenforums.com/tutorials/668-system-recovery-options.html How to Create a Windows 7 System Repair Disc http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html How to Do a Repair Install to Fix Windows 7 http://www.sevenforums.com/tutorials/3413-repair-install.html
Hope this helps.
Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
To check for Windows updates
Open Windows Update by clicking the Start button Picture of the Start button, clicking All Programs, and then clicking Windows Update.
In the left pane, click Check for updates, and then wait while Windows looks for the latest updates for your computer.
If any updates are found, click Install updates. Administrator permission required If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
Recommended Method to Fix the Problem: Blue Screen Errors: ntoskrnl.exe:
How to Fix Blue Screen Errors: ntoskrnl.exe with SmartPCFixer?
1. Click the button to download SmartPCFixer . Install it on your computer. Open it, and it will perform a scan for your system. The errors will be shown in the list.
2. After the scan is done, you can see the errors and problems which need to be repaired.
3. When the Fixing part is done, your computer has been speeded up and the errors have been removed