[Jackpot]

Problem description: I ordered new computer parts off newegg.com, and have had nothing but trouble. I tried to install a Microsoft promotional copy of Windows 7 Ultimate 64-bit on my new SSD, but it continually gave me error code 0x80070570 (cannot install required files) at 11% "expanding..". Based on what I read on the Internets, I popped my old XP disc in because it has a "long format" option, and after that Windows 7 installed fine. Or so I thought....

After a week of successful restarts, I can now no longer get past the graphic of window panes coming together. The computer either restarts to black, or blue screens. I can't use the repair option, because that will BSOD. Same with safe mode. Rarely, the computer will boot up, and I can keep the problem from occuring by enabling sleep mode instead of turning the computer off. Obviously, this is not a permanent solution.

Common stop codes:
0x0000000A IRQ NOT LESS OR EQUAL
0x0000007E ---
0x00000050 PAGE FAULT IN NON-PAGED AREA
0x0000001A MEMORY MANAGEMENT
0x000000E4 ---
0x00000034 CACHE MANAGER
c0000221 UNKNOWN HARD ERROR

Here's a link to a recent minidump file if it will help. The BSOD zip is attached, and here is an alternate download location. The main problem I'm having is that it seems that the stop code is different every time. Now, I am still within a time frame to request an RMA with newegg, but what should I replace? Everything? I can't seem to narrow anything down with so many different errors.

Attempted fixes: Memtest ran 9 hours and 14 passes without error, so I think I can rule that out. I also downloaded a bootable Intel SSD firmware update tool, but it told me I was already up to date. I also downloaded the Intel SSD Toolbox, and my drive passed those diagnostic tests. Oh well. I am considering flashing my bios, but I don't have a floppy drive, my flash drive refuses to format using an HP key boot tool, and I don't know what to do at the A:\ prompt using DRDOS with a bootable CD.

Specs:
Windows 7 Ultimate x64
Gigabyte GA-P55A-UD3 P55 Mobo
Intel Core i5 750 CPU
2x2GB G-Skill F3-10666CL8D RAM
EVGA 9800 GTX Vid Card
40GBIntel SSD SSDSA2MP040G2R5 (OS)
1TB SAMSUNG HD103SJ HDD (storage)
Corsair CMPSU-400CX 400W PSU

Please let me know if you need additional information. I will appreciate any help you guys can give me. :smile:

 

[usasma]

Please upload ALL of the minidump files.

The single memory dump blames a Windows file, so I'd also suggest running Driver Verifier according to these instructions:

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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: http://support.microsoft.com/?kbid=244617&sd=RMVP

 

[Jackpot]

I've followed the instructions with an updated minidump file. Hope this helps!

I might as well update this post to report that I've found a USB DVD drive to reinstall Win7 from, in case my IDE drive created errors in my current installation. I'll do that sometime tomorrow and post results.

 

[usasma]

The memory dump that you uploaded is a Verifier Enabled Minidump and it blames the core of the Windows OS - which isn't what we were looking for (the instructions isolate the 3rd party drivers, leaving the Microsoft stuff unverified).

As such it's either a compatibility problem, broken hardware, or a Windows problem.
To check compatibility, look up your hardware and software at this link: http://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspx
For broken hardware, try these additional free tests:

FurMark download site: http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

As for the Windows issues, the reinstallation of Windows will help to rule that out (but I don't expect that this is a Windows problem).

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 14 16:41:38.236 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:10.297
BugCheck A, {fffff80002e9530c, 2, 0, fffff80002ae8662}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[Jackpot]

My mistake; I could've sworn I unchecked all MS drivers. I'll try again soon.

 

[usasma]

No - this is not your fault. There is no need to run Driver Verifier again.
This is a diagnostic criteria that tells us that the problem is either:
- hardware
- Windows
- compatibility

You instructed the Driver Verifier to stress 3rd party (non-Microsoft) drivers. It did that, and yet it failed the kernel of the OS (a Microsoft file). Therefore, the 3rd party drivers are presumed to be OK (or at least in better shape than the Microsoft files).

Since we can't blame the 3rd party drivers, all that's left is what I mentioned above.
So run the tests/lookups that I mentioned in the previous post to see what else we can figure out.

 

[Jackpot]

Roger. I'll start Prime95 overnight.