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: PC BSOD when installing/updating windows/and other instances as well

20 Apr 2012   #1

7 Pro x64
 
 
PC BSOD when installing/updating windows/and other instances as well

Hi Guys

Thanks in advance, just did a fresh install of win 7 x64 pro on an old kingston ssd v series.

System:
win 7 pro x64 (upgrade disk)
i5 2400
h61 mobo chipset
gtx560
8gb g.skill ripjaws-x
64gb kingston ssd v series
320gb wd blue scratch drive (games/data)

Just updating windows and it will always show a bsod. also tried installing programs/games, it'll show bsod as well.. Here's the details of the error:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 3081

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002ECF6EC
BCP3: FFFFF8800698CF60
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\042012-12043-01.dmp
C:\Users\Charles\AppData\Local\Temp\WER-20623-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Thanks guys! Any help would be appreciated.

My System SpecsSystem Spec
.

20 Apr 2012   #2

7 Pro x64
 
 

Sorry guys, please find attached performance report + other test.
My System SpecsSystem Spec
21 Apr 2012   #3

Windows 7 Home Premium 64 Bit
 
 

Security Software (this is to check that it is installed and working properly; nothing needs to be done with this information at this time):
Code:
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	244	8	200	1380	20/04/2012 11:40 PM	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	2968	8	200	1380	20/04/2012 11:40 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 2:35 PM

Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\monggoking\Windows_NT6_BSOD_jcgriff2\042012-12043-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16973.amd64fre.win7_gdr.120305-1504
Machine Name:
Kernel base = 0xfffff800`02e18000 PsLoadedModuleList = 0xfffff800`03054e70
Debug session time: Fri Apr 20 07:40:08.548 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:36.532
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ecf6ec, fffff8800698cf60, 0}

Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+1c )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ecf6ec, Address of the instruction which caused the bugcheck
Arg3: fffff8800698cf60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiCaptureProtectionFromProto+1c
fffff800`02ecf6ec 488b01          mov     rax,qword ptr [rcx]

CONTEXT:  fffff8800698cf60 -- (.cxr 0xfffff8800698cf60)
rax=0000000000000011 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8800698da88 rsi=fffffa80081a9618 rdi=fffffa80069d4060
rip=fffff80002ecf6ec rsp=fffff8800698d930 rbp=0000000000000001
 r8=000000000ac07000  r9=fffffa80081a9280 r10=0000000000000000
r11=fffff80003087b80 r12=0000000000000011 r13=fffff68000056030
r14=fffff8800698da80 r15=000000000ac06000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!MiCaptureProtectionFromProto+0x1c:
fffff800`02ecf6ec 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ecf6ec

STACK_TEXT:  
fffff880`0698d930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiCaptureProtectionFromProto+0x1c


FOLLOWUP_IP: 
nt!MiCaptureProtectionFromProto+1c
fffff800`02ecf6ec 488b01          mov     rax,qword ptr [rcx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiCaptureProtectionFromProto+1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558ca0

STACK_COMMAND:  .cxr 0xfffff8800698cf60 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiCaptureProtectionFromProto+1c

BUCKET_ID:  X64_0x3B_nt!MiCaptureProtectionFromProto+1c

Followup: MachineOwner
---------
Code:
Event[0]:
  Log Name: System
  Source: Ntfs
  Date: 2012-04-20T23:56:51.190
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gaming-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.
  • If you are overclocking any hardware, please stop.

  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
    For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run disk check again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.
My System SpecsSystem Spec
.


21 Apr 2012   #4

7 Pro x64
 
 

Thanks for your help. I'm still trying to figure out the main cause. What I've figured out so far is that, whenever I pull out 1 RAM stick and leave 1 running - doesn't matter which stick and which slot - I've tried all possible combinations, system is perfectly stable. No issues or anything. As soon as I plug in the other stick - dual channel mode, everything goes feral. Random BSODs, weird lines on windows desktop, Won't be able to open My docs, Can't update windows, and a lot more. But to say it again, as soon as let system run in single channel mode, everything mysteriously works fine!

What could be the prob?

Mobo: Asus P8H61-LE-M/USB3
RAM: G.Skill Ripjaws-X 8GB (2x4GB) 9-9-9-24 1.5V


Thanks heaps!
My System SpecsSystem Spec
21 Apr 2012   #5

Windows 7 Home Premium 64 Bit
 
 

From the logs, things are pointing more toward data corruption than memory. Both work together by writing data into memory and back to disk. Is your firmware up to date for the ssd? What about the BIOS? Chipset drivers? Hard disk controller drivers?

I unfortunately am unable to access your motherboard site at this time. The site is loading very slowly and may be down.
My System SpecsSystem Spec
21 Apr 2012   #6

7 Pro x64
 
 

bios - i know is outdated, i've dloaded the updated one. will try and update bios tomorrow. pretty late here in sydney already.

ssd - my particular model doesnt have updates (correct me if im wrong)

chipset and other mobo drivers - i got the updated ones yesterday from asus's site.


pc is running very stable now with one ram stick. could be just aesthetics, there still might be underlying issues... it's the first time i've encountered this situation. very strange.


thanks so much for your help writhziden. appreciate it mate.
My System SpecsSystem Spec
21 Apr 2012   #7

Windows 7 Home Premium 64 Bit
 
 

When you flash the BIOS, do so with one RAM if that is providing more stability. Any interruption to the flash can render the system useless, so it is best to do everything possible to avoid any crashes during the flash.

And you're right: there do not seem to be any available firmware updates for that SSD.
My System SpecsSystem Spec
21 Apr 2012   #8

7 Pro x64
 
 

thanks mate. i'll flash the bios soon. i'll let you know of the outcome.
cheers.
My System SpecsSystem Spec
22 Apr 2012   #9

7 Pro x64
 
 

bios update seemed to have improved things. no bsods anymore up until now (5hrs running).

weird lines were showing on the desktop even before the update, and even after the update, it still showed up randomly. see pic below.

http://i41.tinypic.com/i39naq.jpg

cheers.
My System SpecsSystem Spec
22 Apr 2012   #10

Windows 7 Home Premium 64 Bit
 
 

Have you tried re-seating your graphics card? Make sure the contacts between the card and your motherboard are clean, too. If you re-seat components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
My System SpecsSystem Spec
Reply

 PC BSOD when installing/updating windows/and other instances as well





Thread Tools



Similar help and support threads for2: PC BSOD when installing/updating windows/and other instances as well
Thread Forum
BSOD when installing/updating WoW BSOD Help and Support
Frequent and Various BSODs while installing/updating and on Youtube. BSOD Help and Support
BSOD after updating windows and installing softwares BSOD Help and Support
Solved BSOD updating windows BSOD Help and Support
Installing and updating software under 7 Software
Installing and updating drivers in 7 Tutorials
Imported Admin from XP stopping installing or updating General Discussion

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 12:53 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33