Sometimes BSOD - Cold boot

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Ultimate x64
       #1

    Sometimes BSOD - Cold boot


    Hi Guys,

    3 weeks ago I upgraded my Vista ultimate x64 to Windows 7 ultimate 64.
    And now I have a strange problem.
    Sometimes when I start the computer (cold boot) I get an BSOD with CNG.sys
    It keeps remaining everytime I reboot.
    When I start the recovery option and let the system restore the pc the problem is solved and Windows 7 starts perfect. Sometimes when I boot the pc it goes without a problem and othertimes I get the BSOD and need to do a recovery.

    I thought that VMWare Workstation could be the problem and uninstalled the software but it didnt help. Even the driver updates by windows update didnt solve it.
    Im thinking now about a reinstall with a clean install but maybe any1 has an other option.

    Thanks!

    Windows: Windows 7 Professional, Version 6.1.7600, , 64 Bit.
    Internet Explorer: 8.0.7600.16385
    Memory (RAM): 4096 MB
    CPU Info: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
    CPU Speed: 2399,9 MHz
    Sound Card: Geluid van externe computer
    Display Adapters: RDPDD Chained DD | RDP Encoder Mirror Driver | RDP Reflector Display Driver
    Monitors: 1x;
    Screen Resolution: 1440 X 900 - 32 bit
    Network: Network Present
    Network Adapters: Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controller
    CD / DVD Drives: G: Optiarc DVD RW AD-5170A | H: CTUZI YNSDEZO1Y
    Ports: COM1 NOT Present
    Mouse: 3 Button Wheel Mouse Present
    Hard Disks: C: 80,3GB | D: 274,2GB | E: 111,3GB | F: 931,5GB
    Hard Disks - Free: C: 33,8GB | D: 42,6GB | E: 24,2GB | F: 532,4GB
    USB Controllers: 8 host controllers.
    Firewire (1394): Not Detected
    Manufacturer: American Megatrends Inc.
    Product Make: P5K SE
    AC Power Status: OnLine
    BIOS Info: AT/AT COMPATIBLE | 07/19/07 | A_M_I_ - 7000719
    Time Zone: West-Europa (standaardtijd)
    Battery: No Battery
    Motherboard: ASUSTeK Computer INC. P5K SE

    :
    Last edited by Merijn25; 06 Dec 2010 at 09:22.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2
      My Computer


  3. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Sorry, updated now with the zip!
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    The single dump is blaming the core system file ntoskrnl.exe, usually a driver is the cause

    By enabling driver verifier the faulty driver will be located

    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

    Then if it crashes again upload the latest dump files located in C:\Windows\Minidump
      My Computer


  5. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Hi,

    I get the BSOD sometimes when I give the PC a cold boot. Not when using the system.

    Can you tell me wich option "Low Resource Simulation" is?
    I cant see it here.

    Thanks for your help btw!
      My Computer


  6. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #6

    I can't understand this language, use Google translate
    Low Resource Simulation is the 9th option i think
      My Computer


  7. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Ok just changed the settings like you said. Now wait for the new BSOD when doing a cold boot and then send the minidump?
      My Computer


  8. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #8

    Merijn25 said:
    Ok just changed the settings like you said. Now wait for the new BSOD when doing a cold boot and then send the minidump?
    Yes
      My Computer


  9. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #9

    To be sure i made a clean reinstall of Win7 and still have the same problems. Even when I switch the settings to make a minidump after a BSOD the settings are changed back to memorydump. Any other suggestions? Thanks!
      My Computer


  10. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #10

    Merijn25 said:
    To be sure i made a clean reinstall of Win7 and still have the same problems. Even when I switch the settings to make a minidump after a BSOD the settings are changed back to memorydump. Any other suggestions? Thanks!
    What antivirus are you using?
    Upload the new dumps
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:34.
Find Us