Tech Support banner

Status
Not open for further replies.
1 - 15 of 15 Posts

·
Registered
Joined
·
9 Posts
Discussion Starter · #1 ·
Hi there,

I've been experiencing a lot of BSOD since purchasing my new laptop.
I thought i fixed the problem with a fresh instal, but it's happening again.

Whenever i run verifier.exe, it causes a blue screen. I removed both sticks of ram separately, and still had the problem. I'm currently running in safe mode /networking, as that's the only way it will start without immediately going into blue screen (i believe verifier is still making this happen after a restart)

Here's the error report -

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFF8800951D495
BCP2: 0000000000000002
BCP3: 0000000000000008
BCP4: FFFFF8800951D495
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


the mini dump files are attached, as well as the Windows7_Vista_jcgriff2 instructions files, however i when i ran perfmon /report, all i get is this -

An error occured while attempting to generate the report.
The system cannot find the path specified.


The rest of my system details are below -

· OS - Vista/ Windows 7 ? Windows 7
· x86 (32-bit) or x64 ? 64
· What was original installed OS on system? Windows 8
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full retail (Home Premium)
· Age of system (hardware) 1 month since purchase
· Age of OS installation - have you re-installed the OS? 2 weeks - yes, clean instal of Windows 7 64

· CPU Intel Core i7-2670QM [email protected] 2.20GHz 2.19GHz
RAM: 16GB

· Video Card NVIDIA GeForce GT 540M
· MotherBoard (no idea how to get this information)
· Power Supply - brand & wattage (same as above)

· System Manufacturer - Sony
· Exact model number (if laptop, check label on bottom) VPCF236FM

If there is anything i'm missing, or other information that could help, please let me know.

Thank you!
 

Attachments

·
Registered
Joined
·
9 Posts
Discussion Starter · #2 ·
here's the perfmon /report i couldn't get working earlier -

I have disabled verifier, and running in regular windows mode but it seems like my entire pc is running slower now, as well.
 

Attachments

·
TSF - Enthusiast
Joined
·
15,298 Posts
Hello,

Try turning off verifier while in Safe Mode.
Some of your dumps indicate a problem with Download Accelerator Plus please remove this program for further testing.
Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`0304e000 PsLoadedModuleList = 0xfffff800`03292670
Debug session time: Thu Apr  4 23:04:44.654 2013 (UTC - 4:00)
System Uptime: 0 days 0:01:59.560
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800951d495, 2, 8, fffff8800951d495}

*** WARNING: Unable to verify timestamp for sbw.sys
*** ERROR: Module load completed but symbols could not be loaded for sbw.sys
Probably caused by : sbw.sys ( sbw+8495 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8800951d495, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8800951d495, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fc100
GetUlongFromAddress: unable to read from fffff800032fc1c0
 fffff8800951d495 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
sbw+8495
fffff880`0951d495 498b542410      mov     rdx,qword ptr [r12+10h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  sbu.exe

TRAP_FRAME:  fffff8800b59c3e0 -- (.trap 0xfffff8800b59c3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8011d77298
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800951d495 rsp=fffff8800b59c570 rbp=fffffa8011d772b8
 r8=fffffa8012775060  r9=0000000000000000 r10=fffff8000304e000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
sbw+0x8495:
fffff880`0951d495 498b542410      mov     rdx,qword ptr [r12+10h] ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c31e9 to fffff800030c3c40

FAILED_INSTRUCTION_ADDRESS: 
sbw+8495
fffff880`0951d495 498b542410      mov     rdx,qword ptr [r12+10h]

STACK_TEXT:  
fffff880`0b59c298 fffff800`030c31e9 : 00000000`0000000a fffff880`0951d495 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0b59c2a0 fffff800`030c1e60 : 00000000`00000000 00000000`00000002 fffffa80`12775060 fffffa80`11d77130 : nt!KiBugCheckDispatch+0x69
fffff880`0b59c3e0 fffff880`0951d495 : fffffa80`11d77130 fffffa80`11d77130 fffffa80`11d772b8 fffff980`18c06fe0 : nt!KiPageFault+0x260
fffff880`0b59c570 fffffa80`11d77130 : fffffa80`11d77130 fffffa80`11d772b8 fffff980`18c06fe0 00000000`00000020 : sbw+0x8495
fffff880`0b59c578 fffffa80`11d77130 : fffffa80`11d772b8 fffff980`18c06fe0 00000000`00000020 00000000`00010293 : 0xfffffa80`11d77130
fffff880`0b59c580 fffffa80`11d772b8 : fffff980`18c06fe0 00000000`00000020 00000000`00010293 fffff980`18ca8ee0 : 0xfffffa80`11d77130
fffff880`0b59c588 fffff980`18c06fe0 : 00000000`00000020 00000000`00010293 fffff980`18ca8ee0 00000000`00000000 : 0xfffffa80`11d772b8
fffff880`0b59c590 00000000`00000020 : 00000000`00010293 fffff980`18ca8ee0 00000000`00000000 fffffa80`11cf6750 : 0xfffff980`18c06fe0
fffff880`0b59c598 00000000`00010293 : fffff980`18ca8ee0 00000000`00000000 fffffa80`11cf6750 fffff800`0356ec16 : 0x20
fffff880`0b59c5a0 fffff980`18ca8ee0 : 00000000`00000000 fffffa80`11cf6750 fffff800`0356ec16 fffff980`19440f60 : 0x10293
fffff880`0b59c5a8 00000000`00000000 : fffffa80`11cf6750 fffff800`0356ec16 fffff980`19440f60 fffff980`18ca8ee0 : 0xfffff980`18ca8ee0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
sbw+8495
fffff880`0951d495 498b542410      mov     rdx,qword ptr [r12+10h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  sbw+8495

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: sbw

IMAGE_NAME:  sbw.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  512e0800

FAILURE_BUCKET_ID:  X64_0xD1_VRF_CODE_AV_BAD_IP_sbw+8495

BUCKET_ID:  X64_0xD1_VRF_CODE_AV_BAD_IP_sbw+8495

Followup: MachineOwner
 

·
Registered
Joined
·
9 Posts
Discussion Starter · #4 ·
Hi,

Thanks for your reply.
I just uninstalled it and not only a faster startup, but verifier didn't crash to a blue screen this time.

Does verifier leave a file somewhere? Nothing seemed to happen after i restarted.

So anyway, hopefully this has fixed the problem. But i do remember getting the BSOD a few times before i installed DAP. Was there anything else in the dump files that looked suspicious?


Thanks again for your help! You may have just saved me days of work.
 

·
Registered
Joined
·
9 Posts
Discussion Starter · #6 ·
I had checked the memory with memtest about a week ago and everything was fine. Also ran another memory test through startup that also didn't report any errors.

Last night i stress tested with prime95 for 10.5 hours. When i ran this previously, it last about two before the blue screen. This time it was still running when i woke up.

But, just today i've had two random freezes. One turned into a black screen after playing a movie for about an hour, the other just stalled everything while i was idle.

Not sure where to go from here. I really hope this isn't a graphics card or motherboard problem, but it sure doesn't seem like anything else at the moment.
 

·
Registered
Joined
·
9 Posts
Discussion Starter · #7 ·
Quick update, another blue screen before (new file attached) and when running verifier, my harddrive seems to make a hissing noise. I ran the windows disk check, which resulted in no errors but are there any other programs i should try?

I really appreciate all the help.
 

Attachments

·
TSF - Enthusiast
Joined
·
15,298 Posts
Disable Verifier:

Click Start> All Programs > Accessories > Right click Command Prompt> choose Run as administrator -> Type verifier /reset and hit Enter

Once this is done restart the PC.

How many passes did you let the memory test run?
 

·
Registered
Joined
·
9 Posts
Discussion Starter · #10 ·
Disable Verifier:

Click Start> All Programs > Accessories > Right click Command Prompt> choose Run as administrator -> Type verifier /reset and hit Enter

Once this is done restart the PC.

How many passes did you let the memory test run?
I'm not sure how many passes, but it ran for about 3+ hours.


Additionally, update your Sony Firmware Extension Parser (SFEP) driver. Yours is from 2007 and known to cause problems.
Sony eSupport - VPCF236FM - Drivers & Software | Sony® Firmware Extension Parser Device Driver
-----
Wow. i got all my drivers from here: Sony eSupport - VPCF236FM - Support
Figured they would be up to date. But, i just updated it now, thank you.

I also ran a program called WhoCrashed, i'm not sure how definitive it is or if it will help but here are the results -

crash dump file: C:\Windows\Minidump\040813-43243-01.dmp
This was probably caused by the following module: iastor.sys (0xFFFFF880010DD6EF)
Bugcheck code: 0xD1 (0x100004B, 0x2, 0x0, 0xFFFFF880010DD6EF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastor.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


crash dump file: C:\Windows\Minidump\040713-40794-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x8884, 0xFFFFFA8000430F80, 0xFFFFFA8000439E00, 0x203)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 

·
Registered
Joined
·
3,036 Posts
WhoCrashed does not do a very in depth analysis of the crashes. We typically analyze the full reports and use all information available including the stack trace of 3rd party drivers that were in use at the time of crashes. Were the latest crashes before or after installing the update to the SFEP software?

memtest86+ should be run for at least 7-10 passes, preferably more. It can take up to 22 passes to find errors. We generally suggest running it overnight or overnight and into a work day to get as many passes as possible. You should also run it both after the system has been shut down (not in sleep mode) for a few hours and also after the system has been in use for a few hours since faulty RAM can behave differently when it is cold or when it is warm.



-----
 

·
Registered
Joined
·
9 Posts
Discussion Starter · #12 ·
I ran memtest for 13 hours, and stopped because errors started to show up after the third test. But it went through 7, and i'll post the results below -

cpu clk: 2195mhz
l1 cache: 64k 60841mb/s
l2 cache: 256k 32718mb/s
l3 cache: 6144k 20279mb/s
memory: 16g 20280mb/s

Time: 13:28:12 Iterations: 3 adrsmode: 64bit pass: 7 Errors: 420

Error confidence value: 186
Lowest error address: 00100430100 - 4100.1mb
Highest error address: 00108430fe0 - 4228.1mb
Bits in error mask: 00000014
Bits in error - total: 2 Min: 1 Max: 1 Avg: 1
Max contiguous errors: 1

Test 0 Errors 0
Test 1 Errors 0
Test 2 Errors 0
Test 3 Errors 4
Test 4 Errors 1
Test 5 Errors 0
Test 6 Errors 4
Test 7 Errors 33

--------------------------------------

So i take it this means the ram is a problem?
 

·
Registered
Joined
·
3,036 Posts
It most likely does. It could also be a motherboard fault for a RAM slot. You should either send the laptop in under warranty or return the laptop to the store you purchased it from. If you send it under warranty, try hard to get a replacement instead of a repair or you may end up having to send it in multiple times before problems are fixed (speaking from experience).



-----
 

·
Registered
Joined
·
9 Posts
Discussion Starter · #14 ·
Well, that's not going to be fun..

But thanks very much to both of you for all your help! At least i know what the problem is, and learnt how to identify problems a lot better!
 
1 - 15 of 15 Posts
Status
Not open for further replies.
Top