After 1.5 hour got a XINPUT1_3.dll crash?

Post » Wed Mar 30, 2011 12:12 pm

After playing for 1.5 hours I started running away from some evil stuff and the game froze.

I gave the 3 fingered salute to get to taskmgr and the game's frozen image was frozen behidn itit. I figure it had a crash dialog window behind it so I alt-tabbed to FalloutNV and pressed space/enter a few times and nothing so then I ended explorer.exe and the game disappeared (maybe finishing it's multi GB dump)

The debug makes it look like XINPUT1_3.dll is to blame. It did crash when I hit a bunch of keys at the same time while trying to run uphill away from evil while opening my inventory. I never did get to see my inventory. I'm going to sum up the debug log in case a dev can see anything special in it.

The debug log showed:

FalloutNV has caused an access violation exception (0xC0000005) when trying to write to memory location 0x00000000 on thread 23..Type of anolysis Performed   Crash anolysis Machine Name   RECYLED Operating System   Unexpected  Number Of Processors   8 Process ID   3404 Process Image   W:\Windows\System32\XINPUT1_3.dll System Up-Time   1 day(s) 08:30:53 Process Up-Time   01:26:10 


Here is a sum up of the loaded modules during the crash:

STEAM MODULES:Steam Client EngineSteam steamclientSteam Client APISteam vstdlib_s.dll Steam GameOverlayRendererSteam tier0_sMEDIA MODULES:libvorbislibvorbisfile FLV Splitterbinkw32MP4Splittervsfilter (Vob)MADFilterDIRECTX MODULES:D3DX9_38 Version: 9.23.949.2378d3d8thk Version: 6.1.7600.16385dinput8 Version: 6.1.7600.16385d3d8thk Version: 6.1.7600.16385 


Click Show to see the running threads
Spoiler


Thread Summary
Number of Threads 40 Thread(s)
Total reserved memory 39.05 MBytes
Total committed memory 976.00 KBytes

Thread ID System ID EntryPoint Reserved Committed
0 5416 0xfffde000 960.00 KBytes 64.00 KBytes
1 3172 FalloutNV+6fcda0 988.00 KBytes 36.00 KBytes
2 4044 FalloutNV+6fcda0 988.00 KBytes 36.00 KBytes
3 6040 FalloutNV+6fcda0 988.00 KBytes 36.00 KBytes
4 5232 FalloutNV+6fcda0 988.00 KBytes 36.00 KBytes
5 5560 FalloutNV+6fcda0 988.00 KBytes 36.00 KBytes
6 5280 FalloutNV+6fcda0 988.00 KBytes 36.00 KBytes
7 5856 FalloutNV+6a1460 1,000.00 KBytes 24.00 KBytes
8 5688 Steam!Win32MiniDumpInit+4bc68 1,012.00 KBytes 12.00 KBytes
9 3836 ntdll!TppWaiterpThread 1,012.00 KBytes 12.00 KBytes
10 5488 dsound!CThread::ThreadStartRoutine 1,012.00 KBytes 12.00 KBytes
11 4832 MMDevAPI!CDeviceEnumerator::PnpNotificationThreadWrapper 1,012.00 KBytes 12.00 KBytes
12 5088 dsound!CThread::ThreadStartRoutine 1,012.00 KBytes 12.00 KBytes
13 5020 FalloutNV+6a1460 984.00 KBytes 40.00 KBytes
14 3652 FalloutNV+6a1460 1,000.00 KBytes 24.00 KBytes
15 4248 FalloutNV+6a1460 1,000.00 KBytes 24.00 KBytes
16 4608 ntdll!TppWorkerThread 1,012.00 KBytes 12.00 KBytes
17 5144 ntdll!TppWorkerThread 1,012.00 KBytes 12.00 KBytes
18 5772 FalloutNV+6a1460 1,000.00 KBytes 24.00 KBytes
19 5492 dinput8!CEm_LL_ThreadProc 1,012.00 KBytes 12.00 KBytes
20 3568 FalloutNV+83d330 1,004.00 KBytes 20.00 KBytes
21 5932 FalloutNV+83d330 1,008.00 KBytes 16.00 KBytes
22 3576 FalloutNV+6a1460 984.00 KBytes 40.00 KBytes
23 3924 FalloutNV+6a1460 952.00 KBytes 72.00 KBytes
24 4516 FalloutNV+6a1460 952.00 KBytes 72.00 KBytes
25 5776 dsound!CThreadBase::StaticThreadProc 952.00 KBytes 72.00 KBytes
26 3564 atiumdag!XdxInitXopServices+240a7e 1,012.00 KBytes 12.00 KBytes
27 5292 atiumdag!XdxInitXopServices+240a7e 1,012.00 KBytes 12.00 KBytes
28 5684 atiumdag!XdxInitXopServices+240a7e 1,012.00 KBytes 12.00 KBytes
29 4060 atiumdag!XdxInitXopServices+240a7e 1,012.00 KBytes 12.00 KBytes
30 5784 atiumdag!XdxInitXopServices+240a7e 1,012.00 KBytes 12.00 KBytes
31 5624 quartz!ObjectThread 1,008.00 KBytes 16.00 KBytes
32 6128 quartz!CCallbackThread::InitialThreadProc 1,012.00 KBytes 12.00 KBytes
33 5532 quartz!COutputQueue::InitialThreadProc 1,012.00 KBytes 12.00 KBytes
34 4580 quartz!CAMThread::InitialThreadProc 1,012.00 KBytes 12.00 KBytes
35 704 quartz!CCallbackThread::InitialThreadProc 1,012.00 KBytes 12.00 KBytes
36 4688 quartz!COutputQueue::InitialThreadProc 1,012.00 KBytes 12.00 KBytes
37 5068 quartz!CAMThread::InitialThreadProc 1,012.00 KBytes 12.00 KBytes
38 4652 ntdll!TppWorkerThread 1,012.00 KBytes 12.00 KBytes
39 5244 dsound!CThread::ThreadStartRoutine 1,012.00 KBytes 12.00 KBytes


User avatar
ijohnnny
 
Posts: 3412
Joined: Sun Oct 22, 2006 12:15 am

Post » Wed Mar 30, 2011 3:21 am

Subsequent crashes have the same info about the XINPUT1_3.dll. It'd be nice if it was input related cause then I'd know where to start. This time the crash happened when I was on top of the edge of a cliff and holding down the arrow keys (more than one at a time) while trying to get around an invisible divider without falling off.

With additional info this time because my debugger is diff than last time.
Thread 9 - System ID 2432Entry point   Steam!Win32MiniDumpInit+4bc68 Create time   26.1.11 01.48.06 Time spent in user mode   0 Days 0:0:0.0 Time spent in kernel mode   0 Days 0:0:0.0 In FALLOU~2.DMP the assembly instruction at KERNELBASE!RaiseException+58 in W:\Windows\SysWOW64\KERNELBASE.dll from Microsoft Corporation has caused an unknown exception (0x406d1388 SetThreadName?) on thread 9

User avatar
Sarah Knight
 
Posts: 3416
Joined: Mon Jun 19, 2006 5:02 am

Post » Wed Mar 30, 2011 1:23 am

Comforting to know someone else had a similar crash. I wonder if it they used steam too or had a Razer mouse.

1 to 1.5 hours between crashes is fine with me, some ppl have it worse.

Malice — March 30, 2009 @ 12:26 pm

Im adding on to my last comment

This is all the info i got on the problem

Problem Event Name: APPCRASH
Application Name: Fallout3.exe
Application Version: 1.0.0.12
Application Timestamp: 48f62dcc
Fault Module Name: XINPUT1_3.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a7a6
Exception Code: c0000135
Exception Offset: 00009cac
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 9d13
Additional Information 2: 1abee00edb3fc1158f9ad6f44f0f6be8
Additional Information 3: 9d13
Additional Information 4: 1abee00edb3fc1158f9ad6f44f0f6be8

User avatar
jaideep singh
 
Posts: 3357
Joined: Sun Jul 08, 2007 8:45 pm

Post » Wed Mar 30, 2011 7:50 am

The prob has gone away. I changed a few things at the same time so I'm not 100% certain what fixed it but I believe it was either freeing up space on my drives or disabling environmental sounds in the .ini. When I had the crashes the game would always be about 7GB memory used (including virtual mem) and crash after 1-1.5 hours play. Now I can play infinitely crashless and total used mem is under 3GB.

The things I did between the time I had crashes and the time it was fixed:

  • Increased three different audio cache related variables in the .ini
  • Disabled environmental sounds in the .ini
  • Freed up space on 2 of my hdds (2 disks had < 3.5GB free and both are virtual memory drives)
  • Updated video card drivers

User avatar
Chris Cross Cabaret Man
 
Posts: 3301
Joined: Tue Jun 19, 2007 11:33 pm

Post » Tue Mar 29, 2011 11:16 pm

The crashes came back when a newly created partition on one of my new drives ran out of free space (had only 6gb left). Freeing up 15gb total free space fixed it.

I don't know why the game crashes (especially with xinput1_3.dll) when a disk is low on space. I haven't seen other people attribute their FO:NV crashes to a lack of free disk space.

The only difference between my system and the average system is I have more physical disks - 6 with one partition each and 1 with three partitions. The cluster size for each partition is either 16k or 64k (with the exception of a hidden boot partition being 4k).

The partition that was low on space wasn't a swap file drive, the recycle bin and indexing were turned off and It didn't have anything on it except large video files so there shouldn't have been any activity on the drive (I didn't log it to see if there was any).

Next time a drive runs low on space and the game starts crashing I'll remove xinput1_3.dll from the system32 folder and see if anything changes. I may also log disk activity on that drive to see what magical things are happening behind the scenes.
User avatar
Angus Poole
 
Posts: 3594
Joined: Fri Aug 03, 2007 9:04 pm

Post » Wed Mar 30, 2011 10:36 am

I wanted to update this to say that there was no prob with xinput1_3.

I removed xinput1_3.dll from the system but it kept reporting the prob as xinput1_3.dll still. It was because I was using the 4gb memory fix. Without the 4gb memory fix the crashes all report FalloutNV.exe.
User avatar
Joanne
 
Posts: 3357
Joined: Fri Oct 27, 2006 1:25 pm


Return to Fallout: New Vegas