Windows 7: BSOD when transfering large amounts of data

Supertonic · 26 Sep 2012

Hi, im new to this forum so i hope im not breaking any rules by just coming right out with a problem!

i built myself a new computer recently and although it's not the first one i've ever built, i'm certainly no expert. i was getting lots of BSODs right from day 1, but when i swapped out the PSU for a larger one, everything seemed ok.

but when i started copying all my stuff onto the hard drives i started getting BSODs again. whenever i transfer more than a few GB of data, either from one HDD to another, or from a DVD to a HDD, the computer bluescreens.

occasionaly a BSOD will happen out of the blue, even if im not actually doing anything, but transfering more than 4GB or so of data is guaranteed to give me a BSOD.

i tried various diagnostics like memtest86 but everything comes up fine. but when i swapped the system drive for a different hdd with linux, transfering data works fine. so i'm fairly certain it's either some element of windows or the ssd that windows is installed on.

i turned on driver verifier and got another bluescreen, and ran the sf diagnostic so i've attached my dumps

i really hope someone can help me with this, thanks

Arc · 27 Sep 2012

Welcome aboard

► It is Intel Rapid Storage: Frequently.

Code:

*** 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+0x371a80
fffff880`076f3008  fffff800`02e59a63 nt!MmGetPhysicalAddress+0x13
fffff880`076f3010  00000002`1afdb000
fffff880`076f3018  fffffa80`0753598c
fffff880`076f3020  fffff880`0438fa80 dump_iaStor+0x371a80
fffff880`076f3028  fffff800`02e59a63 nt!MmGetPhysicalAddress+0x13
fffff880`076f3030  00000001`5db91000
fffff880`076f3038  fffffa80`07533d8c
fffff880`076f3040  fffff880`076f3420
fffff880`076f3048  fffff880`0438fa01 dump_iaStor+0x371a01
fffff880`076f3050  00000002`1afdb000
fffff880`076f3058  fffff880`040219d7 dump_iaStor+0x39d7
fffff880`076f3060  00000000`00000000
fffff880`076f3068  fffffa80`00000001
fffff880`076f3070  00000001`5db91000
fffff880`076f3078  fffff880`0438fa80 dump_iaStor+0x371a80
fffff880`076f3080  00000000`00000000
fffff880`076f3088  fffffa80`07533d00
fffff880`076f3090  fffff880`0438fa80 dump_iaStor+0x371a80
fffff880`076f3098  fffff880`0438fa80 dump_iaStor+0x371a80
fffff880`076f30a0  fffff880`076f3420
fffff880`076f30a8  00000000`00000001
fffff880`076f30b0  fffffa80`07533d00
fffff880`076f30b8  fffff880`04021cda dump_iaStor+0x3cda
fffff880`076f30c0  fffff880`076f3001
fffff880`076f30c8  fffff880`00842000
fffff880`076f30d0  00000000`00000001
fffff880`076f30d8  fffff880`076f3420
fffff880`076f30e0  fffff880`076f30f0
fffff880`076f30e8  fffff880`04021cda dump_iaStor+0x3cda

Again ....

Code:

fffff880`076f3898  fffff880`01053276Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
 iaStor+0x50276
fffff880`076f38a0  00000000`00000000

I would suggest you to uninstall Intel Rapid Storage Technology. It is nothing needed, just comes as bundled with the drivers pack.

► Moreover, better you uninstall those programs too:

ASUS AI Suite
Auslogics Disk Defrag. Windows 7 does not need such a program, but if any chance it is needed, Puran is the best, and free.

► Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept the restart.

Let us know the situation after applying those changes.

Supertonic · 27 Sep 2012

Thanks Arc, I did all the things you suggested and the problem is solved.

I wish i'd discovered this forum earlier!

Thanks again

Arc · 27 Sep 2012

You are welcome, but dont think it as solved so early, crashes may come back again in another disguise

If you face any further trouble, let us know!

Supertonic · 27 Sep 2012

Yeah, you were right again. i wrote my last post because i just transfered like 90GB of stuff without a problem.

then 5 mins later i got another blue screen! i never turned off driver verifier so i've just run sf diagnostic again

thanks for taking the time to help

Arc · 27 Sep 2012

Supertonic, are you sure that driver verifier is enabled? The answer will play a determining role here.

If no, enable it.

If yes, it is a real memory corruption. In such a situation, you are to check your RAM modules.
RAM - Test with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8884, fffffa8005175b10, fffffa8005175c30, 400}

Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )

Followup: MachineOwner
---------

Whereas, Stop 1A causes by device drivers, too. If verifier is enabled, it must be traced, if any device driver caused it.

Supertonic · 27 Sep 2012

Ok i set up verifier again, and i think i must have done it wrong the first time because this time it couldn't even boot into windows.
so i did a system restore through startup repair and ran sf diagnostic again:

Arc · 27 Sep 2012

Well, let us see ....

► It blames the ISO mounting program that you use.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {215, fffff8800418eeab, fffff98009aece10, 0}

Unable to load image \SystemRoot\system32\DRIVERS\NIWinCDEmu.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NIWinCDEmu.sys
*** ERROR: Module load completed but symbols could not be loaded for NIWinCDEmu.sys
Probably caused by : NIWinCDEmu.sys ( NIWinCDEmu+9eab )

Followup: MachineOwner
---------

I'd suggest you to uninstall that program. WinCDEmu - the easiest way to mount an ISO. And more...

► Auslogics Registry Cleaner will not do any good in your system. The only cleaner that we recommend is CCleaner.

Supertonic · 27 Sep 2012

thanks, ive uninstalled that. i had no idea i even had something called NIWinCDemu! lets see if that helps.

Thanks very much, your help is really appreciated.

Arc · 27 Sep 2012

Quote: Originally Posted by Supertonic

thanks, ive uninstalled that. i had no idea i even had something called NIWinCDemu! lets see if that helps.

Thanks very much, your help is really appreciated.

Have you ever installed any iso emaluator program? may be some leftovers are still there.

Run CCleaners disk cleaner and registry cleaner. It might wipe it out.

Also, check if something with the same name is there ....

C:\Windows\System32\Drivers ; and
C:\Windows\SysWoW64\Drivers.

Windows 7: BSOD when transfering large amounts of data

BSOD when transfering large amounts of data problems?