Windows 7: Windows 7 BSOD issues

Ed Borrett · 07 Oct 2010

Hey guys,

I hope you can help. I have been getting quite a few blue screens while using Windows 7. Most of them appear random, but it happenes every time I try and sync my iPhone to iTunes. It's starting to drive me crazy..!

I'm running Windows 7 32bit
This is an upgrade from Windows Vista that came installed on the laptop.
I have re-installed Windows 7 several times. The latest was roughly 5 months ago.
I bought the laptop early in 2009.

The data you asked for in the BSOD posting instructions are attached.

Hope you can help!

Thank you very much,

Ed

zigzag3143 · 07 Oct 2010

Quote: Originally Posted by Ed Borrett

Hey guys,

I hope you can help. I have been getting quite a few blue screens while using Windows 7. Most of them appear random, but it happenes every time I try and sync my iPhone to iTunes. It's starting to drive me crazy..!

I'm running Windows 7 32bit
This is an upgrade from Windows Vista that came installed on the laptop.
I have re-installed Windows 7 several times. The latest was roughly 5 months ago.
I bought the laptop early in 2009.

The data you asked for in the BSOD posting instructions are attached.

Hope you can help!

Thank you very much,

Ed

Hi Ed and welcome

these were caused by rapportPG.sys, which I havent been able to find the owner for. You should uninstall it.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050510-27783-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82e0c000 PsLoadedModuleList = 0x82f54810
Debug session time: Tue May  4 18:59:27.574 2010 (GMT-4)
System Uptime: 0 days 6:42:53.400
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {90dd854e, 0, ffff, 0}

Unable to load image \??\C:\Program Files\Trusteer\Rapport\bin\RapportPG.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RapportPG.sys
*** ERROR: Module load completed but symbols could not be loaded for RapportPG.sys
Probably caused by : RapportPG.sys ( RapportPG+154e )

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them.  A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 90dd854e, address of system function (system call)
Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 0000ffff, Thread->KernelApcDisable
Arg4: 00000000, Previous KernelApcDisable

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


FAULTING_IP: 
RapportPG+154e
90dd854e 6a08            push    8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  iTunes.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 772564f4 to 82e4f7d3

STACK_TEXT:  
bbc9dd34 772564f4 badb0d00 002ab314 00000000 nt!KiServiceExit2+0x17a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002ab3e4 00000000 00000000 00000000 00000000 0x772564f4


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
RapportPG+154e
90dd854e 6a08            push    8

SYMBOL_NAME:  RapportPG+154e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RapportPG

IMAGE_NAME:  RapportPG.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ba8d23c

FAILURE_BUCKET_ID:  0x1_RapportPG+154e

BUCKET_ID:  0x1_RapportPG+154e

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

Old drivers requiring update

Code:

mdmxsdk.sys        0xafd46000    0xafd49180    0x00003180    0x449716a3    6/19/2006 17:26:59                        
tdcmdpst.sys        0x8260a000    0x8260df00    0x00003f00    0x4535965a    10/17/2006 22:50:02                        
PxHelp20.sys        0x8b1bb000    0x8b1c3de0    0x00008de0    0x4679a978    6/20/2007 18:26:00                        
xaudio.sys        0xafdeb000    0xafdf3000    0x00008000    0x4717e005    10/18/2007 18:36:53                        
UVCFTR_S.SYS        0x82540000    0x82549000    0x00009000    0x474bf3aa    11/27/2007 06:38:34                        
SynTP.sys        0x91d8e000    0x91dbc400    0x0002e400    0x474f6490    11/29/2007 21:17:04                        
seehcri.sys        0x82471000    0x82476f00    0x00005f00    0x478488c1    1/9/2008 04:41:37                        
HSX_CNXT.sys        0x98f25000    0x98fda000    0x000b5000    0x47e97ee5    3/25/2008 18:38:29                        
HSXHWAZL.sys        0x82503000    0x82540000    0x0003d000    0x47e97f17    3/25/2008 18:39:19                        
HSX_DPV.sys        0x98e23000    0x98f25000    0x00102000    0x47e97f92    3/25/2008 18:41:22                        
IntcHdmi.sys        0x98e00000    0x98e21000    0x00021000    0x485c06e0    6/20/2008 15:37:04                        
ElRawDsk.sys        0x91c5e000    0x91c61600    0x00003600    0x488b65e1    7/26/2008 13:58:57                        
CHDRT32.sys        0x82488000    0x824bb000    0x00033000    0x4907a4ee    10/28/2008 19:49:02                        
yk62x86.sys        0x92545000    0x92595000    0x00050000    0x49a2b642    2/23/2009 10:44:18                        
spldr.sys        0x8b7c6000    0x8b7ce000    0x00008000    0x4a084ebb    5/11/2009 12:13:47                        
o2media.sys        0x9320f000    0x93219400    0x0000a400    0x4a0a5cf4    5/13/2009 01:39:00                        
GEARAspiWDM.sys        0x82bf7000    0x82bfc280    0x00005280    0x4a1151b5    5/18/2009 08:16:53                        
amdxata.sys        0x8b0ea000    0x8b0f3000    0x00009000    0x4a12f30f    5/19/2009 13:57:35                        
iaStor.sys        0x8b010000    0x8b0ea000    0x000da000    0x4a287809    6/4/2009 21:42:33                        
dump_iaStor.sys        0x90200000    0x902da000    0x000da000    0x4a287809    6/4/2009 21:42:33                        
o2sd.sys        0x82600000    0x82609200    0x00009200    0x4a4441b0    6/25/2009 23:34:08

How To Find Drivers:

Quote:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Ed Borrett · 07 Oct 2010

Awesome. Thanks so much. I'll get that done now and let you know what happens.

Ed

Ed Borrett · 08 Oct 2010

Hi again guys.

I've been downloading most of the drivers listed above, but I've noticed a few that I really don't recognise, and some I def don't use anymore (eg seehcri.sys - this was for an old sony ericsson phone suite). Are you able to give me any advice on how to get rid of these?

Again, thank you!
Ed

Tews · 08 Oct 2010

Ed.. the easiest way is to rename the driver with a .bak extention, so long as you are positive that the driver is no longer needed/wanted..

Ed Borrett · 08 Oct 2010

Tews, thank you for your post! Please forgive my ignorance, what is the best way of going about renaming them? Is it simply to search for them and then rename them?

Tews · 08 Oct 2010

Navigate to c:/windows/system32/drivers ... locate the driver and rename it (right click

rename)

Windows 7: Windows 7 BSOD issues

Windows 7 BSOD issues problems?