BSOD "Custom Error"

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 2,528
    Windows 10 Pro x64
       #11

    OK, did your system create a \windows\memory.dmp file the last time it crashed, perchance?
      My Computer


  2. Posts : 27
    Windows 7 Home Premium x64
    Thread Starter
       #12

    Well, the file is no longer there, however from my first post I noticed:

    On Wed 23/03/2011 19:13:38 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFA8005507B60, 0xFFFFF80000B9C510)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    So I have no idea what happened to it *shrugs*
      My Computer


  3. Posts : 2,528
    Windows 10 Pro x64
       #13

    Well, the next time you get one, let us know. We'll take a look once you've zipped it up and posted it.
      My Computer


  4. Posts : 27
    Windows 7 Home Premium x64
    Thread Starter
       #14

    So it just did it again, yet Windows created a minidump not a kernel dump...I have no idea why, seeing as it's set to kernel dump... :l
      My Computer


  5. Posts : 1,782
    Windows 7 Home Premium 64bit
       #15

    I'd like to take a look at the mini dump. Please upload a new report. Also, do not run any system cleaners because it can delete the system dump files.
      My Computer


  6. Posts : 27
    Windows 7 Home Premium x64
    Thread Starter
       #16

    mgorman87 said:
    I'd like to take a look at the mini dump. Please upload a new report. Also, do not run any system cleaners because it can delete the system dump files.
    'Tis attached. I'm not running any, for the record.
      My Computer


  7. Posts : 27
    Windows 7 Home Premium x64
    Thread Starter
       #17

    Bumpedy bump.

    Another crash, another minidump file. Why is it not creating kernel dumps like it should now?
      My Computer


  8. Posts : 2,528
    Windows 10 Pro x64
       #18

    Have a look at the settings in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl, specifically "CrashDumpEnabled" (should be "2") and "DumpFile" (should be "%systemroot%\MEMORY.DMP"). Then, look at the settings under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management, specifically the "PagingFiles" value (if Windows is managing this, it should be blank - if it isn't, let us know).
      My Computer


  9. Posts : 27
    Windows 7 Home Premium x64
    Thread Starter
       #19

    Yup, the top part is correct - yet it just crashed again and gave me another minidump. Minidumps count is set to 50, does that mean it'll do 50 before starting to overwrite the others, or will it do a full dump after that? Just guessing here *shrugs*

    PagingFiles value is "?:\pagefile.sys", ExistingPagingFiles value is "\??\C:\pagefile.sys". Isn't that the default PF location anyway?
      My Computer


  10. Posts : 2,528
    Windows 10 Pro x64
       #20

    It means it's configured - you probably want to disable the paging file entirely, and then reboot. Once rebooted, delete pagefile.sys, and reboot again. Once back in, set the paging file size to be windows managed and reboot a third time. Assuming you reboot and it crashes again, you should get a dmp file in \Windows\ at that point.
      My Computer


 
Page 2 of 3 FirstFirst 123 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 03:01.
Find Us