JDK 7u2 download causes BSOD

A funny anomaly for those who use JDK on Windows 7, just for your info.
On Windows 7 Professional ver.6.1 (Build 7601: Service Pack 1) that has Adobe Reader 9 Automatic Updater enabled, an attempt to download jdk-7u2-windows-i586.exe resulted in Blue Screen of Death every time when the Adobe Updater has "Click here for Updating for the newest version of Adobe Reader" displayed (as a sign of a completed automatic installer download, and the message ignored by the user).
The BSOD occurred at the last part of the download, occurred every time without failure, until I finally gave up enjoying the good old Blue Screen and installed the latest Adobe Reader 9(version 9.4.7) before downloading the JDK 7u2 installer. After this Adobe install, the download and the installation of the SE JDK went smoothly without a hitch.

Thanks for the comment. It prompted me to describe the BSOD in more detail.
Out of the 11 times I experienced these BSOD's while downloading 7u2, I got several different bug check strings:
MEMORY_MANAGEMENT 4 times, Points to ntkrnlpa.exe
IRQL_NOT_LESS_OR_EQUAL 3 times, Points to fltmgr.sys, MpFilter.sys, ntkrnlpa.exe (once)
Points to halmacpi.dll, ntkrnlpa.exe (twice)
BAD_POOL_HEADER Twice, Points to fltmgr.sys, halmacpi.dll, ntkrnlpa.exe
KERNEL_MODE_EXCEPTION_NOT_HANDLED Once, Points to ntkrnlpa.exe
PFN_LIST_CORRUPT Once, Points to ntkrnlpa.exe
Interesting, isn't it? It seems Windows is not quite sure what to blame the blue screen for. While I am quite aware of app developers' tendency to blame device drivers, driver coders blaming BIOS, BIOS coders pointing to hardware for the "cause" of a problem, I am not interested in semantics on the difference between causing and triggering. It is certainly true that many BSOD has their roots in device driver and BIOS bugs, but I am not so sure if this is the case here. As I don't have the time to look into the way Adobe lets its updater to make downloaded file status to survive a reboot, how Oracle installer performs CRC and other operations, and how Windows system files and config protection schemes interact with them, I chose to be a news reporter.

Similar Messages

  • Drivers cause BSOD {URGENT}

    Good day
    About 2 years ago I bought this laptop for a really good deal and i was impressed with the performance i got with it. Its quite a powerful and quality piece of tech.
    There are some drawbacks...
    In the two years ive had it ive formatted the laptop twice. Once to upgrade to windows 8.1,  and now because windows got corrupted and it didnt want to use a restore point. Which is normal for windows, it doesnt last forever.
    Drivers are a mess. Most i can gather is i'm suppose to download my laptop's drivers from here.
    http://support.hp.com/us-en/drivers/selfservice/HP​-Pavilion-dv6-Entertainment-Notebook-PC-series/522​...
    There are 3 different wireless lan drivers, the chipset drivers cause BSOD's, i can install every single driver on the list and i still have about 4 unknown devices in my device manager.
    Point is Im better off googling for the hardware ID's and scrubbing forums for my drivers.
    Please could Someone supply me a link where i can download a complete Driver DVD image for my laptop model that works.  I am more than willing to download a 1.4 gig torrent if it has proper work everytime drivers.
    Infact i would even drive to hp head office if they could supply me with a hardcopy.
    Help Please!
    Before i break something.
    Back on windows 7 btw

    Hi @Pixelite ,
    Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion dv6-7030ei Notebook and needing a recovery disk. Here is a link to show you how to and or order the Recovery Media you need.
    FWI: The driver page shows all drivers that were installed on all HP Pavilion  Notebooks.
    I would uninstall all the drivers with a yellow mark or caution on it. Restart the Notebook and if they are still there right click on the device and install or update the drivers.
    I hope this helps you out.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • Problems Installing JDK 7u2 Windows 64-bit

    I've downloaded the Development Kit but for some reason it won't install. I try clicking on it and nothing...
    Help please.

    The problem of installation of JDK 7u2 on Windows x64 is coming for both 32 bit and 64 bit versions of JDK.... However, i have tried installing them on Windows x86 (specifically Win XP SP3 x86 on VirtualBox 4.1.8) and the 32 bit version of JDK seems to be installing just fine on 32 bit Windows.
    I might be wrong here but maybe the problem is that the 32 bit code on the JDK 7u2 may contain some 16bit code and so the Windows x64 is not able to run it (x64 OS not backwards compatible with 16 bit code). However the chances of this is slim since this is an update and the JDK 7u1 both 32 and 64 bit versions were fine.
    However if this might have happened, then it is also possible that the 16bit code is also present in the 64 bit version of JDK 7u2 and thats why both the versions are not running on Windows x64.
    Hoping they fix the issue soon. I need to do some testing and programming on Java 7.

  • Reader 9 causes BSOD on Windows XP Pro

    We have a few systems here that are having real problems with Adobe Reader 9. When the users attempt to open a .pdf file, they get a BSOD, and the system reboots. Once the system comes back up, they are able to open the offending file with no problems.
    Here are details of our systems:
    Dell Optiplex 755
    Windows XP Pro SP3
    2GB Ram
    32 Bit OS
    I have found this occurs most often when opening pdf's that were created with earlier versions.
    I'm sure I have left out some vital piece of information, so if you need clarification on something, please ask. Any suggestions would be greatly appreciated!

    [While the original post was for Reader 9, I found this same problem with Acrobat 9 Pro, and found a solution.]
    Problem: Opening one PDF file is fine, but once you open the second file -- BSOD.
    Cause: There is still a problem with Adobe's 2D GPU Acceleration feature.
    Per http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405218&sliceId=1, "If acceleration hardware is detected, then optimization is enabled for all files except the first one opened when Acrobat launches." That is why the first file opens OK, but the second causes BSOD.  Adobe is either not detecting acceleration hardware correctly, or is not calling it correctly.
    Temporary Solution:
      1.  In Acrobat or Adobe Reader, choose to Edit > Preferences.
      2.  Go to the Page Display panel.
      3.  Uncheck Use 2D GPU acceleration.
    I tested my machine [Dell Optiplex 755, ATI Radion HD 2400 XT 8.420.0.0, Win XP Pro, Adobe 9 Pro] with "2D GPU acceleration" checked, attempted open of 4 PDFs from File Explorer -->first one opened, then BSOD, rebooted, unchecked "2D GPU", attempted the exact same operation --> all four opened in their windows and now I am happily typing on this page.
    This is per http://kb.adobe.com/selfservice/viewContent.do?externalId=324073, which is a post from two years ago and relates to Adobe 8.  So, Dell has been fielding calls on this for at least two years.  Way to stick in there, Dell.  Two years ago, Adobe knew the problem ("You are using an desktop ATI video card with driver version 8.291 or 8.301 and have the Acrobat Page Display Preference 'Use 2D GPU acceleration' enabled." was what they said back then, and recommended updating the video drivers.  So, Dell stays with it, Adobe says to update your drivers.  Well, I bought an entirely new Dell to get the latest drivers and it didn't help.
    Permanent solution:
    Adobe needs to get 2D GPU acceleration to really work (how about a line of code where you check whether it is going to work before you execute it?) or ship their product with that feature off by default.

  • Where can i get setup cause i formated my mac mini and now i am not able to download cause i did not have any backup

    where can i get setup cause i formated my mac mini and now i am not able to download cause i did not have any backup

    How did you format your Mac Mini? Did you restart into Recovery Mode (Command+R) and erased your Macintosh HD? Or did you use some external drive or DVD to erase it?

  • Mysterious downloading causing satellite internet to go over limit

    Sorry for the long post. I have tried a lot of ways to answer my question, or fix my problem.
    II have a 3 year old Intel Mac, still working great. Where we live our only high speed option is satellite, so we subscribe to hughesnet. Our downloads are limited to 375 meg per day.
    We don't have a real problem staying under, but when it locks ups to 14.4 kbs, we know we have gone over. I eventually installed a few programs to let me know if it was my kids downloading stuff and not telling me, or something else. I installed two download monitoring programs, and Spector for Mac.
    In the last month, there have been two incidents where massive downloading caused us to go over the daily limit. Hughesnet has at times locked us out claiming we went over - the download monitors were installed to verify this, and proved otherwise.
    However, these last two times, the download monitors verified a download of over 300 meg within the space of an hour, part of the time while I was on the computer.
    I have tried every way in the world to discover what the culprit was, what the files were, but I cannot.
    I have checked the download records and histories of all three browsers, and these show nothing. Spector verified almost no browser use during the time in question.
    I checked Itunes to see if anything, whether music, movies or podcasts had been added during that time frame. Nothing.
    I checked the date of files in the download folder, both "created" and "modified". Nothing there.
    I check the software updater(This had been a problem in the past). The log of downloaded updates shows no activity there as well.
    My e-mail program didn't show any automatic downloads with massive file attachments, either.
    It left me scratching my head.
    After this happened a few weeks ago, I downloaded a 30-day trial of Intego Internet Security Barrier X6. Virus program, firewall, and a couple of other programs, I updated it and did a virus/trojan scan on my computer, with no results. I was completely clean. The antivirus program really slowed down the Mac, of course, and it got so bad that after a few days i couldn't take any more, so I uninstalled it.
    The only options I haven't tried yet are scanning the backup drive( assumed this was scanned at the same time when I scanned the main nard drive, but am not sure) and possible a couple of other partitions. I have Windows XP installed on this computer through bootcamp, but haven't booted up in over 2 months. I also have a second version of windows installed within the mac osx partition through a Virtualbox program. I don't know if a virus could be hiding in there, but I am relatively certain that I installed antivirus protection on it and updated it as well. Even at that, I don't know if a trojan or virus could be play havoc while the program is turned off.
    That is what I have done so far, and am out of ideas. Does anyone know of a way I can track down what this was?
    If not, does anyone know of a program that could monitor this in the future and alert me to massive unauthorized downloads?
    All comments and ideas are appreciated.
    Fred

    There may be a way to monitor who (else) may have access, presumably
    unauthorized and more possible if you have a local wireless aspect to your
    home or business network where someone else not so far away could get in.
    As both up and down load activities can be monitored, are you able to tell if
    some of your usage is due to something in the computers "calling out" online
    and them perhaps something else connecting back to your computers? The
    app Little Snitch will tell what may be attempting some connections out.
    Sometimes, you can tell if another computer is on a local network, unless that
    owner or user has somehow set their computer to be invisible to a network it
    may be borrowing internet access from.
    Do you have any apps that offer an option to provide backups online to some
    outside server? Some kinds of products can offer web-dependent services.
    Even widgets in DashBoard can consume bandwidth. I have and use a widget
    that turns off all widgets until I launch DashBoard. Dash-quit is a handy tool.
    {Having dual operating systems in the computers, possibly could be an issue;
    but whether or not your configurations are accessing the internet somehow,
    is an unknown to me. If the Windows systems can't go online while you aren't
    using them, maybe those aren't a probable cause of this; until they actually are.}
    Is the network usage statistic based on mbps, kbps or some other set of numbers
    where your version may appear different than that of the provider? Some of the
    math (like MB vs. GB in drive capacities; comparing grapes and bananas) can be
    harder to follow if one entity derives their quota from a different connection math.
    Almost as bad in a few cases, as the cited hard disk drive capacities, when there
    may be two different kinds of numbers!
    I've only used dialup, ADSL, and some low-end cable internet. Had dish TV but
    at the time, they offered nothing for internet; except weather outages of all signal.
    If you have nothing checking for automatic updates, including apps that may offer it;
    and have the firewall set to not allow some invasive efforts of outside connections
    to try and hook up to your network, and no body accessing your satellite internet via
    a wireless component whose security is not what it should be; I am not so sure what
    kind of other thing you'd need to be looking into at this point. Apparently something.
    Good luck & happy computing!

  • Just got a new 5c--the apps stopped downloading cause I wasn't connected to wi-fi. How do I get them to start downloading again?

    Just got a new 5c--the apps stopped downloading cause it wasn't connected to wi-fi. How do I get it to start up again?

    If you're downloading them as part of restoring and iCloud backup, sometimes turning the device off, then back on will restart the download.   Otherwise, you may need to stop the restore (Settings>iCloud>Storage & Backup, Stop Restoring), then erase the phone and restore the backup again.

  • ITUNES downloads from store causing BSOD windows stop error- Please Help!

    Hi everyone,
    maybe someone can help me out or knows how to fix this problem.
    Problem in detail:
    This problem started since I updated to the latest version of itunes 7 to download video for my ipod video 30gb. Itunes worked perfect on my computer before updating as I used it with an ipod mini.
    I was able to use my new IPOD 30gb fine and transfer all my music to it correctly.
    The main problem occurrs when downloading anything from itunes store...1st noticed this when my podcasts were updating and downloading and then the system suddenly crashed with the windows blue screen error message and had to reboot. This happened multiple times so I disabled the automatic downloads of podcasts. Itunes then works fine when not downloading anything.
    I then tried purchasing a TV show, whole series, and when it began downloading, the Exact same Error and Blue screen will occur--Very Frustrating.
    I uninstalled ITUNES and Quicktime, and then reinstalled them via the latest download from itunes. The same errors still occur.
    When windows reboots and sends error report to Microsoft, it states the error is due to a Driver error of which the specific driver is not known.
    I have called apple/itunes support and spoke with them and they could not figure out the problem and said I should check with my computers cust service and/or microsoft as it was probably something on this end...I did this and they stated the problem must be something with itunes and especially since all other programs run fine on my system.
    SO basically I am going in circles trying to figure this out so I am hoping someone here may know how to fix this problem.
    Not only that, but I tried the same on my desktop as I figured I could at least download my podcasts and purchases to my desktop and then transfer to my ipod from there(as I am mainly using my labtop for my ipod) and updated my desktop to itunes 7 latest version,, and figured it would work on my desktop with same operating system----but it Caused the SAME error BSOD as my labtop and in same fashion....only when downloading from itunes.
    ANy help is much appreciated as I got the ipod video mainly because of ITUNES video content and podcasts and if I cannot use these major functions on ITUNES than This Was a Complete Waste for me to get the Video IPOD.
    Hope there is a way to fix
    Thanks

    I afraid can’t help much with this, but no one else
    has answered. It does seem very odd that two
    different computers have the same problem. It makes
    you wonder about the content you were trying to
    download. As a matter of interest was the
    installation for both computers done from the same
    download file?
    When your computer dies, can you read the stop
    message or does it disappear, if it does, go to
    Control Panel>System>Advanced
    Click Settings in Start Up and Recovery and make sure
    that Automatically Restart is no checked.
    You should be able to get a stop number from the blue
    screen and you may also be able to identify the
    filename of a driver, which could give a clue to the
    problem.
    The Microsoft Website has a certain amount of help on
    specific stop messages, you can search for the number
    of the stop message which will be something like
    0x0000000A.
    There is also some help on troubleshooting stop
    messages here:
    http://aumha.org/win5/kbestop.htm
    Thanks for your reply.
    As far as the content being downloaded from itunes---consisted of different podcasts and also on a separate occasion-the tv show Heroes complete season on ITUNES..So I would guess the error has nothing to do with the content being downloaded.
    The ITUNES installation for both computers was from the same itunes download file on this website on apples itunes free download.
    I did not write down the most recent stop numbers and no drivers seemed to be named on the blue screen from what I could tell, but I guess I could be missing something...
    From a previous crash with the BSOD- the error message listed was this: STOP: 0x00000050 (0xbad0b158, 0x00000000, 0x8056ea22, 00000002)
    not sure if this helps maybe figure out the cause of this or not.
    Maybe this will help get to the bottom of this.
    Thanks

  • Ntkrnlmp.exe causing BSOD randomly

    Recently we have been having random reboots and BSODs on our TS box
    Background:
    Windows Server 2012 R2 - RDS/Print/File - VM on Hyper-V Host (Windows server 2012 r2)
    https://onedrive.live.com/redir?resid=AF339BCAC63CB706!228&authkey=!AG-5gWy6tUwoAiE&ithint=folder%2c
    Attached are the dump files^^^
    Ran ran memtest86 on the host with no errors
    Ran Windows memory diags on host and VM with no errors
    Updated all firmware and drivers for our HP Proliant ML350 gen8 server
    Ran Driver Verifier and pointed it towards the problem child (ntoskrnl.exe) and the server bsod twice in a matter of ten minutes with, of course "Driver Verifier detected a Violation"
    Checked the version number Ntoskrnl.exe version 6.3.9600.16452 - Removed
    Windows Update Rollup - KB2903939
    Double checked and verified removed.
    Rebooted and ran Driver verifier after update removal - BSOD twice with same scenario as above. Disabled Driver verifier for now. 
    I'm hoping to find a fix for this as this is the main RDS server. 
    I appreciate your time. If you need anything else, please let me know. 
    Thanks!
    *Going to add another DUMP that happened today Below*
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Windows 8 Kernel Version 9600 MP (6 procs) Free x64
    Product: Server, suite: TerminalServer
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    Machine Name:
    Kernel base = 0xfffff802`1f286000 PsLoadedModuleList = 0xfffff802`1f54a990
    Debug session time: Fri Apr  4 16:32:20.197 2014 (UTC - 4:00)
    System Uptime: 0 days 6:36:23.236
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00007ff6`35f58018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ************* Symbol Loading Error Summary **************
    Module name            Error
    ntkrnlmp               The system cannot find the file specified
    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff8021f2cc740, ffffd000276e0eb0, 0}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                      ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                      ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    Probably caused by : ntkrnlmp.exe ( nt!RtlAvlRemoveNode+478 )
    Followup: MachineOwner

    Thanks for the information.
    In case you do need to enable Driver Verifier, refer to the following:
    Driver Verifier:
    What is Driver Verifier?
    Driver Verifier is included in Windows 8/8.1, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows
    kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
    Before enabling Driver Verifier, it is recommended to create a System Restore Point:
    Vista - START | type rstrui - create a restore point
    Windows 7 - START | type create | select "Create a Restore Point"
    Windows 8/8.1 -
    http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html
    How to enable Driver Verifier:
    Start > type "verifier" without the quotes > Select the following options -
    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    - Special Pool
    - Pool Tracking
    - Force IRQL Checking
    - Deadlock Detection
    - Security Checks (Windows 7 & 8)
    - DDI compliance checking (Windows 8)
    - Miscellaneous Checks
    4. Select  - "Select driver names from a list"
    5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
    7. Click on Finish.
    8. Restart.
    Important information regarding Driver Verifier:
    - If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this
    happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled, it is monitoring
    all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.
    - After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and
    as stated above, that will cause / force a BSOD.
    If this happens, do not panic, do the following:
    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    - Once in Safe Mode - Start > Search > type "cmd" without the quotes.
    - To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
    ・    Restart and boot into normal Windows.
    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    - Once in Safe Mode - Start > type "system restore" without the quotes.
    - Choose the restore point you created earlier.
    -- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods:
    5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1
    How long should I keep Driver Verifier enabled for?
    I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.
    My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?
    They will be located in %systemroot%\Minidump
    Any other questions can most likely be answered by this article:
    http://support.microsoft.com/kb/244617
    Regards,
    Patrick

  • Ntkrnlmp.exe causing BSOD intermittently (DUMP Attached)

    Recently we have been having random reboots and BSODs on our TS box
    Background:
    Windows Server 2012 R2 - RDS/Print/File - VM on Hyper-V Host (Windows server 2012 r2
    https://onedrive.live.com/redir?resid=AF339BCAC63CB706!228&authkey=!AG-5gWy6tUwoAiE&ithint=folder%2c
    Attached are the dump files^^^
    Ran ran memtest86 on the host with no errors
    Ran Windows memory diags on host and VM with no errors
    Updated all firmware and drivers for our HP Proliant ML350 gen8 server
    Ran Driver Verifier and pointed it towards the problem child (ntoskrnl.exe) and the server bsod twice in a matter of ten minutes with, of course "Driver Verifier detected a Violation"
    Checked the version number Ntoskrnl.exe version 6.3.9600.16452 - Removed
    Windows Update Rollup - KB2903939
    Double checked and verified removed.
    Rebooted and ran Driver verifier after update removal - BSOD twice with same scenario as above. Disabled Driver verifier for now. 
    I'm hoping to find a fix for this as this is the main RDS server. 
    I appreciate your time. If you need anything else, please let me know. 
    Thanks!
    *Going to add another DUMP that happened today Below*
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Windows 8 Kernel Version 9600 MP (6 procs) Free x64
    Product: Server, suite: TerminalServer
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    Machine Name:
    Kernel base = 0xfffff802`1f286000 PsLoadedModuleList = 0xfffff802`1f54a990
    Debug session time: Fri Apr  4 16:32:20.197 2014 (UTC - 4:00)
    System Uptime: 0 days 6:36:23.236
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00007ff6`35f58018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ************* Symbol Loading Error Summary **************
    Module name            Error
    ntkrnlmp               The system cannot find the file specified
    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff8021f2cc740, ffffd000276e0eb0, 0}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                      ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                      ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands 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                                     ***
    Probably caused by : ntkrnlmp.exe ( nt!RtlAvlRemoveNode+478 )
    Followup: MachineOwner

    Please understand that this forum is meant for general windows server queries and we dont really analyze the crash dumps here.
    Please
    contact Microsoft Customer Service directly so that the memory dump file can be analyzed and this issue can be resolved efficiently.
    You
    may obtain the phone numbers for specific technology request please take a look at the web site listed below:
    https://support.microsoft.com/common/international.aspx?iid=174859&iguid=56907522-6886-4238-a70f-a1d06a4473c7_2_2&rdpath=1
    http://www.arabitpro.com

  • Flash causes BSoD on GX660R

    Recently I bought a MSI GX600R laptop.
    It seems to be working all fine except for a small issue that I can't figure out to solve.
    When I view streamed videos in Flash for instance YouTube videos the laptop has a tendency cause some kind of graphical error, making the screen output look really bad and if I don't immediately close the browser a BSoD occurs.
    In most cases I can make the graphical error disappear and avoid the BSoD by closing down the browser.
    For the record I'm running the newest Adobe Flash Player and just downloaded the newest ATI drivers/Catalyst.
    The problem is not browser specific since it happens both in IE as well as Chrome.
    Furthermore I'm not sure it only happens when I'm running my laptop on the batteries but it certainly happens a lot more frequently.
    Have anyone seen this problem before?

    Quote from: Kksmed on 19-December-10, 19:04:45
    Recently I bought a MSI GX600R laptop.
    It seems to be working all fine except for a small issue that I can't figure out to solve.
    When I view streamed videos in Flash for instance YouTube videos the laptop has a tendency cause some kind of graphical error, making the screen output look really bad and if I don't immediately close the browser a BSoD occurs.
    In most cases I can make the graphical error disappear and avoid the BSoD by closing down the browser.
    For the record I'm running the newest Adobe Flash Player and just downloaded the newest ATI drivers/Catalyst.
    The problem is not browser specific since it happens both in IE as well as Chrome.
    Furthermore I'm not sure it only happens when I'm running my laptop on the batteries but it certainly happens a lot more frequently.
    Have anyone seen this problem before?
    Hi!! i resolved on flash player disable hardware acceleration. But sometimes i have this problem. I updated my driver for ATI, but not work.
    And update flash video bios again dont work :(

  • Usb 6501 unresponsive causing BSOD(Blue Screen Error)

    There are a lot posts about the same issue but mine is a little peculiar so i decided to post it.
    I am using two usb DAQ in the same pc(usb-6501, usb-6001), connected to the usb port on the back. The usb-6501 is used to obtain digital inputs from read switches, Sensors through an ssr. The usb-6001 is used to control 2 double valve solenoid, 1 dc motor, 2 indicator lamps. usb-6001 is also used to read analog values of current(using hall effect sensor) and voltage(using potentiometer).
    At first i was facing problems with the usb-6001(the usb-6501 was working fine at this point) resetting during operation accompanied by BSOD. Then i learned it was due to my relay, which requires 30 mA of current to switch so i used the ULN2003a to interface the usb-6001 with the relays and after that the application was running perfectly for 4 days.
    Now the usb-6501 is having the same problem and when i perform "Self Test" from NI MAX it shows "Error Code:50405" and i am able to reset the device from NI MAX only sometimes, other times i would have to unplug the USB device then plug it back in. As the application is used for an automated test rig the customer is frustrated by this problem. Once the card becomes unresponsive(or after the card is reset) BSOD occours.
    I have checked all the device drivers and OS for any errors but they are fine. i have even tried changing the ram to solve the BSOD with no use.
    System Details:
    Windows 7 SP1
    NI MAX 14.0
    power saving is disabled 
    I have attached the latest mini dump files as they might help in finding out the reason behind this problem(File extensions changed for the purpouse of uploading).
    I need to know: Is there any permanent solution for this problem? and what is the reason for this problem.
    Attachments:
    060115-12480-01.txt ‏315 KB
    053015-12324-01.txt ‏315 KB
    052615-17440-01.txt ‏315 KB

    Additional info : i did an analysis of the dump files and this is the result
    0: kd> !analyze -v
    * Bugcheck Analysis *
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff88009fe10b1, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800657922e, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c30e8
    fffff88009fe10b1
    CURRENT_IRQL: 2
    FAULTING_IP:
    nifslk+822e
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0xD1
    PROCESS_NAME: System
    TRAP_FRAME: fffff80000b9c6b0 -- (.trap 0xfffff80000b9c6b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88009fe10b2 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffff80000b9c8e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800657922e rsp=fffff80000b9c840 rbp=fffff88009fe10b1
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nifslk+0x822e:
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1] ds:c8e0:fffff880`09fe10b1=??
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80003091be9 to fffff80003092640
    STACK_TEXT:
    fffff800`00b9c568 fffff800`03091be9 : 00000000`0000000a fffff880`09fe10b1 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c570 fffff800`03090860 : fffffa80`06adc250 fffffa80`05c3a060 fffffa80`06adc250 00000000`0000ffff : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c6b0 fffff880`0657922e : fffff880`05d47468 fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 : nt!KiPageFault+0x260
    fffff800`00b9c840 fffff880`05d47468 : fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 : nifslk+0x822e
    fffff800`00b9c848 fffff880`01d91f90 : 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 : 0xfffff880`05d47468
    fffff800`00b9c850 00000000`00000000 : fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 fffff800`00b9c8e0 : nipalk+0x75f90
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nifslk+822e
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nifslk+822e
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nifslk
    IMAGE_NAME: nifslk.dll
    DEBUG_FLR_IMAGE_TIMESTAMP: 51f2daeb
    FAILURE_BUCKET_ID: X64_0xD1_nifslk+822e
    BUCKET_ID: X64_0xD1_nifslk+822e
    Can anyone help me with what this means?

  • I started downloading a song from iTunes and then stopped it in the middle of the download cause it froze, but when I tried to redownload it, iTunes said the song was already downloaded. But it does not show up in my music library on my phone. Help?

    I bought a song on iTunes and it started downloading but then about half way through it seemed to stop downloading so I pressed the square stop button in he middle of the downloading circle so that I could try and restart the download. But when I went back to iTunes, instead of having the cloud and the arrow to let me download the song from the cloud next to it, it said "Play" as if I had already downloaded the song. So I went back to my music library to try and find the song but it's not there and iTunes isn't letting me download it cause it says I already have it. Please help.

    http://www.everythingicafe.com/quick-tips-how-to-delete-songs-from-your-iphone-i pad-or-ipod-touch/2012/02/14/

  • W510 Solid State Drive (SSD) Gets Stuck Causing BSoD. Why?

    Hey guys, this has been a problem for a while now, and it is really mind boggling ... I have a Lenovo ThinkPad W510 laptop with a 256GB Crucial M4 SSD drive. Ever so randomly the drive just hangs, the LED light that the drive is trying to load something stays "ON" for up to 5 minutes or so before it finally goes into a Blue Screen of Death (BSoD). Once it goes into BSoD the laptop reboots and it gets stuck on the ThinkPad motherboard logo, eventually it will display "ERROR 2100: HDD0 (Hard Disk Drive) initialization error (X)" Where X is usually 1 or 2, sometimes 3 but rarely. It will not function again until I physically turn it off and back on using the power button.
    A little bit of background about the problem, this is my 3rd Crucial 256GB M4 SSD, Crucial has been very helpful and they went as far as replacing the drive twice, i am starting to highly doubt its a drive issue, I think it could be something from the laptop itself. To be more clear, my laptop has also been serviced back in March (Motherboard was swapped as well as keyboard), parts failure. It was all done in very timely manner and everything was OK after the swap.
    A representative from Crucial told me that this is a classical problem with the SATA controller driver handling TRIM, he said the drive is getting stuck in an infinite TRIM state which causes the BSoD, after that the drive goes into some sort of a "panic" mode to protect itself and doesn't function again until a full power cycle. (thus the need to turn off and then on the laptop) he also added it could be fixed by installing the correct SATA controller driver.
    I have tried to use the default windows SATA controller driver, and I have tried to use the Intel one too, and it seems to happen less often with the windows drivers, but overall, it happens at least once a day. It is really frustrating and I am not able to get anywhere with it.
    Any help or advice is highly appreciated. I am considering getting rid of the Crucial SSD altogether and just using Intel SSD instead, but I am really doubtful that it is the SSD's fault especially that its the 3rd one I use. I also know a couple of friends who own ThinkPads with Crucial M4 SSD inside them, and they seem to be working very well for them.
    Thanks in advance,
    Al.

    Hi again,
    Ok so I have applied the fix you have mentioned above, and it did improve (lower) the frequency of the problem happening. It really improved a lot significantly when I uninstalled the Intel drivers and used the Windows 7 built in SATA controller drivers.
    However, ... it still happens ... less frequent, but it still takes place, my SSD still gets stuck at least once in 3 days now, or once in 2 days (after severe testing) and the same scenario happens. I am really stuck at this point, and not sure which direction to take.
    Any help would really be appreciated, if you have / know any method to debug the BSoD's I get and a way to locate the source of the problem I am willing to go through it 1 by 1 and solve this problem before deciding to finally just giving up on the drive altogether.
    Sincerely,
    Al.

  • Display adapter causing bsod

    hellloo
    I am currently trying to fix my bsod issue with my evny dv6 64bit running windows 8 (16gb RAM, intel i7 8 cores), which has been happening since the first month I got it, for many different reasons.
    Updating drivers and such has fixed a lot, but then a new error appears. At first I thought it was a RAM issue but that has so far come up clear (ran memtest for 24 hours, 8 passes no errors in fail safe mode, it crashed once when not in fail safe mode but I haven't been able to recreate it). recently I noticed that both intel HD 4000 graphics and NVIDIA are enabled, which it's apparently supposed to do. However, certain applications will run better, and without crashing, if I disable one. 
    For instance, the sims 3 will crash on the save game loading screen, but if I disable intel graphics, not only does the quality go waaay up, it won't crash on the loading screen. it is laggy, however.
    minecraft won't play if only NVIDIA adapter is enabled. the picture won't show and it just won't respond. works if both are enabled. haven't managed to get it to crash if just intel graphics is enabled
    Games are the only thing that makes the computer bluescreen. They're the only resource heavy programs I run (sometimes I use photoshop but as far as I can remember that has never resulted in bsod)
    to my understanding, it's supposed to use NVIDIA for games and the such, but intel HD for everything else? is there the possibility of some kind of miscommunication going on with these adaptors to cause constant blue screens? or is the error more likely somewhere else?

    Hi Inkiecat,
    Thank you for visiting the HP Support Forums and Welcome. I have read your thread on your HP ENVY dv6 Notebook and BSOD. Please call our technical support at 800-474-6836. If you are calling within North America, the number is 1-800-474-6836 and for all other regions click here.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Maybe you are looking for

  • How to Send Purchase Order in mail( PDF) to vendor while creating it(ME21N)

    Dear Experts, In our current system when ever we create purchase order using the tcode ME21N, based on the output type configured in our system for the vendor a FAX is send to them.. Now we wanted to send vendors a mail with PO as a PDF attachement. 

  • Album art mixed up on Ipod 5G

    Hello, I have a 5g ipod and recently finished riping over 200 CD's to Itunes. I added album art to every song on every disk . My Ipod is displaying the album art but it is displaying the wrong art on many songs. Sometimes it shows one art image on th

  • When I click on a link, a new window opens but is blank and says "stopped" at the bottom

    Happens on any website.eg-if I am looking for a quote on moneysupermarket.com and I lick on the required link, a new window will open but it will be blank and in the bottom left hand corner the word stopped appears

  • Fail to mount

    for the past few days, I have been in search of a faster/easier bittorrent client than azureus. I had had some difficulty with it and downloaded something else. since that time when I try and download a new client, or even reinstall azureus: 1. I don

  • Landscape keyboard in App Store

    Is there a hidden feature that lets you use a landscape keyboard when writing reviews in the App Store?