BSDO- interrupt_exception_not_handled

[sipep]

Using Windows 7 64bit home premium. New system other than PSU and GPU. Full retail version. Everything is about 3 weeks old but the GPU and PSU. PSU is about 2 years old and the GPU about 10months.

Attached the dump and the system health report.

 

[zigzag3143]

No DMPS included in upload 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.

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.

 

[sipep]

I can't seem to find the windows\minidump folder. I enabled the minidumps when the crashes started happening a few days ago since I was trying to see what they were using BlueScreenView. So to figure out what error I was getting I had to unclick the auto reset box.

I am also not overclocking.

 

[zigzag3143]

I can't seem to find the windows\minidump folder. I enabled the minidumps when the crashes started happening a few days ago since I was trying to see what they were using BlueScreenView. So to figure out what error I was getting I had to unclick the auto reset box.

I am also not overclocking.

I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).