Solved BSOD when downloading larger files (including Windows Update)

[Icuic]

Fresh install of Windows 7 Pro 64 on this machine and it seems to BSOD when downloading large-ish files including Windows Update.

During the Windows Update, it either freezes or BSOD when trying to download too many, and when downloading a larger file I get BSOD.

File attached as per instructions. Hope someone can shed some light on this issue.

Ta muchly in advance

 

[koolkat77]

Start Menu\Programs\GIGABYTE	Public:Start Menu\Programs\GIGABYTE	Public
Start Menu\Programs\GIGABYTE\AutoGreen	Public:Start Menu\Programs\GIGABYTE\AutoGreen	Public
Start Menu\Programs\GIGABYTE\ET6	Public:Start Menu\Programs\GIGABYTE\ET6	Public

Gigabyte EasySaver (and EasyTune6 if installed) will cause BSOD's on some Windows 7 systems. Please uninstall it.

Start Menu\Programs\Avira	Public:Start Menu\Programs\Avira	Public
Start Menu\Programs\Avira\Avira Desktop	Public:Start Menu\Programs\Avira\Avira Desktop	Public
Start Menu\Programs\Comodo	Public:Start Menu\Programs\Comodo	Public
Start Menu\Programs\Comodo\COMODO Firewall	Public:Start Menu\Programs\Comodo\COMODO Firewall	Public
Start Menu\Programs\Comodo\GeekBuddy	Public:Start Menu\Programs\Comodo\GeekBuddy	Public

Security App
Avira and Comodo are known to cause BSOD's. Please remove and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software

Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free

   Warning

DO NOT start the free trial of MalwareBytes, unselect that option when prompted.

   Tip

Make full scans with both separately.

Basic checks:
Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

 

[Icuic]

koolkat77

Thanks so much for the advice. I'm running through the list now and I will post back with the results. Fingers crossed!

 

[koolkat77]

Will be here for an update, good luck

 

[Icuic]

As it was a clean install, I just formatted and reinstalled and just installed the drivers. Going to run the checks on the HD and Ram now.

 

[Icuic]

I let the Ram checker run for 2 passes (will let it go longer) and it passed. Then after rebooting let Windows Update run.

When concerning a .net 4 update, the updater froze and the crashed out to a BSOD again. Before the reinstall, I was getting error messages relating to a .net installation that was initiated and the computer would freeze and the BSOD out.

I try to run the diagnostic tool linked here but it stopped responding half way through (I think the System Information tool was causing a problem). Attached what it managed to collect.

I'm going to check the HD (If anyone can let me know if there is a Sandisk SSD tool to use that would be great) and then let the Ram test run when I pop out.

Any ideas would be greatly appreciated. The PC was custom built so if there could be anything to check (loose cables etc) then please let me know.

 

[Icuic]

Just another update. When running Windows Update, I managed to install all Security patches but when trying to update anything related to .net it hangs for a moment then BSOD.

Second update: Tried installing the .net framework directly and again, BSOD.
Also, when installing Graphics Card drivers, I had a BSOD when it came up with a message about .net. When retrying I unticked the nVidia experience box and there was no mention of .net and it installed fine.

Hope this information helps.

 

[Arc]

You are having a hardware problem, but which part of the hardware is failing is not specified.

Continue with memtest ....
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Do some Disc checks.

1. Update your SSD's Firmware, SanDisk SDSSDH2128G ATA Device
   SSD Toolkit support information
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.
   (3 and 4 are for the Seagate HDD only)
5. Post a screenshot of your SSD and HDD using CrystalDiskInfo - Software - Crystal Dew World

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Also, how old the build is?

For a security reason, scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

________________________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff88002fbcb70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff88002fbcb70
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff80003012818 to fffff800030c81c0

STACK_TEXT:  
fffff880`02fbcb38 fffff800`03012818 : 00000000`0000009c 00000000`00000000 fffff880`02fbcb70 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fbcb40 fffff800`03011f57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`02fbcc90 fffff800`03005e88 : 00000000`3d2f4f3a 00000000`00000002 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`02fbccc0 fffff800`030c6aac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fbccf0 fffff800`030c6913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fbce30 fffff800`030fdbb1 : 00000000`00000000 fffff880`0a832380 00000000`00000000 fffff800`030d47e8 : nt!KiMcheckAbort+0x153
fffff880`0a832300 fffff800`030cd01c : 00000000`00000000 fffff880`0a832448 00000000`00000000 fffff880`0a832400 : nt!KxFlushEntireTb+0xcd
fffff880`0a832340 fffff800`030fe053 : fffff880`0000131b 00000000`00000000 fffff800`03049000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`0a832410 fffff800`030cd234 : 00000000`00000008 fffff800`03274f60 00000000`00000000 00000000`00000000 : nt!MiReplenishBitMap+0x468
fffff880`0a832520 fffff800`030e2eeb : fffff880`00000000 fffff800`032757a8 00000b72`00010f24 00000000`00010f25 : nt!MiEmptyPteBins+0x10d
fffff880`0a832570 fffff800`03369122 : fffff880`0a832700 fffff880`0000ef17 fffff700`00000001 fffff880`0a832b60 : nt!MmMapLockedPagesSpecifyCache+0x74c
fffff880`0a832640 fffff800`03368c7f : fffffa80`0727e620 00000000`04ca0a50 fffffa80`072a8b30 00000000`06260020 : nt!MmCopyVirtualMemory+0x436
fffff880`0a8329f0 fffff800`030c7453 : fffffa80`06dcfb50 00000000`0011e088 fffff880`0a832a88 00000000`0000017c : nt!NtReadVirtualMemory+0xff
fffff880`0a832a70 00000000`76ea170a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0011e068 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ea170a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KxMcheckAbort+6c
fffff800`030c6aac 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KxMcheckAbort+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

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

 

[Icuic]

Running some of the other checks now, CPU first.

It did crash out shortly after running the CPU check first, will try again to see if that's the issue.

The build is new, only built this weekend. The MB, CPU and RAM and bought as a bundle from overclockers and are overclocked before shipping, and tested I thought...

The temps seem fine (nothing higher than 31-2) on normal usage and directly after a crash they don't seem any higher (will double check that).

 

[Icuic]

Computer drops to a BSOD almost instantly when trying to run Prime95.

Last minidump files attached. Does this look as the the CPU is the culprit?

 

[Arc]

Have you taken the disc checks? What is the result?

Have you run the virus checks? What is the result?

What is the heat of the system after suing a reasonable time?

There is an indication of hardware failure in the last dump, but CPU failing itself is a very rare situation. It fails when it is physically damaged, not properly seated, or overheating.

So we need these results too, to draw an inference.

 

[Icuic]

Virus check comes back fine (fresh install too).

Temperatures stay nice and low for everything.

Screenshot attached from DiskCheck.

Also, run the memory test overnight and no errors reported.

 

[Icuic]

After another fresh install after rewiring some hardware and such, things seem more stable. Going to run the checks again.

Fingers crossed.

 

[Arc]

What are the hardware components you have renewed?

 

[Icuic]

Checked the wires on the HDs. Reseated graphics card. Reseated heatsink. Reset BIOS to defaults.

Still going through the checks as you've all suggested and so far so good.

Fingers crossed still.

 

[Arc]

Best of luck

 

[Icuic]

No BSOD of death yet. I've run Prime95 and Graphic BenchMark test.

I'm going to mark this as solved. I think some hardware must not have been installed correctly.

Thank you both for your help, would have been lost without it. The diagnostic tools and guides you guys linked to were invaluable and will go on my tool USB stick right away for future use!

 

[Arc]

Good to know
For any further issue, let us know.