BSOD at random times. Different types of Errors but mainly 0x0000007E

Nispar101 · 03 Apr 2012

I have just bought this computer and have constantly had multiple BSOD occurrences a short while after first use. This computer is brand new, Custom Built. While it was at Cyberpower HQ it underwent Quality control to test the hardware's compatibility with each other which it passed. I have tried to fix these BSOD's by myself but to no avail so I decided to ask the forums :). Here is some basic info on my Computer.

Windows 7 is...
64-bit
The originally installed OS (no other OS has been installed)
Full Retail version.
Hardware is brand new.
Installed OS about a month ago (When the computer was received).

If any more info is needed please ask.

I've also attached the requested zip file in accordance with the BSOD Posting Instructions.

UPDATE: I recently reinstalled my entire OS, updated all of the possible windows updates, installed all of the drivers I have in order to attempt to fix this issue. At first I had thought that It had worked, because when I first started it up it was running pretty smoothly. However, I have had 4 different blue screens within the past 2 days. I have a new system report and now I finally have DMP files. (Yay!) So I have attached them in this post.

zigzag3143 · 03 Apr 2012

No DMPs included in upload

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.

Nispar101 · 03 Apr 2012

Ah I see. Memory dumping must not have been enabled. I enabled it according to your instructions and will upload the next dump next time the BSOD occurs. Thanks for the reply!

zigzag3143 · 03 Apr 2012

Nispar101 said:

Ah I see. Memory dumping must not have been enabled. I enabled it according to your instructions and will upload the next dump next time the BSOD occurs. Thanks for the reply!

Good Luck

Nispar101 · 04 Apr 2012

I crashed again. With the same 0x0000007E error. However, this time even with the setting's changed in system and recovery no DMP file was generated. That or it is hidden from me. If I went into safe mode with networking would if find the DMP file or would it just generate the DMP file (without crashing) when the computer reaches a state at which it would normally crash?

EDIT: I did check the system and recovery options and they remained the same. They still say what your instructions directed me to change them too.

EDIT 2: I have crashed again and could not find the DMP file again, and am now in safe mode with networking. Hopefully, I can catch the DMP file.

EDIT 3: Crashed again in safe mode. With same error. Rebooted to again not find a DMP file... I'm so confused as to why it is not being generated! I'm going to try to get the file by changing the directory that the file is generated to the new folder of C:\Minidump that I just created and see if it will generate there. Which did not work... Because I crashed again and it is not there.

Nispar101 · 06 Apr 2012

More new DMP files to go with the new DMP files in my update in my initial post. They all seem to be different so this is really throwing me off.

zigzag3143 · 06 Apr 2012

Nispar101 said:

More new DMP files to go with the new DMP files in my update in my initial post. They all seem to be different so this is really throwing me off.

Both of the most recent were memory exceptions.

These crashes were caused by memory corruption/exception (Cx05) 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!!!

* If you have raid update its Driver.

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

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.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Nispar101 · 06 Apr 2012

Per a freind's request (because a friend of mine is helping me out as well.) I had already run Memtest86+. It ran about 6 passes and found no errors. I am trying out Driver verifier now. I have no RAID drivers or devices installed. Everything on here is ATA/ATAPI or IDE. I am also not overclocking anything because all devices at stock speed are already fast enough for me.

Nispar101 · 06 Apr 2012

Here is the latest crash with Driver Verifier.

zigzag3143 · 06 Apr 2012

Nispar101 said:

Here is the latest crash with Driver Verifier.

Verifier is an "iffy" proposition. In this crash it points to an OS file which is unlikely. I would turn it off and run a system file check

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

If that comes back no violations found I would turn verifier back on with "all drivers" checked. That will look at all the drivers on the computer (it may make the computer a bit slower)