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

Win7 - BSOD - d1


  • Please log in to reply

#1
logoff

logoff

    New Member

  • Member
  • Pip
  • 1 posts
Hi there,

After getting one 3b, I'm now experiencing regular d1 BSODs (see below).
Searching for answers to that issue I came across this forum where a poster -namely Broni- was able to extract info from a dump that BlueScreenView doesn't display.

1st BSOD (3b)
==================================================
Dump File		 : 030310-19640-01.dmp
Crash Time		: 2010/03/03 19:35:32
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code	: 0x0000003b
Parameter 1	   : 00000000`c0000005
Parameter 2	   : fffff880`0145c4fa
Parameter 3	   : fffff880`0624cd30
Parameter 4	   : 00000000`00000000
Caused By Driver  : ndis.sys
Caused By Address : ndis.sys+174fa
File Description  : 
Product Name	  : 
Company		   : 
File Version	  : 
Processor		 : x64
==================================================

All others (d1)
==================================================
Dump File		 : 030310-18314-01.dmp
Crash Time		: 2010/03/03 22:30:54
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code	: 0x000000d1
Parameter 1	   : 00000000`00000000
Parameter 2	   : 00000000`00000002
Parameter 3	   : 00000000`00000000
Parameter 4	   : fffff880`03a86f40
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+86f40
File Description  : 
Product Name	  : 
Company		   : 
File Version	  : 
Processor		 : x64
==================================================


Attached are all the dumps Attached File  Win7_BSOD.zip   319.2KB   47 downloads
and a full text file Attached File  Win7_BSOD.txt   15.88KB   200 downloads

TIA for your assistance.

Update:
I ran SFC /SCANNOW and was told to check the CBS.LOG inside which I found the following:
2010-03-30 18:24:27, Info				  CSI	000002da [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-03-30 18:24:27, Info				  CSI	000002dc [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-03-30 18:24:27, Info				  CSI	000002dd [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2010-03-30 18:24:27, Info				  CSI	000002e0 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2010-03-30 18:24:27, Info				  CSI	000002e2 [SR] Repair complete
2010-03-30 18:24:27, Info				  CSI	000002e3 [SR] Committing transaction
2010-03-30 18:24:27, Info				  CSI	000002e7 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

Edited by logoff, 30 March 2010 - 11:23 PM.

  • 0

Advertisements







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