Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Random BSODs (1-2 a day) Event ID 41 on new W7 install, this time tcpi


  • Please log in to reply

#1
martini1179

martini1179

    New Member

  • Member
  • Pip
  • 3 posts
Thank you in advance for helping me.

I'm getting random BSODs in a 2-day old install of Windows 7 (which itself was an upgrade from a 1-day old install of Vista--upgrade W7 disc). I'm averaging 1-2 such BSODs a day so far on this gaming rig, but ironically none have happened while gaming.

The latest BSOD said something about tcpip.sys (I think--BSODs are impossible to read given the 5-second duration). It happened while I was watching a youtube video; another happened while I was scrolling through a webpage. A third happened when Windows attempted to install Microsoft Visual C++ redistributable before installing Crysis (I was out of the room when this one took place). As far as I can tell, all the BSODs are cited by Windows Event Viewer as originating from "Kernel-power" event ID 41, with this latest one (tcpip.sys) giving the following details:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />

<EventID>41</EventID>

<Version>2</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000002</Keywords>

<TimeCreated SystemTime="2011-11-19T02:34:05.095615100Z" />

<EventRecordID>51542</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>Marty-PC</Computer>

<Security UserID="S-1-5-18" />

</System>
- <EventData>

<Data Name="BugcheckCode">59</Data>

<Data Name="BugcheckParameter1">0xc0000005</Data>

<Data Name="BugcheckParameter2">0xfffff88001686d7c</Data>

<Data Name="BugcheckParameter3">0xfffff880091c4c30</Data>

<Data Name="BugcheckParameter4">0x0</Data>

<Data Name="SleepInProgress">false</Data>

<Data Name="PowerButtonTimestamp">0</Data>

</EventData>
</Event>
After rebooting, Windows gives the following details:

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: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88001686D7C
BCP3: FFFFF880091C4C30
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\111811-22261-01.dmp
C:\Users\[username]\AppData\Local\Temp\WER-49967-0.sysdata.xml

I tried uploading the *.DMP file, but I got a "You aren't permitted to upload this kind of file" error.


Potentially useful information:

Running Panda Cloud Antivirus 1.9.1 BETA (which now comes with a firewall) on top of the Windows firewall (only because Iíve been busy setting up the PC).

I should note that this identical hardware (minus a HDD swap) ran Ubuntu Linux flawlessly for 2 years, so I donít think that itís a hardware issue.

Attached Files


Edited by martini1179, 18 November 2011 - 09:57 PM.

  • 0

Advertisements


#2
martini1179

martini1179

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Here's the DMP file.

Attached Files


  • 0

#3
martini1179

martini1179

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Here are the other two DMP files that I have, from the other BSODs.

Attached Files


  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
(Click to consult the online MSDN article.)
Generally, use the General Troubleshooting of STOP Messages checklist above to troubleshoot this problem. A specific problem is known to exist with Win XP SP2 and Server 2003 in combination with certain antivirus programs, firewalls, and similar software; see the article linked below for details and current status of a fix from Microsoft.



Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads



Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program




Download and install Free Everest Home Edition
Open it.
1: In left pane expand Computer folder.
2: Click once on Summary
3: In upper menu, go Report
4: And then to Quick Report-Summary
5: Save it in text file, and paste it in your next post.
Click the + by computer, click on Sensor. Get a screenshot and post it so I can check your temps and voltages...


DO NOT INCLUDE ANYTHING UNDER THE LINE THAT SAYS "DEBUG- PCI"
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP