Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Reoccuring BSOD on previously reliable workstation

14 Dec 2012   #1
WAUX

Windows 7 Professional x64
 
 
Reoccuring BSOD on previously reliable workstation

Hi everyone, I've suddenly been experiencing BSOD issues on a system that's been very solid for the last 2 years. Crashes happen every time I try to load a 3D application or install new software.

I've done as much research as I can and tried the following fixes without success:

-Fresh install of Windows 7 Pro x64
-RAM memtest and physically isolating/rotating the cards
-Change SSD mode from IDE to AHCI and upgraded firmware
-Compete driver update from Gigabyte
-Booted with only critical hardware (video card, SSD, 1 RAM stick)

I hoping that someone more knowledgeable can help me trouble shoot the cause of this as I am at a complete loss at this point. Any advice would be greatly appreciated!


My System SpecsSystem Spec
.
14 Dec 2012   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hello WAUX.

The contributing factor in your Crash is Intel Rapid Storage.
Code:
fffff880`08b8e018  fffff880`02cce20bUnable to load image \SystemRoot\System32\Drivers\dump_iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dump_iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_iaStor.sys
 dump_iaStor+0x4720b
Get rid of intel rapid storage.
  1. Right click on "my computer" icon and click "manage" on the context menu.
  2. It will open the "computer management" window.
  3. Select "Device Manager" in the left pane, It will list all the existing devices up.
  4. Expand "Disc Drives" by clicking on the triangle in front of it.
  5. Select one item under it, right click, uninstall.
  6. Continue the process for all items under "Disc Drives"
  7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.
Also, the bugcheck code is a 0xF4.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8009c70960, fffffa8009c70c40, fffff80002dc3240}

Probably caused by : csrss.exe

Followup: MachineOwner
---------
So here you may need to do some more Disc checks.

  1. Update your SSD's Firmware (Skip it, if it is not a SSD)
  2. Re-seat the sata and power.
  3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
  4. Seatool for dos: SeaTools | Seagate download
    Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
Let us know the results.
My System SpecsSystem Spec
15 Dec 2012   #3
WAUX

Windows 7 Professional x64
 
 

Thank you very much for your detailed response. I completed the first 7 steps you listed, and came up with the following results for the disc checks.

1. Updated SSD firmware - no issues
2. Re-seated sata and power - no issues
3. Ran chkdsk /f/r - "0 bad file records processed"
4. Ran Seatool for dos with the following error:

"Unfortunatly, your Seagate hard drive has failed an important diagnostic test, possibly caused by problem sectors which are difficult to read"

Started Long Test 12/15/2012 @ 16:17.57
Long Test Time out!
Long Test Failed 12/15/2012 @ 16:19.14


BSOD issues remain. Do you feel this is evidence of a failed SSD?
My System SpecsSystem Spec
.

16 Dec 2012   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Better you upload a later crash dump.
My System SpecsSystem Spec
16 Dec 2012   #5
WAUX

Windows 7 Professional x64
 
 

Here are the lasted crash dumps.
My System SpecsSystem Spec
16 Dec 2012   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Apparently your problem is with Intel Rapid Storage. It is very old version that is installed there.
Code:
lmvm iastor
start             end                 module name
fffff880`01052000 fffff880`0116e000   iaStor     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Fri Jun 05 07:23:40 2009 (4A287AA4)
    CheckSum:         000640D7
    ImageSize:        0011C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
I requested Dave76 to guide you to update the driver properly.
My System SpecsSystem Spec
16 Dec 2012   #7
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Your BSoD System File Collection and health reports are not complete, re-upload the complete files requested. The Event Logs are very useful in these type of crashes, they will help us to identify to actual cause.
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.

What size and how many RAM cards do you have?

You have two Western Digital hard drives, add them to your 'System Specs'. If we have a complete list of your system components it will help us to analyze the cause of the crashes.
Run the WD Lifeguard test on each of your HDDs. Quick Test first, if it passes then run the Extended Test.
Data Lifeguard Diagnostic for Windows

Are you running the 'Intel SSD Toolbox' on your SSD?
If not, it's recommended to run it minimum of once a week, download and run it.
Intel® Solid-State Drive Toolbox
If you already have it, check the version number, update it if it is not the newest version.

I have not read anything saying running a HDD diagnostic program on a SSD is bad or causes any problems, but I have never seen it recommended. It's recommended to run SSD diagnostic programs on SSDs.
Use Intel SSD Toolbox and first run the 'Quick Diagnostic Scan' if it passes then run the 'Full Diagnostic Scan'.
Post the results.

You should run Disk Check, as recommended, as you have done and it passed. This indicated the current file system is not corrupted.

Post a snip of your Device Manager > Disk Drives > right click any drive > properties > Driver tab
Should look like this:
Attachment 245980

Post a snip of your Device Manager > IDE ATA/ATAPI controllers > right click the 'Intel' listing > properties > Driver tab
Should look like this, with a different driver version:
Attachment 245982

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Is this your motherboard?
Gigabyte GA-EP45-UD3P
If this is correct, what version is the board? 1.0, 1.1 or 1.6?
There is no EU45-UD3P as listed in your 'System Specs'.
The latest Intel Matrix Storage Manager controller driver listed for the above board is v.8.9.0.1023 date: 2009/08/11.
Your iaStor driver date is Jun 05 2009, which is older than the driver above.
This version will not allow the SSD trim function to work, the first version to allow trim was 9.6.0.1014, over time your SSD will become 'dirty' and quite possibly corrupt.
Install the Intel® Rapid Storage Technology version 11.​2.​0.​1006
The Intel RST drivers after v11.​2.​0.​1006 and up to v11.​6.​0.​1030 (these versions have been removed from the Intel site) are known to have issues with some systems, so use v11.​2.​0.​1006.
There is a new release, v11.​7.​0.​1013, due to some of the previous version problems I recommend to wait until it has been tested before using it.

The 'dump_iaStor.sys' driver listed in a previous post is a separate driver used only for Crash Dump reports and is not the same iaStor driver used by the OS.

The last four crashes, oldest first:
Code:
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes:  Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack.
GetPointerFromAddress: unable to read from fffff80002f07220
Probably caused by : memory_corruption
If the error status is 0xC000000E, it means the disk subsystem has experienced a failure
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096
Followup: memory_corruption
This is indicating the Page File on your SSD/HDD was corrupt.
By default the page file will be on your SSD, have you moved the page file to one of the hard drives?
Memory is also indicated above, it may need to be tested again, likely when info in the RAM was sent to the page file on the SSD/HDD it became corrupt there and when it was returned to the RAM it caused an error.
Running the SSD diagnostic tests and the HDD diagnostic tests will help to find if that is indeed the cause.

The last three crashes are all the same:
Code:
STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION
A process or thread crucial to system operation has unexpectedly exited or been terminated.
Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no
longer function.
IMAGE_NAME:  csrss.exe - Client/Server Runtime Subsystem, or csrss.exe, is a component of the Microsoft Windows NT operating system that provides the user mode side of the Win32 subsystem and is included in Windows 7. It is critical to system operation; therefore, terminating this process will result in system failure.
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_VRF_IMAGE_csrss.exe
2: kd> !process fffffa8009c99b30 3
GetPointerFromAddress: unable to read from fffff80002f0c000
PROCESS fffffa8009c99b30
    SessionId: none  Cid: 0250    Peb: 7fffffd7000  ParentCid: 023c
    DirBase: 20bd72000  ObjectTable: fffff8a000f98180  HandleCount: <Data Not Accessible>
    Image: csrss.exe
    VadRoot fffffa8009d2dc20 Vads 81 Clone 0 Private 2644. Modified 58985. Locked 0.
    DeviceMap fffff8a000007e50
    Token                             fffff8a000f99060
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
    ElapsedTime                       00:00:00.000
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         166888
    QuotaPoolUsage[NonPagedPool]      30768
    Working Set Sizes (now,min,max)  (3538, 50, 345) (14152KB, 200KB, 1380KB)
    PeakWorkingSetSize                7586
    VirtualSize                       77 Mb
    PeakVirtualSize                   100 Mb
    PageFaultCount                    15867
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      2821

        *** Error in reading nt!_ETHREAD @ fffffa8009defb60
These three crashes were blamed on csrss.exe a Windows driver/process, which are usually not to blame, this was the last thing the debuggar has seen and it couldn't find the actual cause so it blames csrss.exe.
Other information is pointing to a page file fault, so the above recommendations should resolve this issue.

These are 'Verifier Enabled Crashes' disable Driver Verifier.
Driver Verifier - Enable and Disable

Let us know if you have any questions.
My System SpecsSystem Spec
27 Dec 2012   #8
WAUX

Windows 7 Professional x64
 
 

I was able to find a fix so I just want to post a quick resolution to this thread. I went on a whim and replaced my motherboard (Gigabyte EU45-UD3P) with an MSI (G41M-P33) which has completely solved all of my BSOD issues. The Gigabyte board appeared to have some physical damage so my guess it that it was entirely a hardware problem. Thank you very much Arc and Dave76 for your time, I really appreciate it. Cheers!
My System SpecsSystem Spec
27 Dec 2012   #9
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Glad to hear you resolved the problem, good work.

Let us know if you have any other questions.
My System SpecsSystem Spec
28 Dec 2012   #10
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by Dave76 View Post
Glad to hear you resolved the problem, good work.

Let us know if you have any other questions.
My System SpecsSystem Spec
Reply

 Reoccuring BSOD on previously reliable workstation




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Reoccuring BSOD after performing clean reinstall factory OEM Windows 7
Hi all, I have been having issues with my pc for about a month now. It has been tough diagnosing what is causing my pc to crash/ prompt BSOD's. I was away for a year and left my pc unplugged and out of use. When I came home, I tried booting it and ran into problems. Cleaned fans/ heat sinks and...
BSOD Help and Support
Previously BSOD Nvlddmkm.sys, now just crashes during gameplay.
I have a fairly new MSI Gt70 gaming laptop that started acting up about 2 months ago when I used driver professional to update all of my drivers in one go. I am using windows 7 home premium 64 bit incidentally that came pre installed on the laptop. My problem: At first after I updated the...
BSOD Help and Support
Clean Win 7 install on new SSD, BSOD out of nowhere, previously stable
Just added a 120gb Patriot Pyro SSD, replaced existing ram with 16gb Patriot DDR3-1333 Kit, and did a clean install of Win 7 Ultimate x64 on my Corsair H50-cooled Phenom II X6 1055t/ Asus M4A89GTD PRO/USB3 machine. Previously was running at 3.8ghz stable. After overclocking from scratch was able...
BSOD Help and Support
Several reoccuring BSODs
This happened on my Win7 Home 64 : It all started with a BSOD connected to my new Creative SoundBlaster Play (USB soundcard). Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 2057 Additional information about the problem: ...
BSOD Help and Support
Reoccuring BSOD
using whocrashed, it only show that ntoskrnl.exe is causing the problem, been going on for 2 months and today it crashed about 6 times...help please
BSOD Help and Support
reoccuring BSOD
Well after not having any BSODs for a few months now I'm suddenly having having a few BSODs that I want to get to the bottom of. My windows 7 is x64 and came with my computer but around July my computer just crashed on me and I had to reinstall around October. I got the computer itself last...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 07:23.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App