BSOD just after starting FS9, error 0x0000003b, tcpip.sys driver

sparrow17m · Aug 4, 2012

FS9 (Flight Simulation 2004) used to run OK, no problems.
After installing REX2004 patches and Overdrive, a few seconds after starting FS9 a BSOD occurs. So far no other programs have caused a BSOD.
I have tried fully uninstalling FS9 and reinstalling it and the BSOD returns after the reinstall. At present FS9 is not installed. Have now created the file folder you requested to support this thread, see attached.
Does anyone know how to fix this so that I can again run FS9 please?

JaidynM · Aug 10, 2012

Software

There seems to be a problem with your Windows installation. Please follow the Windows Genuine and Activation Issue Posting Instructions. Post the results in your next post; do not start a new thread.

Drivers

The following drivers need to be updated:

Code:

teamviewervpn.sys           Thu Dec 13 20:22:09 2007 (4760F9C1)

These drivers can be found by searching them in Google and then finding the associated software or driver. Finally, find the latest version of this driver or software and download and install it. Some of the drivers may also be found here (if the driver says 'Windows Update' simply make sure all Windows Updates are installed).

You should also update any other drivers you can think of including graphics, audio, chipset, SSD etc.

Update your NVIDIA video card drivers from the below link. Rather than doing a typical install, select custom and perform a clean install.
http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html

sparrow17m · Aug 10, 2012

Code:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-2497Q-MXYJW-YTBGC
Windows Product Key Hash: Gblzz+IbrOI6qVE/W1v9i/0ljtE=
Windows Product ID: 00359-OEM-8703622-23382
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {C33CF267-9866-4B79-A5C0-DA231EF5B075}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120503-2030
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
OGA Data-->
Office Status: 100 Genuine
Microsoft Office Home and Student 2007 - 100 Genuine
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Opera\Opera.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
File Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{C33CF267-9866-4B79-A5C0-DA231EF5B075}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-YTBGC</PKey><PID>00359-OEM-8703622-23382</PID><PIDType>3</PIDType><SID>S-1-5-21-2392155845-2901444307-2996211098</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7681</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.14</Version><SMBIOSVersion major="2" minor="7"/><Date>20110713000000.000000+000</Date></BIOS><HWID>CCCE3007018400FE</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>359841F68914F34</Val><Hash>y/JA1Gd0zHax7WpPQMfOD0jBEBc=</Hash><Pid>81602-922-8409223-68318</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7601.17514
Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
Activation ID: 586bc076-c93d-429a-afe5-a69fbc644e88
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00174-036-223382-02-2057-7601.0000-3262011
Installation ID: 017976051004333330975605311594363431236066976964074303
Processor Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88338[/URL]
Machine Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88339[/URL]
Use License URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88341[/URL]
Product Key Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88340[/URL]
Partial Product Key: YTBGC
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 10/08/2012 11:05:22
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 5:24:2012 12:10
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:

HWID Data-->
HWID Hash Current: OAAAAAEABAABAAEAAAADAAAAAwABAAEAln38ZTzoDP54dGI0St0IWwRW/udkoovIuB3YW2ANLnM=
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name OEMID Value OEMTableID Value
  APIC   ALASKA  A M I
  FACP   ALASKA  A M I
  HPET   ALASKA  A M I
  MCFG   ALASKA  A M I
  SSDT   AMICPU  PROC
  ASF!   INTEL    HCG

Thanks for the guidance, here is some further information:
As recommended, I've downloaded and installed the latest version of
TeamViewer (7.0.13989). I believe Windows is fully up-to-date.
Reference graphics drivers: I am using those provided by the card manufacturer
(MSI) on the CD that came with the card. I previously had later NVIDIA drivers
installed for the card but those resulted in frequent graphics card black screen
crashes. The cpu carried on running correctly and after a while the graphics
card recovered and resumed operation from where it had left off. Reverting
to the MSI drivers corrected the problem. (I assumed that was because it was
a card manufacturers overclock that the NVIDIA drivers could not run correctly).
Do you still recommend updating the video card drivers?
Thanks.

JaidynM · Aug 10, 2012

If you are overclocking any hardware, STOP. Reset any changed values back to default.

Check the MSI website if they have any new drivers for your card. If not, I would recommend using the NVIDIA drivers and then reverting back to the old ones if they cause crashes.

sparrow17m · Aug 19, 2012

I think I may have uncovered the area of the problem.
I've been installing FS9 on another just built Windows 7 Pro pc x64.
FS9 has been working fine until I added some software today.
Those added are:
.NET Framework 1.1 Redistributable (this generated a warning that it is incompatible with Windows 7, so this could be the problem).
EditVoicepack v3.1
.NET Framework 1.1 SP1
Traffic 2005 v1.00
FSUIPC v3.999w
WideFS v6.94
I have been creating restore points as I added those items so I will
try back-tracking tomorrow. The blue screen error message generated
refers to the same tcpip.sys as previously.
Does any of this help at all?

Cheers

FredeGail · Aug 21, 2012

Information

Follow the current given steps, this is a jump-in.

*Where did you get your Windows 7 disc? PC/Separate
*Does it only happen when playing FS?
*Have you done any hard drive diagnostics?
*You mentioned you have overclocked your motherboard, stop!

================================================================

BSOD Analyse

Different culprits pointed towards your NVIDIA Graphics Driver. Driver Sweeper will ensure that you'd have a clean install at the end of the procedure, and by that no leftover files that'd bork the system.

* Make your way to Nvidia Drivers - Download NVIDIA Drivers and download the latest driver for your card, save it to your desktop for instance.
* Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet)
* Download Driver Sweeper
* Get to safe mode (without network) and search for Driver Sweeper in your rb:
* Select all the Nvidia components and analyse them
* Clean them, head into Windows without internet and install the driver you downloaded previously

dd'ing tcpip

Code:

0: kd> dd [COLOR=Red]fffff88004772ae0[/COLOR] L10
[COLOR=DarkOrchid]fffff880`04772ae0  04772fd0 fffff880 00000000 00000000
fffff880`04772af0  00000000 fffff880 060000ff fffffa80
fffff880`04772b00  04772fa0 fffff880 04772b28 fffff880
fffff880`04772b10  0010001f 00001f80 002b0010 0053002b[/COLOR]

Bugcheck

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
[COLOR=DarkOrchid]Arg2: fffff880016d1471, Address of the instruction which caused the bugcheck[/COLOR]
Arg3: fffff88004772ae0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

What you should do

*Full scan with Malwarebytes
*http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

Best Regards,
Frederik.

BSOD just after starting FS9, error 0x0000003b, tcpip.sys driver

sparrow17m

New member

My Computer

JaidynM

BSOD Dump Analyst

My Computer

sparrow17m

New member

My Computer

JaidynM

BSOD Dump Analyst

My Computer

sparrow17m

New member

My Computer

FredeGail

It's full of stars

My Computer