BSOD on restarting W7 64 bit and surfing in IE

Is there any reason that you enabled driver verifier?

And, when a verifier enabled crash dump is blaming the memory, and memory is good as per the test, then the issue is a real serious one.

We cannot check/test the motherboard for errors, so we cannot blame it; but I cannot see any other issue there, so suspecting the board only.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fa2125, fffff880072510f0, 0}

Probably caused by : memory_corruption ( nt!MiUnmapViewOfSection+385 )

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

1: 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: fffff80002fa2125, Address of the instruction which caused the bugcheck
Arg3: fffff880072510f0, 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!MiUnmapViewOfSection+385
fffff800`02fa2125 488b08          mov     rcx,qword ptr [rax]

CONTEXT:  fffff880072510f0 -- (.cxr 0xfffff880072510f0)
rax=000000000000ffff rbx=fffffa8009b5c0c0 rcx=00000000010a8000
rdx=0000000000000000 rsi=fffffa800aae7b30 rdi=fffffa8007a52590
rip=fffff80002fa2125 rsp=fffff88007251ad0 rbp=000000000000f000
 r8=00000000010a8000  r9=000000000000f000 r10=fffff80002fa22f4
r11=0000000000319af4 r12=000007fef0900000 r13=0000000000000000
r14=000007fef090efff r15=000007fef0900000
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!MiUnmapViewOfSection+0x385:
fffff800`02fa2125 488b08          mov     rcx,qword ptr [rax] ds:002b:00000000`0000ffff=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fa2353 to fffff80002fa2125

STACK_TEXT:  
fffff880`07251ad0 fffff800`02fa2353 : fffff880`00000000 000007fe`f0900000 fffffa80`00000001 00000000`0000ffff : nt!MiUnmapViewOfSection+0x385
fffff880`07251b90 fffff800`02c86e13 : fffffa80`07a52590 fffff880`07251c60 fffffa80`0aae7b30 fffffa80`0aeaf270 : nt!NtUnmapViewOfSection+0x5f
fffff880`07251be0 00000000`7749155a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0299f398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7749155a


FOLLOWUP_IP: 
nt!MiUnmapViewOfSection+385
fffff800`02fa2125 488b08          mov     rcx,qword ptr [rax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiUnmapViewOfSection+385

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

STACK_COMMAND:  .cxr 0xfffff880072510f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_VRF_nt!MiUnmapViewOfSection+385

BUCKET_ID:  X64_0x3B_VRF_nt!MiUnmapViewOfSection+385

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

Driver verifier is very effective, but not appropriate in your issue.

Though I must to say that it narrowed down the issue really easily.

If you send the computer for servicing, ask them to make it sure that your motherboard is not causing any problem at all. If it is within warranty, ask for a warranty replacement.

mrki69tua said:

And today my laptop came from service and that they changed motherboard so I will install everything but i believe that problem is solved! Thanks Archie.

Good news, mate :)

Now observe it over some days. Let us know how it is running.

Well, try to install the latest version of the Intel USB3 driver once again. See what happens.

I am not being able to determine what may be the real reason behind the BSODs. The last one was indicating to USB3, and this one .....

Code:

fffff880`02686058  fffff880`0103c74d ataport!IdeProcessPortNotification+0x30d

ataport.sys is the system native IDE ATA/ATAPI Controller driver (works alongwith atapi.sys). It may malfunction if the port/SATA cable/board is faulty, or a virus infection called rootkit.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

If they havent replaced th motherboard, then that is not possible to determine. I just casn say that your BIOS version is as same as the first post ....

Code:

BiosVendor = Hewlett-Packard
BiosVersion = 68IRR Ver. F.42
BiosReleaseDate = 07/16/2013