BSOD internet, eclipse, spotify, vmware player cdd.dll error

Hi, i follow your tutorial and I preparate a zip folder with sf diagnostic tool. In my new sony vaio notebook vpcf2, just using it with different application opened (not always the same but usually: eclipse, sqldeveloper, vmware player, chrome, firefox, iexplorer) the pc shutdown with a BSOD.

Windows 7 professional 64bit
original installed OS on the system
OEM
New laptop one month

thanks in advance.

It does not appear you let the program run to completion. Many of your files are missing for the crash reports. Please follow the https://www.sevenforums.com/crashes-d...tructions.html and let it run to completion. It may sometimes look like it is not doing anything when it actually is, so go get a cup of coffee or something while it runs to make sure it finishes.

Thanks, I run it again and I upload new files also with the procedure that you linked to me, but the second part of the last procedure https://www.sevenforums.com/crashes-d...tructions.html goes in timeout, without other information, and I run it as administrator from control panel and from prompt. But I upload the files about sf diagnostic tool and from the first part of the link that you indicate to me.
thanks again.

Software Concerns:

It appears you may be cleaning your disk with CCleaner. Please refrain from doing so for the duration of our troubleshooting. CCleaner deletes the .dmp files during disk cleanup that we need for analysis.

Analysis:

Your Event Viewer logs indicate a likely memory or driver issue.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 220210
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.

Thanks.
Yes my pc is still under warranty, I'll do memtest to check memory status, i'm not overclocking nothing. I just change initial ram banks from 2x2GB=4GB to 2x4GB=8GB. I'll post the result soon as possible.
thanks again

You're welcome. Let us know how things go with the RAM swapped out.

I'd no time to test my RAM but my pc goes in BSOD again right now. I upload the dump files &co., they're still hot :-(

No .dmps were included. Did you turn Verifier on? Sometimes Verifier will not allow .dmps to be created if there are too many non-Microsoft drivers being Verified. If you have Verifier enabled, try testing 5 non-Microsoft drivers at a time for 24-36 hours. Post back after that time with any new crash reports. If you do not get any new crashes, move to the next 5 non-Microsoft drivers after 36 hours.


Also, your VAIO software is causing a lot of application crashes. Clean Up Factory Bloatware may be of interest.

here we are,
i used a lot of time memtest but i can't find no errors, I also cleaned up my pc with the link that you suggest me.
Today I had a crash but different from others because was linked to verifier and vmware, when i turn off the verifier vmware goes up with no trouble, now I'm going to do controls with verifier for my drivers, now I think that the problem is hided there.

Thanks

You could also see if leaving Verifier disabled provides stability now. Verifier can cause false positives at times, so there may not be anything actually wrong with VMWare, it just does not work well with Verifier enabled.

See how the system behaves with Verifier disabled. Do your normal routine for a while, and post back whether you get another crash. Also post back if the problem is solved. :)