Random different BSOD's tried many things

Page 2 of 2 FirstFirst 12

  1. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #11

    Blikkie said:
    No I can't because when I enable driver verifier and then do a reboot to complete the setup. It will cause an instant BSOD at windows start-up! I dont even get to see the desktop. It loads and than BAM: BAD_POOL_CALLER.

    Then I have to load a restore point to a previous working configuration.

    Must be a driver issue than right?
    Thats the idea, so we can see what is causing the BSOD.

    Once you receive your BSOD, upload the new DMP Files :)
      My Computer


  2. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #12

    Ok. I think there's a misunderstanding here.

    I cannot upload .DMP files because they do not appear in the folder "minidump" or anywhere else on my HDD. There is no 'minidump.dmp' or MEMORY.dmp file anywhere on my computer. My computer simply does NOT write a dump file after a crash even though message in the BSOD says "Physical memory dump complete".

    I tried everything to fix this but nothing helped.
      My Computer


  3. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #13

    Okay sorry i missed that have a read of this :)

       Information

    If your computer is not creating DMP Files please follow this link: Dump Files - Configure Windows to Create on BSOD

    I look Forward to Helping you.
      My Computer


  4. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #14

    As I mentioned before, I also followed those instructions. I even downloaded the Create_Minidump_on_BSOD.reg file which also has no effect.

    As you can see in the attached image all settings are registered correct. I also Added a D_WORD entry AlwaysKeepMemoryDump to prevent windows 7 from removing the file at start-up. But that also doesn't work.

    I give up
      My Computer


  5. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #15

    Blikkie said:
    As I mentioned before, I also followed those instructions. I even downloaded the Create_Minidump_on_BSOD.reg file which also has no effect.

    As you can see in the attached image all settings are registered correct. I also Added a D_WORD entry AlwaysKeepMemoryDump to prevent windows 7 from removing the file at start-up. But that also doesn't work.

    I give up
    Once you have changed the settings you will need to restart the computer, then next time you have a BSOD you will be able to use the SevenFoums tool to retrieve the DMP Files.
      My Computer


  6. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #16

    I did fresh install of Windows 7, installed all drivers and updates. I hoped for the problem to disappear but I got a BSOD during the installation of updates.

    But!, after the fresh installation my computer does write dump files!!!

    Here's the link to the DUMP file:
    https://drive.google.com/file/d/0Bzx...it?usp=sharing

    I really hope you can help me solve this Harrie! Thank you for all the effort.
      My Computer


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

    Sorry for the double post. I attached another dump file. This time a minidump.
      My Computer


  8. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #18

    In the meanwhile I ran memtest86 for another 8 passes. It found no errors so I think the RAM is fine.

    I downloaded Bluescreenview to check my own dumpfiles. It seems that the errors are completely random.
    Also the .sys files tagged by the application are different.

    Most of the times the error is: IRQL_NOT_LESS_OR_EQUAL but there also different errors: DRIVER_PORTION_MUST_BE_NON_PAGED, MEMORY_MANAGEMENT, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

    I am going to return the laptop to my retailer to have it cleaned up. I think dust is the problem. I will let you guys know if the problem is solved by then.
      My Computer


  9. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #19

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {411, fffff683ff804df0, 8ee00002f0260886, fffff683bf804df1}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )
    
    Followup: MachineOwner
    ---------
    
    7: kd> !thread
    GetPointerFromAddress: unable to read from fffff80002eb9000
    THREAD fffffa800ca93040  Cid 0004.009c  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 7
    Not impersonating
    GetUlongFromAddress: unable to read from fffff80002df8ba4
    Owning Process            fffffa800ca76040       Image:         <Unknown>
    Attached Process          fffffa8010551900       Image:         CCC.exe
    fffff78000000000: Unable to get shared data
    The .dmp file is inconclusive, but there is a small clue : please uninstall Catalyst Control Center, reboot and do the following:

    Please do the following:

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode
      My Computer


  10. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #20

    Golden said:
    The .dmp file is inconclusive, but there is a small clue : please uninstall Catalyst Control Center, reboot and do the following:

    Please do the following:

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode
    Thank you so much for analyzing my dump file! I did a fresh install of windows 7 (again) because all the crashes corrupted Windows Updates and my system files.

    I installed the most important components: chipset driver, Intel Management Engine, LAN driver and USB 3.0 drivers. I left the other components as well as the AMD Radeon Graphics driver uninstalled.
    I then successfully installed all windows update and had no BSOD for the past 6 hours!!

    I will now make a system restore point and try to install the AMD graphics driver as well.

    But first I have a couple of more questions:


    1. Is it okay to update all components to the latest version using Windows update?

    2. The AMD Graphics Auto detect tool says its best to download driver version 14. But, on the motherboard manufacturers website (CLEVO) the latest version available is version 9. Which one should I use?

    3. My laptop also has an on board graphics chip; Intel graphics 4000 family. I haven't installed the on board Intel switchable graphics driver yet. Should I do this first, before installing the AMD driver?
    And should I download the latest version from the Intel website or should I download the driver offered by CLEVO (older version)?

    I hope you can answer my questions, thanks again!
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 09:19.
Find Us