Sure no prob, thanks again!
Sure no prob, thanks again!
OK, I forgot all about this. Thanks for the post, Ill check it out, now. Come back shortly.
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?
Test Hard Drive
Harddrive scan usings SeaTools - SeaToolsfor Windows | Seagate - Both long and shorttests
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.
Problem started before I updated video card. Went to go look for more updates just now but it said my card was up to date. Hm.....
Go to the website and update, not the windows updater.
Okay, just had my first crash post-all the stuff that we did yesterday. It usually seems to happen when I'm watching youtube.
Anyways, I went to Nvidia website and I didn't see my card type on their list of driver updates. I asked it to do a scan to find my card but it said it couldn't do that.
Anyways, here's a log of the crash
OS Version: 6_0_6002
Service Pack: 2_0
Files that help describe the problem:
Can you give me the report? It will give much more information
Sure, here ya go, thanks again!
|Thread||Thread Starter||Forum||Replies||Last Post|
|BSOD: 1000007e||denniscompact||Crashes and Debugging||1||18 Jan 2011|
|BSOD error 1000007e||steelmanac||Crashes and Debugging||3||01 Sep 2009|
|BSOD 1000007e||ahucmu||Vista installation & setup||0||27 Aug 2009|
|BCCode: 1000007e BSOD||Kamil7707||Vista installation & setup||3||05 Apr 2009|
|BSOD, BCCode: 1000007e||Rakanishuu||Vista installation & setup||2||16 Jan 2008|