Random BSOD's, error 0x0000001e

For the past few months, my computer has been randomly deciding it doesn't like whatever i'm doing, and having a good ol' fashioned BSOD. It very rarely lets me know what the error is before restarting, so if it's due to any other errors, i don't know what they are - i only got this code from it recrashing while dumping the memory to disk.
I've tried a few basic things to try and sort it out (cleaned the registry, run various mal/spy/whateverware programs, etc), but i'm not that experienced with fixing computers - generally it comes down to a quick google search for the offending error.
The first BSOD's came immediately after my computer spent a month disconnected from the internet, and initially seemed down to Norton Antivirus (it came free, i thought the worst that could happen was that it wouldn't be very effective), due to various errors stopping once it was removed, but it's continued, and i can't work out any connection between the crashes and the programs i'm running at the time - it can crash 5 times in a day, or not have any problems for 2 weeks.
As far as i know, all the drivers are up to date, but again, i'm not that experienced - there may be ones i had no idea even existed.

Also, please, in your answers, treat me like i'm good at following instructions but a little thick. I'll be happy to give you any additional information you need, but don't assume i'll automatically know exactly what you mean, and if possible, link to any programs i might need.

Thanks.

NuklearAngel said:

For the past few months, my computer has been randomly deciding it doesn't like whatever i'm doing, and having a good ol' fashioned BSOD. It very rarely lets me know what the error is before restarting, so if it's due to any other errors, i don't know what they are - i only got this code from it recrashing while dumping the memory to disk.
I've tried a few basic things to try and sort it out (cleaned the registry, run various mal/spy/whateverware programs, etc), but i'm not that experienced with fixing computers - generally it comes down to a quick google search for the offending error.
The first BSOD's came immediately after my computer spent a month disconnected from the internet, and initially seemed down to Norton Antivirus (it came free, i thought the worst that could happen was that it wouldn't be very effective), due to various errors stopping once it was removed, but it's continued, and i can't work out any connection between the crashes and the programs i'm running at the time - it can crash 5 times in a day, or not have any problems for 2 weeks.
As far as i know, all the drivers are up to date, but again, i'm not that experienced - there may be ones i had no idea even existed.

Also, please, in your answers, treat me like i'm good at following instructions but a little thick. I'll be happy to give you any additional information you need, but don't assume i'll automatically know exactly what you mean, and if possible, link to any programs i might need.

Thanks.

Hello & welcome,
Re cleaning the registry...

> If you do not have knowledge of the registry, then you would probably be better off leaving it alone, and definitely not placing blind trust in a program to do the job for you.

To advise anyone that a "Registry Cleaner" works, and that it will fix or speed up their machine {or all the other nonsense that is often propagated about these things} can mislead people.

Should you decide to go ahead -
Make sure you have
1.a current System Restore point created.
2.a recent "Back up" of your computer- preferably to an external HD.




> 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.

The procedure:

* 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.

To ensure minidumps are enabled:

* 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.

Ah, i didn't know that. My more computer literate friends had advised using CCleaner, but i guess they think i know more than i do...

The minidumps setting was originally set to Kernal Memory Dump instead of Small Memory Dump, so i don't know if these are useful or if i'll need to wait for it to crash again, but i've attached them anyway.

These crashes were caused by memory exception. (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!!!


1-Memtest.

*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.

RAM - Test with Memtest86+



2-Driver verifier

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/Win7 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.

Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users