locked
BLUE SCREEN OF DEATH ( WHILE PLAYING GTA4 and GTA4 EFLC ) AND ALSO IN A APP. RRS feed

  • Question

  • hello...

    before you all start giving suggestions , i would LIKE YOU TO KNOW that i have ended GTA4 and i got this BSOD AFTER I STARTED PLAYING THIS GAME AFTER A MONTH.. THE ERROR DIDNOT CAME WHEN I WAS PLAYING THE GAME A MONTH AGO..

    MY PC SPECS:

    Operating System

    MS Windows 7 Ultimate 32-bit

    CPU

    Intel Core i3 530  @ 2.93GHz

    Clarkdale 32nm Technology

    RAM

    2.0GB Single-Channel DDR3 @ 669MHz (9-9-9-24)

    Motherboard

    ASUSTeK Computer INC. P7H55-V (LGA1156)

    Graphics

    DPRO750SB @ 1280x1024 ( I THINK THIS IS OF MY MONITOR )

    NVIDIA GeForce GT 240

    Hard Drives

    488GB Seagate ST3500418AS ATA Device

    Optical Drives

    HP DVD Writer 1270r ATA Device

    Audio

    Realtek High Definition Audio

     

    NOW TO THE DETAILS OF THE BSOD THAT COMES WHEN I PLAY GTA 4 :

    http://i33.tinypic.com/w7b5j.jpg

    THE DETAILS WHEN THE COMP IS RESTARTED :

    Problem signature:

      Problem Event Name: BlueScreen

      OS Version: 6.1.7600.2.0.0.256.1

      Locale ID: 1033

     

    Additional information about the problem:

      BCCode: 1000007f

      BCP1: 00000008

      BCP2: 8AF03750

      BCP3: 00000000

      BCP4: 00000000

      OS Version: 6_1_7600

      Service Pack: 0_0

      Product: 256_1

     

    Files that help describe the problem:

      C:\Windows\Minidump\082310-12636-01.dmp

      C:\Users\Adnan\AppData\Local\Temp\WER-41246-0.sysdata.xml

     

    Read our privacy statement online:

      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

     

    If the online privacy statement is not available, please read our privacy statement offline:

      C:\Windows\system32\en-US\erofflps.txt

    ...............................................................................................................................

    NOW TO THE SECOND BSOD I GOT RIGHT AFTER INSTALLING EVEREST home edition :


    DETAILS:

    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.256.1
      Locale ID: 1033

    Additional information about the problem:
      BCCode: 1000008e
      BCP1: C0000005
      BCP2: 9B34AAD8
      BCP3: A32E2904
      BCP4: 00000000
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 256_1

    Files that help describe the problem:
      C:\Windows\Minidump\082310-16972-01.dmp
      C:\Users\Adnan\AppData\Local\Temp\WER-27237-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt


    NOTE: MY CPU TEMP IS BETWEEN 40 & 45.

    I HOPE I HAVE PROVIDED ALL THE DETAILS YOU MIGHT NEED IN HELPING ME..

    THANK YOU.

    • Moved by Ronnie VernonMVP Monday, August 23, 2010 5:37 AM Focus (From:Windows 7 Miscellaneous)
    Sunday, August 22, 2010 10:10 PM

Answers

  • Hi,

    1 crash is caused by the driver: kerneld.wnt which is part of Lavasoft Everest. Update the tool please:

    Loaded symbol image file: kerneld.wnt
        Image path: kerneld.wnt
        Image name: kerneld.wnt
        Timestamp:        Mon Jul 25 17:31:46 2005

    because it is too old (from 2005)!!!!!

    2 crashes is caused by the driver:

    Image path: \??\C:\Windows\system32\drivers\FDCDNT.SYS
        Image name: FDCDNT.SYS
        Timestamp:        Thu May 28 16:28:25 2009 (4A1E9F89)

    So update this driver too and the issues should be gone.

    best regards
    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Tuesday, August 24, 2010 2:23 PM
    • Marked as answer by a.d_d.y Thursday, August 26, 2010 9:08 AM
    Tuesday, August 24, 2010 2:23 PM

All replies

  • Please zip and upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, August 23, 2010 12:40 PM
  • Hi,

     

    First, please provide the information which Andre.Ziegler requested.

     

    Also, please check if this game is compatible with Windows 7 from Windows 7 Compatibility Center or the manufacturers’ websites. And please let me know if there are any changes before the issue occurs.

     

    Now, let’s perform System Restore to the point when the issue hadn’t been occurring.

     

    After that, you may test this issue in Clean Boot and Safe Mode to determine the possible cause.

     

    If it works fine in Clean Boot, the root cause can be the third party software. If the issue reoccurs in Clean Boot, but works fine in Safe Mode, the cause can be the incompatible hardware drivers. You may narrow down the causes in Device Clean Boot.

     

    Device Clean Boot

    =================

    1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter.

     

    2. Expand "Sound, video and game controllers".

     

    3. Right click on your sound card and then click "Properties.

     

    4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK.

     

    5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled.

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article:

     

    How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,

     

    Sabrina

     

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     

    Tuesday, August 24, 2010 9:55 AM
  • Please zip and upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

    http://cid-c8108044de1a3603.office.live.com/browse.aspx/minidump?uc=1&nl=1

     

    this is the minidump file u wanted..

    Tuesday, August 24, 2010 1:19 PM
  • Hi,

     

    First, please provide the information which Andre.Ziegler requested.

     

    Also, please check if this game is compatible with Windows 7 from Windows 7 Compatibility Center or the manufacturers’ websites. And please let me know if there are any changes before the issue occurs.

     

    Now, let’s perform System Restore to the point when the issue hadn’t been occurring.

     

    After that, you may test this issue in Clean Boot and Safe Mode to determine the possible cause.

     

    If it works fine in Clean Boot, the root cause can be the third party software. If the issue reoccurs in Clean Boot, but works fine in Safe Mode, the cause can be the incompatible hardware drivers. You may narrow down the causes in Device Clean Boot.

     

    Device Clean Boot

    =================

    1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter.

     

    2. Expand "Sound, video and game controllers".

     

    3. Right click on your sound card and then click "Properties.

     

    4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK.

     

    5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled.

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article:

     

    How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,

     

    Sabrina

     

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     

    thank you sabrina.. this method is too technical for me.

    you can download the minidump file and if you can not find any solution from minidump , i will try these methods.

    thank you

    DOWNLOAD LINK: 

    http://cid-c8108044de1a3603.office.live.com/browse.aspx/minidump?uc=1&nl=1

    Tuesday, August 24, 2010 1:21 PM
  • Hi,

    1 crash is caused by the driver: kerneld.wnt which is part of Lavasoft Everest. Update the tool please:

    Loaded symbol image file: kerneld.wnt
        Image path: kerneld.wnt
        Image name: kerneld.wnt
        Timestamp:        Mon Jul 25 17:31:46 2005

    because it is too old (from 2005)!!!!!

    2 crashes is caused by the driver:

    Image path: \??\C:\Windows\system32\drivers\FDCDNT.SYS
        Image name: FDCDNT.SYS
        Timestamp:        Thu May 28 16:28:25 2009 (4A1E9F89)

    So update this driver too and the issues should be gone.

    best regards
    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Tuesday, August 24, 2010 2:23 PM
    • Marked as answer by a.d_d.y Thursday, August 26, 2010 9:08 AM
    Tuesday, August 24, 2010 2:23 PM
  • Hi,

    1 crash is caused by the driver: kerneld.wnt which is part of Lavasoft Everest. Update the tool please:

    Loaded symbol image file: kerneld.wnt
        Image path: kerneld.wnt
        Image name: kerneld.wnt
        Timestamp:        Mon Jul 25 17:31:46 2005

    because it is too old (from 2005)!!!!!

    2 crashes is caused by the driver:

    Image path: \??\C:\Windows\system32\drivers\FDCDNT.SYS
        Image name: FDCDNT.SYS
        Timestamp:        Thu May 28 16:28:25 2009 (4A1E9F89)

    So update this driver too and the issues should be gone.

    best regards
    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

    THANK YOU FOR YOUR HELP.. i just need to know 1 thing..  C:\Windows\system32\drivers\FDCDNT.SYS  

    OF WHAT DEVICE IS THIS DRIVER OF??? I WANT TO KNOS SO THAT I CAN UPDATE.

    Tuesday, August 24, 2010 2:26 PM
  • I have no idea. Make a right click on the file and look for the name of the vendor.
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, August 24, 2010 2:38 PM
  • Hi,

    1 crash is caused by the driver: kerneld.wnt which is part of Lavasoft Everest. Update the tool please:

    Loaded symbol image file: kerneld.wnt
        Image path: kerneld.wnt
        Image name: kerneld.wnt
        Timestamp:        Mon Jul 25 17:31:46 2005

    because it is too old (from 2005)!!!!!

    2 crashes is caused by the driver:

    Image path: \??\C:\Windows\system32\drivers\FDCDNT.SYS
        Image name: FDCDNT.SYS
        Timestamp:        Thu May 28 16:28:25 2009 (4A1E9F89)

    So update this driver too and the issues should be gone.

    best regards
    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    THANK YOU... i couldnt find how to solve the issue .. i installed and ran UNIBLUE REGISTRY BOOSTER and it did the work for me.. now the prob is gone..
    Thursday, August 26, 2010 9:10 AM