Too many BSoD

Page 1 of 4 123 ... LastLast

  1. Posts : 17
    Seven Edition Integrale 64 bits ver: 6.1.7600
       #1

    Too many BSoD


    Hi to all,

    I have too many BSod per day and every time my WhoCrashed give me this message :
    Code:
    Crash dump directory:  C:\Windows\Minidump
    Crash  dumps are enabled on your computer.
    The following dump files were found but could not  be read. These files may be corrupt:
    C:\Windows\Minidump\MEMORY.DMP
    No valid crash dumps have been found on your  computer
    You can find my crash dump here:

    Thanks to all
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    GFXguru said:
    Hi to all,

    I have too many BSod per day and every time my WhoCrashed give me this message :
    Code:
    Crash dump directory:  C:\Windows\Minidump
    Crash  dumps are enabled on your computer.
    The following dump files were found but could not  be read. These files may be corrupt:
    C:\Windows\Minidump\MEMORY.DMP
    No valid crash dumps have been found on your  computer
    You can find my crash dump here:

    Thanks to all

    Unfortunately the DMP file is corrupt and unusable. If you have others upload them.



    Ken
      My Computer


  3. Posts : 17
    Seven Edition Integrale 64 bits ver: 6.1.7600
    Thread Starter
       #3

    the problem is, each new DMP file are corrupt, it's not the first time. But I don't know why.
    Have you any ideas ?
      My Computer


  4. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #4

    Please check this:
    Windows 7:
    Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
    Click on the Advanced tab
    Click on the Startup and Recovery Settings button
    Ensure that "Automatically restart" is unchecked
    Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
    Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
    Click OK twice to exit the dialogs, then reboot for the changes to take effect.
      My Computer


  5. Posts : 17
    Seven Edition Integrale 64 bits ver: 6.1.7600
    Thread Starter
       #5

    Ok thanks for your help, but all that things was done before.
    And the DMP files are still corrupts.
    And although the path is "%systemroot%\Minidump" every new DMP file replace that one in the "Windows" folder. I don't know why. And the "Windows\Minidump" folder stay empty.
    Attachment 79495
      My Computer


  6. Posts : 13,354
    Windows 7 Professional x64
       #6

    Are you using CCleaner or some other cleaning program?
      My Computer


  7. Posts : 17
    Seven Edition Integrale 64 bits ver: 6.1.7600
    Thread Starter
       #7

    Sorry there is no cleaning software (CCleaner or other) installed on this station.
    To day at 18pm I had a BSoD, same probleme, the DMP file is corrupt for Whocrashed, and the DMP file was records outside the Minidump folder...
    Or how to become crazy

    Also, Memtest86+ gives no error.
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #8

    Let's see if we can skirt around the lack of dmps somehow. Please run jcgriff2's scripts on TSF. That gives a ton of data we might be able to use somehow.

    Blue Screen of Death (BSOD) Posting Instructions - Tech Support Forum
      My Computer


  9. Posts : 17
    Seven Edition Integrale 64 bits ver: 6.1.7600
    Thread Starter
       #9

    Thank, here what you asked:
      My Computer


  10. Posts : 13,354
    Windows 7 Professional x64
       #10

    Please remove any programs listed in this link: pxHelp20.sys programs

    I see you have an old driver PxHlpa64.sys, and old drivers can cause BSODs.

    Please update your Walcom Mouse or Touchscreen/pad drivers.

    Your Brother USB drivers should be updated as well.

    Do you see any Adaptec products installed? If so, update or remove them.

    I will say I am just treading on hope here. Without the dmps, we are seriously hurt. As you can see, all I suggested was updating old drivers. We can hope that one of them is the cause.
      My Computer


 
Page 1 of 4 123 ... LastLast

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 15:24.
Find Us