As you have indicated the reports do indeed show a code 7E. In generic terms this error usually indicates:
hardware incompatibility, a faulty device driver or system service, or some software issues.
This particular type of error report is very common and as you can see many possible causes. If you have installed new hardware or software please uninstall boot and try the computer. If this is not your situation. Lets start with a memory test. Guide to using Memtest86+ - Geeks to Go Forums
The test should be made for 6 pases (usually overnight is the best time). Then take a good stick and test each slot for 3 passes.
If these tests are negative report back and we shall try to test your drivers, which is a very likely possiblity, too.
The next test with the most potential is a driver verifier. Please run the verifier after a few more BSODs, please post the the dump reports again.
I'd suggest that you firstbackup your data and then make sure you've got access to another computer soyou can contact us if problems arise. Then make a System Restore point (so youcan 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....AllPrograms...Maintenance...Create a System Repair Disc - with Windows Vistayou'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 useyour system normally, and if you know what causes the crash, do thatrepeatedly. The objective here is to get the system to crash because DriverVerifier isstressing the drivers out. If it doesn't crash for you, then let it run for atleast 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 yourinstallation DVD to set the system back to the previous restore point that youcreated.
Hello so I used the verifier/stresser and upon rebooting the computer immediately crashed. System repair kicked in and scanned for errors. Says it couldn't fix errors, so I restarted/scanned a few more times and it said it fixed the errors. I'm back on my computer, crossing my fingers that the worst is over.
Sorry, but I doubt that the errors fixed will solve the BSODs. Try to use the verifier, if you cannot just keep the reports coming in. Maybe will will uncover something.
Check to see if you did get a new BSOD report with the last crash, if so upload to us.
Hello, alright I think I'm a little confused on how to use verifier. When I used it, it crashed the computer and gave me the option of going to windows repair or to start window again normally, which doing so would just cause the crashing to go again.
Anyways, here's a new report, hopefully a clue will present itself.
The way the verifier works is that it causes BSODs and the reports give the name of the problem driver.
You have said that you enabled Verifier and crashed. There are no new reports. Your crash was probably not a BSOD and had other causes. Try the verifier once again, be sure you have done it correctly and report back with the latest reports. If they are the same as before, we will have to proceed differently.
Maybe you can help me. Here are the causes of 7E.
Look it over have you done anything recently that can account for any of these problems? Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
Check your hard drive space
Take a hard drive test.
Go to device manager, update your video card driver
Install any new hardware?
Would you mind if we skipped verifier, it's just last time I tried it I couldn't get it out of that crash cycle and for some reason that one time it stopped crashing.
I downloaded SeaTools and when I ran it, it said "Fatal Error: Device Discovery - Argument 'Length' must be greater or equal to zero. System. String Mid (System.String, Intl32, Int32)
As far as other causes. I still have half of my disk space free, no new software installed. I've downloaded pretty much all of windows updates. I haven't touched BIOS, I updated my video card a couple weeks ago. These other possibilities you mentioned I'm not really sure what they are but pretty sure I haven't changed them.
That SeaTools error usually means that your hard drive cant be tested. It is the same with mine, I bet you have a Sata.
Updated video card; did the problem start about that time? If yes. Go to device manager, (type those words in search by the start button). Upadate the video driver. Look for any small yellow markers near any driver.