BSOD During Boot (Graphics Related?)

[ememery]

Hello,

I recently re-installed a clean version of Windows because my system would boot into windows and immediately BSOD. I thought the issue was graphics driver related (Nvidia Quadro 2000) so I ran "Driver Verifier" on the particular display driver. This caused the system to begin to boot into windows with a black screen and cursor, then immediately reboot. So I decided to just break down and do a clean install of Windows 7 x64 Ultimate.

After getting everything back up and running I still have a BSOD every so often, and the graphics don't feel as if they are running stable (mouse lag/jump) when I am running multiple graphics intensive programs on my dual monitors. Most of the BSOD come just as windows boots into the desktop. Also I have inspected the Minidump files with Windbg and It seems I cant find a consistent pattern in the service that causes the crash.

Attached is my .zip containing all of the required minidump etc.

System Specs:
OS: Windows 7x64 Ultimate SP1
Mobo: Asus P8Z68 Deluxe
CPU: Intel i7 2600K 3.4 GHz
GPU: PNY Nvidia Quadro 2000 Driver 306.97
SSD: OCZ Vertex 3

Any help would be greatly appreciated

 

[koolkat77]

Welcome to Seven Forums,

A bug check F4 is usually related to the storage device, in your case:

Model	OCZ-VERTEX3 ATA Device

Please make sure the firmware is updated.

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Go through this thread: http://www.sevenforums.com/bsod-hel...bject_termination-1-hour-after-cold-boot.html

AVG contributes in BSOD-s. Please uninstall it:

AVG | Download tools and utilities​

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

Microsoft Security Essentials, Free antivirus for windows.
Malwarebytes Anti-Malware Free
Good and Free system security combination

​

   Warning

:ar: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start rb:
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it.

• How to run Disk Check on Windows 7

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

If the above does not make the system stable, test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:

• http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Let us know the results.

BSOD BUGCHECK SUMMARY

Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Sat Mar  2 17:58:48.622 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:48.434
Probably caused by : wininit.exe
CRITICAL_OBJECT_TERMINATION (f4)
BUGCHECK_STR:  0xF4_IOERR
PROCESS_NAME:  wininit.exe
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Sun Feb 24 20:04:09.459 2013 (UTC + 6:00)
System Uptime: 0 days 0:02:54.318
Probably caused by : csrss.exe
CRITICAL_OBJECT_TERMINATION (f4)
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Sun Feb 24 19:49:54.584 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:36.443
Probably caused by : wininit.exe
CRITICAL_OBJECT_TERMINATION (f4)
BUGCHECK_STR:  0xF4_c0000005
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: wininit.exe
FAILURE_BUCKET_ID: X64_0xF4_c0000005_IMAGE_wininit.exe
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Fri Feb 22 05:38:43.198 2013 (UTC + 6:00)
System Uptime: 0 days 1:27:12.010
Probably caused by : csrss.exe
CRITICAL_OBJECT_TERMINATION (f4)
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Thu Feb 21 07:03:43.160 2013 (UTC + 6:00)
System Uptime: 0 days 2:09:22.972
Probably caused by : ntkrnlmp.exe ( nt!PopEndMirroring+145 )
INTERNAL_POWER_ERROR (a0)
BUGCHECK_STR:  0xA0
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA0_nt!PopEndMirroring+145
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb 20 10:53:28.099 2013 (UTC + 6:00)
System Uptime: 0 days 0:21:50.005
Probably caused by : csrss.exe
CRITICAL_OBJECT_TERMINATION (f4)
BUGCHECK_STR:  0xF4_c0000005
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411

 

[ememery]

Thanks for the quick and detailed response. I updated bios and Intel chipset graphics driver, removed avg in exchange for WSE. The system seems stable but I will see if that lasts.

However when I ran the SFC /scannow I could not get it to fix the corrupt files.

Thanks again for your help

 

[koolkat77]

Upload the CBS log if possible.

 

[ememery]

Here is the Log file for the CBS.

The system appear to be stable (Two days without BSOD)

 

[NoelDP]

At least part of your problems can be put down to the following problem

2013-03-04 14:39:19, Info                  CSI    000002fd [SR] Repairing 1 components
2013-03-04 14:39:19, Info                  CSI    000002fe [SR] Beginning Verify and Repair transaction
2013-03-04 14:39:19, Info                  CSI    00000300 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-03-04 14:39:19, Info                  CSI    00000302 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-03-04 14:39:19, Info                  CSI    00000303 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
2013-03-04 14:39:19, Info                  CSI    00000306 [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
2013-03-04 14:39:19, Info                  CSI    00000308 [SR] Repair complete

I'll work up a fix protocol, and get back in a few minutes

 

[NoelDP]

I've uploaded a file - emeaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\emeaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\emeaa
or
DIR E:\emeaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\emeaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the (complete new) CBS.log file to your reply

 

[NoelDP]

I've just noticed - the installation of Windows is potentially counterfeit.
You have an apparent ASUS OEM_SLP Key on what appears to be an ASUS retail motherboard.

Please post an MGADiag report,
we need to see a full copy of the report produced by the MGADiag tool
(download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
Once saved, run the tool.
Click on the Continue button, which will produce the report.
To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
- **in your own thread**, please

Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine (or inside the battery compartment), but do NOT quote the Key on the sticker!
How to Tell