|01 Jan 2012||#2|
| || |
No attachments uploaded try this method.
We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
If you are overclocking STOP
You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under 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 (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
|My System Specs|
|01 Jan 2012||#4|
| || |
These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
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 disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) 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 Blue Screen. 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 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Using Driver Verifier to identify issues with Windows drivers for advanced users
|My System Specs|
|Similar help and support threads for2: My computer is starting to have BSOD, error 0x0000000a ntoskrnl.exe|
|BSOD (random) possibly after computer when to sleep, error 0x0000000A||BSOD Help and Support|
|BSOD while looking around computer error 0x0000000A||BSOD Help and Support|
|BSOD while starting the computer , 0x0000000A csrss.exe ntkrnlmp.exe||BSOD Help and Support|
|BSOD when left kaspersky scanning the whole computer, error 0x0000000a||BSOD Help and Support|
|BSOD ntoskrnl.exe with 0x0000000a||BSOD Help and Support|
|Windows 7 BSOD -0x0000000a ntoskrnl.exe||BSOD Help and Support|
|0x0000000a + IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe random BSOD, help :S||BSOD Help and Support|