Windows 7 Fresh Install(s) - Corrupt/Crash/BSoD(?) - Repeated

natedp · 30 May 2011

Hi all, been browsing this forum for a couple days to try and fix my problem based off other posts but I am at a loss.

I ordered my PC online from iBuyPower (March 2011) and it came pre-loaded with Windows 7 Home Premium 64bit.

My PC ran error-free for 2 months until about 3 days ago, it just would not start up. It went directly to Startup Repair and would say it cannot fix the problem, ask me to restart pc and repeat the same thing.

After multiple Fresh installs, due to BSoDs/Corrupts, I am at a point where I haven't had a BSoD for a number of hours.

BSoD Errors Received (Current Install)

Code:

KERNEL_DATA_INPAGE_ERROR
STOP error 0x7A means that the requested page of kernel data from the paging file could not be read into memory.
 
UNMOUNTABLE_BOOT_VOLUME 
STOP error 0xED means that the I/O subsystem attempted to mount the boot volume and it failed
 
DRIVER_POWER_STATE_FAILURE
STOP error 0x9F means that the driver is in an inconsistent or invalid power state
 
STATUS_SYSTEM_PROCESS_TERMINATED
STOP error 0xC000021A means that an error has occurred in a crucial user-mode subsystem.

Testing/Scans
I have run every "Deep Scan" and "Fix/Repair" associated with all my system repair/cleaner/defrag programs listed in my attachments.

Memtest86+ : ran for 8 passes, complete. No errors.
CHKDSK /f /r: ran to completion. Did not see results...(?)

C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

Notes
My PC is AHCI compatible but in my BIOS I set storage config to Enhanced IDE and Chipset configured to IDE as well.

My Sound Card: Sound Blaster X-Fi Xtreme Audio is connected but I am unable to install drivers from Creative.com (Cannot detect supported device error) and the CD Drivers are wrong for Win7 or Device.

I have not installed any updates through Windows Update yet. Automatic Updates: Off

System Specs

Code:

- Windows 7 64-bit
- Original Installed OS
- OEM - Only have Reinstallation DVD
- System Age: 2 Months
- Fresh Install OS < 24 hours

natedp · 31 May 2011

Updated Thread, hoping it's better formatted for review...

Thanks

natedp · 31 May 2011

I keep getting BSoDs with varying Error Stop Codes (explained on other post) and I downloaded WhoCrashed, but my system is not creating dumps even though it has been enabled since always.

I've run SFC /scannow multiple times and it originally came up with no errors, now it is saying: Windows Resource Protection found corrupt files but was unable to fix some of them.

I could REALLY use some help. My PC is just over 2 months old and I am hoping it is not a Hardware problem...

Edit
Added SFC /scannow report

Also, my last crash restarted to Windows with a Classic theme enabled and I can no longer use any Aero stuff. My Wireless capabilities seem to have disappeared and my Administrative rights dont apply without forcing them anymore...

natedp · 01 Jun 2011

Anyone able to help?

I am still getting various BSoD... seemingly at random.

When my PC is sitting idle
While browsing the internet
During almost every reboot
When Installing software
When attempting to uninstall AVG, corrupted during a restore(?)
When Copying files to/from USB drive and

Recently got Stop Error: PROCESS1_INITIALIZATION_FAILED after installing a couple Windows Update security updates...

My PC still isnt creating Dump files on Crash for some reason.
I have it enabled and I have more than sufficient pagefile space alloted, I even had a fresh pagefile created.

So WhoCrashed.exe isn't going to work until this is resolved...

natedp · 03 Jun 2011

Update: I finally got some BSoDs that actually WROTE a dump file to my drive.

Here is the WhoCrashed report...

Code:

System Information (local)
</B>
computer name: X-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU X 990 @ 3.47GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 6433132544 total
VM: 2147352576, free: 1987850240

Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 6/3/2011 6:22:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060211-37502-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xC4 (0xB2, 0xFFFFF980299D2FC0, 0x4, 0x4)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver called MmMapLockedPages for an MDL with incorrect flags. For example, the driver passed an MDL that is already mapped to a system address or that was not locked to MmMapLockedPages. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 6/3/2011 5:01:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060211-30622-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFF80002F73B60, 0x2, 0x8, 0xFFFFF80002F73B60)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Conclusion
</B>
2 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

If anyone can provide some assitance?

Both of these BSoD occured while I was trying to install ASUS related updates.

Attached is zip file with the jcgriff.exe report and perfmon report...

Windows 7 Fresh Install(s) - Corrupt/Crash/BSoD(?) - Repeated

Windows 7 Fresh Install(s) - Corrupt/Crash/BSoD(?) - Repeated

BSoD - Minidumps/Kernal Dumps Enabled but not Created on Crash!