New
#11
OK, did your system create a \windows\memory.dmp file the last time it crashed, perchance?
Well, the file is no longer there, however from my first post I noticed:
So I have no idea what happened to it *shrugs*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.
Well, the next time you get one, let us know. We'll take a look once you've zipped it up and posted it.
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
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.
Bumpedy bump.
Another crash, another minidump file. Why is it not creating kernel dumps like it should now?
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).
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?
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.