Jump to content

uTorrent 1.8.3 BSOD on windows 7 x64


ashi

Recommended Posts

i have no idea how this happened, but it definately caused by utorrent. BSOD took place about every 10-20 minutes since utorrent started downloading, and it said that the file related to BSOD is ntfs.sys.

i have tested both stable release and beta release, no luck with any of them.

utorrent team fix this please.

here is some records from event log for last 24 hrs of unexpected shutdowns.

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2009/5/4 9:52:25

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: ashi-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-04T01:52:25.459210400Z" />

<EventRecordID>7662</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>ashi-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2009/5/4 9:35:59

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: ashi-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-04T01:35:59.570008900Z" />

<EventRecordID>7559</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>ashi-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2009/5/4 9:26:43

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: ashi-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-04T01:26:43.977207800Z" />

<EventRecordID>7463</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>ashi-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2009/5/4 7:25:20

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: ashi-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-03T23:25:20.348412000Z" />

<EventRecordID>7332</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>ashi-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2009/5/4 2:29:50

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: ashi-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-03T18:29:50.880411200Z" />

<EventRecordID>7177</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>ashi-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2009/5/4 0:49:28

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: ashi-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-03T16:49:28.053609700Z" />

<EventRecordID>7047</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>ashi-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2009/5/4 0:02:11

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: ashi-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-03T16:02:11.738412700Z" />

<EventRecordID>6933</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>ashi-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 2009/5/3 22:51:27

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: ashi-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-03T14:51:27.582412400Z" />

<EventRecordID>6813</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>ashi-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Link to comment
Share on other sites

Are you using v 6.110 of the driver (for Vista x64)? :/

For the record if you've got ntfs.sys problems, you either are dealing with a bad hard drive or some low level kernel things. To see if it's anything related to uTorrent's dealing with the Disk, try reconfiguring the options under Ctrl-P > Advanced > Disk Cache.

Link to comment
Share on other sites

Well, ntfs.sys is never really supposed to crash, so there's some nasty driver fault or failing hardware. It has absolutely nothing to do with µTorrent.

First of all, you need to run the RC for Windows 7 (and even that isn't guaranteed stable). Test your RAM for 12-24 hours with memtest86. Then update all drivers. If using an external hard drive, don't use it while testing.

Link to comment
Share on other sites

  • 2 weeks later...

This is caused by uTorrent. I just experienced the same crash after rebooting from Linux into Windows 7 Build 7100 x64 and after uTorrent checked the data. I've also experienced a few other BSOD's in the past with various Windows 7 builds and now that I think of it, they were also caused by uTorrent. And yes, my uTorrent and drivers are up-to-date, and my hardware is rock solid. No crashes in OS X or Ubuntu.

<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="2009-05-14T16:14:12.520012300Z" />

<EventRecordID>8610</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>DrewsDesktop</Computer>

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

</System>

- <EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

Link to comment
Share on other sites

I'll be honest, I'm not surprised neither Ubuntu nor OSX crashes as neither uses an ntfs filesystem (unless you're using the NTFS-3G userspace utility, in which case you can try running uTorrent in them, but i suspect 3G will crash, and there's a possibility it will take some data with it as it's not as robust as the Microsoft NTFS drivers).

Have you tried checking the filesystem integrity? You can just use the build-in check disk utility. Make sure you select "Scan for and attempt recovery of bad sectors" (/r switch if you run chkdsk from the CLI).

Also, you skipped the "description" of your error. Event 41 could be anything from "windows did not shut down cleanly" to "the filesystem is corrupt and unusable". I could look it up on technet if Windows 7 events were listed there, but they aren't up yet. If you could provide the complete error, we would be in better shape to help out. Here's a sample of a complete error report:

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 12/05/2009 5:47:20 PM

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (2)

User: SYSTEM

Computer: Riley-PC

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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="2009-05-12T07:47:20.708428400Z" />

<EventRecordID>43401</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>Riley-PC</Computer>

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

</System>

<EventData>

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

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

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

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

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

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

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

</EventData>

</Event>

As you can see, this error is also event 41. I've also seen event 41 relate to using dual-CPU's with different revisions. Without the full error, it is unfortunately of little to no help in resolving the issue. If this is just another copy of the ones in your earlier thread, they're just indications of the reboot state, and don't provide any useful troubleshooting information. Any BSOD will generate this error, as will any power failure.

Link to comment
Share on other sites

Ashi (and others)

There's no need to guess what was wrong :) Instead, there's an excellent way to identify a root cause - crash dump analysis.

If you do not have experience with that, reply to me via email and I'll follow up with you to help with that.

Regards

Dmitry.

Link to comment
Share on other sites

  • 4 weeks later...

Utorrent Devs:

Win7 is getting ready for release, it would be a good idea to address this issue as soon as possible, and will have to be looked at eventually anywayz. Microsoft doesen't directly support this software, and will not take on the workload to get this software to run on it's OS before launch (haven't we found this out already?). Assuming MS won't support, is there any way that we can work around this exception, other than keeping our downloads at 1 or 2 simotanious?

following is a description of my problem, if you'd like memory dumps, you might want to post a walkthrough to get the specific information you'd like. It's pretty consistantly repro-able across every machine i've tried this on.

I got this same BSOD when I'm running utorrent. As I understand, this has to do with a certain number of simotanious torrents downloading, and has a tendency to occur faster with large downloads. When all tasks are paused or stopped when utorrent starts, this doesent repro at all. (Has to be when it starts). Current, (and sucky) workaround is to download one or two at a time.

Here's the stack, I took out the generic headers saying to restart the pc and stuff:

:::::::::::::::::::

IRQL_NOT_LESS_OR_EQUAL

if this is the first time ::::blah blah:::

...select Safe Mode.

Technical Information:

*** STOP: 0x0000000A (0x0000000000000008, 0x0000000000000002, 0x0000000000000000,0xfffff80002E167F7)

::More unrelated blah's::

Windows team reports that this is on utorrent corp/devs to fix... although I think win7 should be a bit more robust to be able to handle unsupported programs.

I was under the impression this was fixed with the recent builds, but it does persist on the most recent (7228 is the most stable as of now)

Windows 7 ultimate 7228.winmain.090603-1900

anyone heard of when utorrent will address this issue?

Link to comment
Share on other sites

  • 3 weeks later...

c'mon people, can we please get this squared away? I'm trying to get an external debugger setup, so I can get you a solid call-stack, but we really do need some admin participation on this one. this is definitly a memory address issue, that is 100% repro on specific hardware setups (we see it more often on dual channel cosair sticks 2x2GB) and 64 bit setups. I have tested hundreds of non-M$ supported software and torrenting programs with Win7, and all seem to work flawless, EXCEPT utorrent. I really want to continue using this program, but if utorrent continues to not support incoming OS's, I will have to recommend against using it :(

Varified 100% repro on the following setup:

7264.0.090622-1900 amd64 Windows 7 Ultimate

dual core e8500 @ 3.16GHz

2x2GB Cosair RAM (sorry for spelling, im too lazy to Bing! it.)

Could you Please help us out??

Link to comment
Share on other sites

Is there a resolution to this issue? My newly installed Win7 RC test box rebooted last night by itself while I was asleep (unexpectedly, generating a minidump file - so assuming BSOD). The only program I had running was uTorrent, so I assume it was either a Windows 7 issue or a uTorrent one, or configuration of either. I am interested in finding out the resolution to this issue, because it may relate to my crash. I will post my minidump file if anyone is interested in looking at it.

As a FYI: Win7 RC was very recently installed on a newly formatted disk as a standalone install and not an upgrade or dual boot. The only software I have on it so far are: Win7 Ultimate RC (and everything that comes with it), MS Office 2007 full install, all microsoft patches for both Win7 and MS Office (except the language packs), uTorrent and AVG free.

Link to comment
Share on other sites

AVGFree was selected precisely because it was one of the 3 virus scanners I could find that was claimed to be compatible with Windows 7. It is possible that it's not fully compatible, and also possible that it is a Win7 bug. However, googling for Win7 crashes has revealed very little. The only thing of remote relevance to my situation was this thread - which points at utorrent.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...