There's unloaded modules here, my guess is that there was a function call to a driver that was unloaded. Or system corruption had occured.
Quote:
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {50, 6, 0, fffff88002fade0e}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( Unknown_Module_fffff800`00000099>+3098ba7 )
Followup: MachineOwner
---------
|
Here's the indication above.
------------------------------------------------------------------------------------------------------------------------------------------
1) Run Memtestx86 -
http://www.memtest86.com/
2) Run a
Hardware Diagnostics test. If that passes, then move on to driver verifier:
3)
Driver Verifier: Note make sure you backup your data first
Quote:
If you have access to another computer you can contact us through your other working system in case any problems prevent you from getting into Windows. Make a System Restore point as well.
A startup repair disk may assist you in a system restore during boot if you can't get into Windows as well. In Windows 7 you can make a Startup Repair disk by going to Start > All Programs > Maintenance > "Create a System Repair Disc". With Windows Vista you'll have to use your installation CD/DVD or the "Repair your computer" option in the F8/Safe mode boot menu
Follow these steps:
- Go to Start and type in "verifier.exe" and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the BSOD. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 48 hours (recommended) of continuous operation to make sure.
If you can't get into Windows because it crashes too soon, try it in Safe Mode (recommended) or boot from Last Known Good Configuration.
If you can't get into Safe Mode, try using System Restore from your installation DVD or startup repair menu to set the system back to the previous restore point that you created.
|
You're next minidump shows me that there was a system service exception pointing towards your DirectX graphics driver. So what's really happening (my best guess) is a function call to a driver that was either unloaded or corrupted, and it couldn't execute because of excessive paged pool usage and passing bad data to the kernel code from being unable to read the unloaded or corrupted module.
Similar Threads
