BSOD

Joined
Dec 12, 2012
Messages
1
Reaction score
0
Last night my system experienced a 0x3b BSOD. I have experienced weird, intermittent BSOD issues for awhile and thought I would finally ask for some help in figuring things out. I have attached my minidump folder. Thanks for your help.
 

Attachments

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,134
Reaction score
252
Welcome to the W7 Forums.

The results are inconclusive.
Debug session time: Wed Dec 12 19:01:56.751 2012 (UTC + 11:00)
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 5 days 4:09:46.979
Probably caused by : tdtcp.sys ( tdtcp!TdiAllocateIrp+17 )
BugCheck 3B, {c0000005, fffff800040a9d8d, fffff8801fda82e0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800040a9d8d, Address of the instruction which caused the bugcheck
Arg3: fffff8801fda82e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0x3B_tdtcp!TdiAllocateIrp+17
MaxSpeed: 3400
CurrentSpeed: 3502
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Nov 27 05:29:54.320 2012 (UTC + 11:00)
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 1 days 15:58:01.101
Probably caused by : tdtcp.sys ( tdtcp!TdiAllocateIrp+17 )
BugCheck 3B, {c0000005, fffff880071c35fb, fffff8800f5542f0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880071c35fb, Address of the instruction which caused the bugcheck
Arg3: fffff8800f5542f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0x3B_tdtcp!TdiAllocateIrp+17
MaxSpeed: 3400
CurrentSpeed: 3502
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 25 13:30:11.034 2012 (UTC + 11:00)
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 2 days 18:14:07.815
Probably caused by : tdtcp.sys ( tdtcp!TdCancelReceiveQueue+33 )
BugCheck D1, {0, 2, 0, fffff88007993fc3}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007993fc3, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0xD1_tdtcp!TdCancelReceiveQueue+33
MaxSpeed: 3400
CurrentSpeed: 3502
BiosVersion = 3304
BiosReleaseDate = 04/18/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Please enable Driver Verifier and then post any crash files.


(Borrowed from Zigzag3143 posts)

Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:

  1. Go to Start and type in "verifier" (without the quotes) and press Enter
  2. Select "Create custom settings (for code developers)" and click "Next"
  3. Select "Select individual settings from a full list" and click "Next"
  4. Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
  5. Select "Select driver names from a list" and click "Next"
  6. Then select all drivers NOT provided by Microsoft and click "Next"
  7. Select "Finish" on the next page.


  • Reboot the system and wait for it to crash to the Blue Screen.
  • Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
  • The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.


 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top