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: BSOD When browsing with Chrome and using R

15 Oct 2012   #1

BSOD When browsing with Chrome and using R

I did a clean install of Windows 7 along with an SSD upgrade (M4) on a friend's laptop (Toshiba E105-S1402) and soon after returning it to her she started experiencing some BSODs. I was rather concerned that I may have installed a faulty SSD drive. But then she told me it was okay and that she had gotten used to the BSODs.

Well, had I known this was a previous issue I would have done a memory test to see if there was faulty ram, but alas I didn't know and didn't think of doing it. In any case, the BSOD does seem to occur when she's browsing with Chrome and multiple tabs are open and she is using the software R. Maybe it's just coincidence but I thought I'd ask for some help here before I have her send her laptop back to me needlessly if it's something that can be fixed remotely.

Computer Specs
Windows 7 - 64-bit
Intel Mobile Core 2 Duo P8400 @ 2.26 GHz
RAM - 4.00 GB Dual Channel DDR2 @399MHz (6-6-6-18)
Mobile Intel 4 Series Express Chipset Family
.NET Frameworks installed v4.0 Client, v3.5 SP1, v3.0 SP2, v2.0 SP2
Windows Provided Info:
BCCode: 7a
BCP3: 0000000036EF0860
BCP4: FFFFF88000DB5630
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

I'm also attaching a photo of the first BSOD she got which seems different from the 7a one listed just above.

Thanks in advance, folks.

My System SpecsSystem Spec
15 Oct 2012   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Hello Johnal.

The dump you supplied is not matching with the screenshot, but a similarity may be drawn, and that is important to the inferences here.
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc40006da8, ffffffffc000000e, 36ef0860, fffff88000db5630}

Probably caused by : partmgr.sys ( partmgr!PmPnp+b4 )

Followup: MachineOwner
The screenshot says it is stop F4, and it is an SSD as you are saying (120 GB). When a SSD stops with a F4 error, what you have to try first is to update its firmware.

Some more things you are to do there ....
Scan your system for viruses. It is needed here.
Disc Check:
  1. Reseat the sata and power.
  2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
  3. 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.
BIOS update:
BIOS Version/Date    INSYDE 1.80, 9/9/2009
► Update Display Driver, Sound Driver, Network Adapter Driver.

Perform those, according to priority order. After each step, notice if the situation changed or not. Let us know the situation.
My System SpecsSystem Spec
15 Oct 2012   #3


Thanks for the prompt reply!

I wouldn't have suspected a virus simply because it was a clean install of Windows on a new Hard Drive, though, I suppose a BIOS rootkit? I dunno. Either way, I'll do as you suggested as it couldn't hurt.

As far as I could find, the BIOS 1.80 was the latest/newest I could find so I'm not sure if I have any options there.

I will double check the hard drive's firmware as well as run the suggested disk checks.

Am I to understand though, that this is unlikely to be a RAM issue? Since she was having BSOD's (unfortunately I don't have those dmp files) before the new Hard Drive I had assume that to be the likely culprit. Thanks again for your prompt help and responses.
My System SpecsSystem Spec

15 Oct 2012   #4

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Three or four memory records reveal such situations which matches with virus infection, specially rootkit. Dumps never indicate a virus, clearly. It is just a situational evidence, nothing more.

The BIOS date is way back. If there is no versions after that date, that's sad for you.

None of the provided information indicate a memory issue strongly. Still, if you want, you may opt for RAM - Test with Memtest86+.
My System SpecsSystem Spec
17 Oct 2012   #5

Follow Up:

Bios Update: N/A
Display, Sound, and Network Adapter Driver: Up to date with what's available (AFAIK)
Anti rootkit utility TDSSKiller: Clean
Windows Defender Offline: Clean
AVG Rescue CD: Clean
Seatools for DOS: Passed
Reseat Drive/Power: √

Memtest86+ 4.20: In Progress
Firmware Update for Hard Drive: Pending (New firmware became available a couple weeks ago)
Chkdsk: Pending

So i'm jumping the gun a bit but assuming the Memtest86+, and Chkdsk come out clean I'm not really sure what else to try. I'll update the firmware on the hard drive but it seems unlikely that that is the issue considering the firmware currently installed is only a couple weeks older than the new one. Are there any other suggestions or means by which I can troubleshoot? Thanks!
My System SpecsSystem Spec
18 Oct 2012   #6


Chkdsk completed and there were no errors.

A side note -- I was checking event viewer and found I was getting an error on the machine:

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected

Little research and found a Microsoft Fix It - Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2

No more error, but not sure if it'd be related to the BSODs or not.
My System SpecsSystem Spec
18 Oct 2012   #7
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit

Both of them are the same in that both reported an error with the disk hardware, in that the drive it intended to use (the SSD) went spontaneously missing. If all driver/BIOS/firmware updates didn't resolve this problem, then the drive itself is just bad. It happens. Get it replaced, and you should be good from then on.


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

The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arg1: fffff6fc40006da8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000036ef0860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88000db5630, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e





TRAP_FRAME:  fffff88002fd26e0 -- (.trap 0xfffff88002fd26e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800491bb90
rdx=fffffa8007c9b680 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000db5630 rsp=fffff88002fd2878 rbp=fffffa8007c9b7e0
 r8=fffff88000db17c0  r9=0000000000000001 r10=0000000000000000
r11=fffff88002fd2850 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff880`00db5630 4c8bdc          mov     r11,rsp
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b05552 to fffff80002a97fc0

fffff880`02fd2408 fffff800`02b05552 : 00000000`0000007a fffff6fc`40006da8 ffffffff`c000000e 00000000`36ef0860 : nt!KeBugCheckEx
fffff880`02fd2410 fffff800`02abecbf : fffffa80`03d72a00 fffff880`02fd2540 fffff800`02cca540 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36bea
fffff880`02fd24f0 fffff800`02aa5589 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`00961000 : nt!MiIssueHardFault+0x28b
fffff880`02fd2580 fffff800`02a960ee : 00000000`00000008 fffff880`00db5630 00000000`00000000 fffffa80`07c9b680 : nt!MmAccessFault+0x1399
fffff880`02fd26e0 fffff880`00db5630 : fffff880`00db72c4 00000000`00000000 fffffa80`07c9b680 fffffa80`07c9b7e0 : nt!KiPageFault+0x16e
fffff880`02fd2878 fffff880`00db72c4 : 00000000`00000000 fffffa80`07c9b680 fffffa80`07c9b7e0 fffff880`02fd2988 : partmgr!PmSurpriseRemoval
fffff880`02fd2880 fffff800`02cfe8d9 : fffffa80`0491bb90 00000000`c00000bb fffff880`02fd2988 fffffa80`07c9b680 : partmgr!PmPnp+0xb4
fffff880`02fd28d0 fffff800`02e7e1e1 : fffffa80`046fa1f0 00000000`00000000 fffffa80`0474f900 fffff800`02bc3350 : nt!IopSynchronousCall+0xc5
fffff880`02fd2940 fffff800`02e78bd8 : fffff880`02fd2b00 fffffa80`046fa1f0 00000000`0000030a 00000000`00000308 : nt!IopRemoveDevice+0x101
fffff880`02fd2a00 fffff800`02e7dd27 : fffffa80`0474f900 00000000`00000000 00000000`00000003 00000000`00000098 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
fffff880`02fd2a40 fffff800`02e7de40 : 00000000`00000000 fffff8a0`03389a00 fffff8a0`0a3ce440 fffff880`02fd2b98 : nt!PnpDeleteLockedDeviceNode+0x37
fffff880`02fd2a70 fffff800`02f0e79f : 00000000`00000002 00000000`00000000 fffffa80`0474f900 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`02fd2ae0 fffff800`02f0f35c : fffff880`02fd2cb8 fffffa80`04126300 fffffa80`03cf0100 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
fffff880`02fd2c20 fffff800`02df85ce : 00000000`00000000 fffffa80`04126360 fffff8a0`03389aa0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`02fd2c50 fffff800`02aa1641 : fffff800`02cfd768 fffff8a0`03389aa0 fffff800`02c352d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x5ab9b
fffff880`02fd2cb0 fffff800`02d2ee5a : aeefbeff`ff7feff9 fffffa80`03cf0170 00000000`00000080 fffffa80`03ccf9e0 : nt!ExpWorkerThread+0x111
fffff880`02fd2d40 fffff800`02a88d26 : fffff880`009e9180 fffffa80`03cf0170 fffff880`009f3f40 ffbfb6c7`dbffef3f : nt!PspSystemThreadStartup+0x5a
fffff880`02fd2d80 00000000`00000000 : fffff880`02fd3000 fffff880`02fcd000 fffff880`02fd25b0 00000000`00000000 : nt!KiStartSystemThread+0x16


fffff880`00db72c4 eb64            jmp     partmgr!PmPnp+0x11a (fffff880`00db732a)


SYMBOL_NAME:  partmgr!PmPnp+b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: partmgr

IMAGE_NAME:  partmgr.sys


FAILURE_BUCKET_ID:  X64_0x7a_c000000e_partmgr!PmPnp+b4

BUCKET_ID:  X64_0x7a_c000000e_partmgr!PmPnp+b4

Followup: MachineOwner
As the stack says, there was a surprise removal (spontaneous and unexpected). Because this was reported by partmgr, it means it involves a drive and not some other type of device. Since we're suffering a c000000e error from this surprise removal during a kernel inpage operation (as in it occurred when attempting to grab Windows data from disk), it's evident the drive that suffered the surprise removal is none other than the system drive, aka the SSD. If cable changes and rehooking did not work, as well as driver/firmware/BIOS updates, then the SSD is just dead. Simple as that.
My System SpecsSystem Spec
18 Oct 2012   #8


Thanks for your response, Vir. As was to be expected, Memtest+ ran overnight and did six passes with no errors. I also updated the firmware for the hard drive without a hitch. I couldn't recreate a BSOD but it's too soon to tell whether or not the firmware update was enough to fix the problem. Aside from the already used Seagate and chkdsk methods, are there any alternatives to testing the hard drive?

I do have a spare M4 SSD so if another BSOD occurs I'm assuming Clonezilla will work fine for me to Clone the defective SSD over to the new one. Thanks again to all who have helped!
My System SpecsSystem Spec
18 Oct 2012   #9
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit

I'm not sure of any, unless one is provided by Crucial (which I don't believe they do have a diagnostic test). Seagate also isn't the most reliable test for SSD drives, so consider that for future use. The only other test I know is what you're about to do, which is a hardware swap. Of course, verify if the new firmware fixes things, and if not, swap drives.
My System SpecsSystem Spec
29 Oct 2012   #10


Well, it's tough to say whether it was re-seating the hard drive a third time, the firmware update for the HD or the most unlikely - the microsoft patch/fix-it. In any case, no more BSODs have occurred and I consider this fixed. Thanks for all the help and advice sent my way. Thanks!
My System SpecsSystem Spec

 BSOD When browsing with Chrome and using R

Thread Tools

Similar help and support threads
Thread Forum
BSOD during Chrome browsing
Hi. I keep getting this BSOD while running chrome(that's the connection i can make to it). I never get it during intense gaming. BCCode: 3b BCP1: 00000000C000001D BCP2: FFFFF80001A7E956 BCP3: FFFFF8801C438B30 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product:...
BSOD Help and Support
BSOD when browsing with Chrome
Excuse me, I put the minidump What should I do?
BSOD Help and Support
BSOD 10 or so min. into web browsing on Chrome.
I have never had issues with my computer until today. I bought some RAM as an upgrade, installed it, booted fine, then after opening up a few windows in Chrome, it crashed. It happened 3 times, same scenario. I couldn't read much of the BSOD, most of it was out of my monitor's FOV.
BSOD Help and Support
BSOD just browsing on chrome
Hey guys, I got a BSOD just browsing on Chrome, first time it's happened. I uploaded my .dmp file. Thanks guys.
BSOD Help and Support
BSOD while browsing with Chrome - why?
Hi, I'd really appreciate it if someone could look over these files and see if you can find the reason why my PC got a BSOD. I haven't got a BSOD in about a year so this is really unusual, which is why I'd like to find out what caused it.
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 14:05.
Twitter Facebook Google+