PDA

View Full Version : Anyone else with game crash issues [disrupt error]



NightbreedUK
05-23-2014, 09:29 PM
Just wondering if anyone else who has their copy are having trouble getting it to work?

My game goes to the screen after the ubisoft logo and then locks up - apparently a 'disrupt_b64.dll' error.

Updated all drivers etc on my system and then reinstalled by downloading from uplay (in case the disc install didn't work properly) - same problem.

Even used a fresh copy of win 8 on another hard drive and installed to that - and the same error lol, not heard back from tech support yet so just wondering if anyone else has the same problem

KmarkoPL
05-23-2014, 09:52 PM
What you talking about ? the game is not official released yet , If I did not know better , I would say you try pirated version !
Other wise , I would think that the game is been locked until full release on 27.05

fishers1989
05-23-2014, 09:54 PM
Retail versions aren't date locked. But yes, the game isn't officially released yet so anyone playing it prior to that is running it with out-dated drivers (the Watch Dogs compatible ones aren't out yet) and possibly without a necessary patch.

Devil0351
05-23-2014, 09:55 PM
The b64.dll is a system function component for Windows. If you're getting a critical error, it's not the game that's jacked up, but your OS. Unless of course you pirated it and are using a crack, in which case you now have a system reg virus embedded in your rig.

https://www.google.com/#q=disrupt_b64.dll&safe=off

fishers1989
05-23-2014, 10:00 PM
Disrupt is the name of Watch Dogs' engine, so no it's not a Windows component.

Devil0351
05-23-2014, 10:06 PM
Disrupt is the name of Watch Dogs' engine, so no it's not a Windows component.

b64.dll file is a crucial part of Windows operating system and is used to open and execute files.

NightbreedUK
05-23-2014, 10:07 PM
Thanks for the answers so far - the drivers issue does make sense so could be an idea to just wait and see :)

But to clarify - it is the uplay edition (arrived in the post today) And also after activating the product with the code - I could also download the whole game through uplay too (which I did in case the disk installation didn't install properly)

fishers1989
05-23-2014, 10:16 PM
All retail versions are uplay regardless of which edition you got so they'll all let you install from the disc or download. People who bought digital have to wait for their key to be sent to them around release day. That's what I meant by date locked, I should probably have been clearer on that.


b64.dll file is a crucial part of Windows operating system and is used to open and execute files.

The file is Disrupt_B64.dll, meaning it is a Ubisoft created library for the engine, not a Windows file.

Devil0351
05-23-2014, 10:17 PM
Go into Windows Error Reporting and copy/paste the error message here exactly as it appears.

1) Click Start
2) Type Event Viewer into the Search Box
3) Click Windows Logs then Application
4) Find the associated error

NightbreedUK
05-23-2014, 10:24 PM
Go into Windows Error Reporting and copy/paste the error message here exactly as it appears.

1) Click Start
2) Type Event Viewer into the Search Box
3) Click Windows Logs then Application
4) Find the associated error

Thanks for your replies :) Here is the error message:

Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000001d7433c
Faulting process id: 0x1134
Faulting application start time: 0x01cf76b8afb48a43
Faulting application path: G:\Ubisoft\Ubisoft Game Launcher\Games\Watch_Dogs\bin\Watch_Dogs.exe
Faulting module path: G:\Ubisoft\Ubisoft Game Launcher\Games\Watch_Dogs\bin\Disrupt_b64.dll
Report Id: fb83f8f9-e2ab-11e3-9255-bcaec5309bf8

fishers1989
05-23-2014, 10:26 PM
Access violation? It's a long shot but you could try creating an exemption for Disrupt_b64.dll in your anti-virus.

Devil0351
05-23-2014, 10:34 PM
Okay, so their are a couple of issues you could be facing. The message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this.

Before you go ripping hardware and **** out of your rig, remove your video card drivers, shutdown your PC, and then reboot and install the drivers again. If that doesn't work, post back and we'll run through the other options including Memtest.

fishers1989
05-23-2014, 10:45 PM
Incompatible software like a 2 month old graphics driver?

NightbreedUK
05-23-2014, 11:07 PM
Thanks for all your replies :)

I uninstalled the video card drivers as suggested and then reinstalled after a reboot.
Because it was a fresh driver install rather than the usual upgrade - it asked me if I wanted to turn on crossfire - so I left it on disabled and the game ran :)

For a test afterwards - I enabled crossfire, and then the same crash as before. So just in case anyone else has this problem try disabling crossfire.

But of course I wouldn't have even thought of this without your suggestions - so a big thanks to you :)

fishers1989
05-23-2014, 11:20 PM
Keep an eye on AMDs driver page. They haven't released a driver in a month either, so theirs should be due any day now as well, complete with Crossfire compatibility. Nvidia already added SLI for Watch Dogs to their last 2 drivers but they haven't released a new one in 46 days. No idea what's going on with those two lately.

Devil0351
05-23-2014, 11:21 PM
Thanks for all your replies :)

I uninstalled the video card drivers as suggested and then reinstalled after a reboot.
Because it was a fresh driver install rather than the usual upgrade - it asked me if I wanted to turn on crossfire - so I left it on disabled and the game ran :)

For a test afterwards - I enabled crossfire, and then the same crash as before. So just in case anyone else has this problem try disabling crossfire.

But of course I wouldn't have even thought of this without your suggestions - so a big thanks to you :)

No worries. Glad you got it sorted.

D_cover
05-23-2014, 11:35 PM
What you talking about ? the game is not official released yet , If I did not know better , I would say you try pirated version !
Other wise , I would think that the game is been locked until full release on 27.05

Some of us got the game early.

TheJackasaurus
05-24-2014, 02:17 PM
I'm getting a similar problem, any help would be appreciated :)

Problem signature:
Problem Event Name: APPCRASH
Application Name: Watch_Dogs.exe
Application Version: 0.1.0.1
Application Timestamp: 537507a1
Fault Module Name: dxgi.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c631
Exception Code: c000001d
Exception Offset: 000000000002da7d
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 2b24
Additional Information 2: 2b24300755bec8549d8dac294ed9740e
Additional Information 3: e6d0
Additional Information 4: e6d026250cecf6a54f097ef959818b85

fishers1989
05-24-2014, 02:35 PM
dxgi? Does the game ship with that or is that from SweetFX? If it's SweetFX you should make sure you're running 1.5, it's not totally compatible with DX11 games but that's the best version.

TheJackasaurus
05-24-2014, 03:02 PM
dxgi? Does the game ship with that or is that from SweetFX? If it's SweetFX you should make sure you're running 1.5, it's not totally compatible with DX11 games but that's the best version.
Must be part of the game, I've never heard of or used SweetFX. Reckon it's worth trying?

Devil0351
05-24-2014, 04:05 PM
I'm getting a similar problem, any help would be appreciated :)

Problem signature:
Problem Event Name: APPCRASH
Application Name: Watch_Dogs.exe
Application Version: 0.1.0.1
Application Timestamp: 537507a1
Fault Module Name: dxgi.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c631
Exception Code: c000001d
Exception Offset: 000000000002da7d
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 2b24
Additional Information 2: 2b24300755bec8549d8dac294ed9740e
Additional Information 3: e6d0
Additional Information 4: e6d026250cecf6a54f097ef959818b85

Post your system specs. Is your rig overclocked?

Ubi-MoshiMoshi
05-24-2014, 08:19 PM
I have reported this to the team, but please also open a ticket with Technical Support https://support.ubi.com

TheJackasaurus
05-24-2014, 09:31 PM
Post your system specs. Is your rig overclocked?

I've got...

MSI AMD Radeon R9 270X 2GB}
AMD FX-8320 CPU @ 3.5GHz (not overclocked)
8GB Kingston HyperX RAM

Mr_Shade
05-25-2014, 04:43 PM
To help us, please provide as much information as you can in your post:

Country + Format: (eg. United States - PS4, disc)

Usernames & Gamertags: (PSN / XBL gamertag or Uplay ID)

Frequency: (How often is it mentioned. How often does it happen to you?)

Since when does it happen (This helps identify if a patch or DLC is the source of the bug)

Describe what is the issue encountered: (Activation the game? / Problem launching the game? / Issue with a specific part of the game Mutliplayer? / But can you still access solo? )

Define the Flow of the error: (What did you do before this error occurred? / Written description / Ex: “When I launch from the desktop it crashes”. “I received this error message : Error xx6546” / Screen grab of the error if possible will also help!)

Anything else you think is useful:
screenshots of any errors, always help too!

Apesh_tViking
05-25-2014, 07:18 PM
Same thing for me:
Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000001c687d1
Faulting process id: 0x500
Faulting application start time: 0x01cf783f3631871c
Faulting application path: F:\Watch_Dogs\bin\Watch_Dogs.exe
Faulting module path: F:\Watch_Dogs\bin\Disrupt_b64.dll
Report Id: 631020ba-e436-11e3-bef6-14dae9d5a27b
Faulting package full name:
Faulting package-relative application ID:

Happened approx after 20 minutes of game time (chasing a car in "big brother").
I've only gotten this error once, but then again, only played once.

Username: vinterulv
System specs:
Windows 8.1 Pro
Intel i7 2600K @ 3.4 GHz
Asus P8P67 Pro REV 3.1 mainboard (latest BIOS confirmed, version 3602)
16GB RAM
EVGA Geforce 690GTX, Geforce Experience 2.0 and Driver package 335.23 (which is the latest WHQL and yes its 2 months old)
Game is installed on an intel 530 SSD 240GB

All game files have been fully validated. No errors.

MaximusTD
05-26-2014, 03:38 PM
Uplay ID: MaximusTD


Same problem, I'm not to computer savvy either =/

AMD Radion HD 6900 Series

30271076
20
APPCRASH
Not available
0
Watch_Dogs.exe
0.1.0.1
537507a1
Disrupt_b64.dll
0.0.0.0
5375077c
c0000005
0000000001d7433c


C:\Users\The Beast\AppData\Local\Temp\WERC59A.tmp.WERInternalMe tadata.xml
C:\Users\The Beast\AppData\Local\Microsoft\Windows\WER\ReportAr chive\AppCrash_Watch_Dogs.exe_6b5affff4bdd16a249db 69b3e666fc88ce9bb6_1db7e673

0
62d19649-e4e0-11e3-ade5-bcaec54d8e24
0

w576
05-26-2014, 05:32 PM
Same here, but my game doesnt even start. I can reach the main menu fine, but when I click on new game, after a few seconds of loading the game always crashes with the "Watch Dogs" stopped working window. I have up to date drivers, reinstalled DirectX, DotnetFX, VC Redist, verified game files. No Dice. I have wrote to the support but I don't hold my breath about it, every time I had a problem with a Uplay game I always get the "update your drivers" message. 60 euros wasted. So great.






Watch_Dogs.exe







0.1.0.1







537507a1







Disrupt_b64.dll







0.0.0.0







5375077c







c0000005







0000000000ae669f







d1c







01cf78fe6202c65b







E:\Program Files (x86)\Ubisoft\Watch_Dogs CZEHUN\bin\Watch_Dogs.exe







E:\Program Files (x86)\Ubisoft\Watch_Dogs CZEHUN\bin\Disrupt_b64.dll







6b24926b-e4f2-11e3-9a12-902b3462b3aa




Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, időbélyeg: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, timestamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000000ae669f
Faulting process id: 0xd1c
Faulting application start time: 0x01cf78fe6202c65b
Faulting application path: E:\Program Files (x86)\Ubisoft\Watch_Dogs CZEHUN\bin\Watch_Dogs.exe
Faulting module path: E:\Program Files (x86)\Ubisoft\Watch_Dogs CZEHUN\bin\Disrupt_b64.dll
Report Id: 6b24926b-e4f2-11e3-9a12-902b3462b3aa

CainStar
05-26-2014, 10:11 PM
I have the same disrupt_b64.dll problem. Thou I couldn't fix it by reinstalling game or GPU drivers. Has anybody found out any other solutions?

wili_goralnik
05-27-2014, 09:12 AM
Hello,
Well I have this problem, the game crashes right after finishing loading the game after I press continue on the main menu.
This happens every time, I cant even enter the game.

I have the latest Nvidia driver that was released today, game files are verified on UPlay, and Antivirus program is disabled.
Thank you!

This is the crash log-

http://i.gyazo.com/e1c777883c50e7f000f331f632536b0e.png

Problem signature:
Problem Event Name: APPCRASH
Application Name: Watch_Dogs.exe
Application Version: 0.1.0.1
Application Timestamp: 537507a1
Fault Module Name: Disrupt_b64.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5375077c
Exception Code: c0000005
Exception Offset: 0000000000ae669f
OS Version: 6.3.9600.2.0.0.256.49
Locale ID: 1037
Additional Information 1: ae09
Additional Information 2: ae09c43b3df4c26f8b1e634323336393
Additional Information 3: cbc0
Additional Information 4: cbc05b904372f84d5b04c59ab87cf36e

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

p370
05-27-2014, 02:41 PM
Same problem here...
I get following error whenever I try to start a new game from game menu:

Problem signature:
Problem Event Name: APPCRASH
Application Name: Watch_Dogs.exe
Application Version: 0.1.0.1
Application Timestamp: 537507a1
Fault Module Name: Disrupt_b64.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5375077c
Exception Code: c0000005
Exception Offset: 0000000002346620
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1051
Additional Information 1: 97ff
Additional Information 2: 97ff3c62a2849bd8a171bd58c6cfe43e
Additional Information 3: 718f
Additional Information 4: 718f63883ebcda96601ee593cb351b3a


That's an access violation exception so some code in Disrupt_b64.dll is trying to read or write a memory segment it has no rights to (or is out of memory range). When I've debugged it in Visual Studio it told me that the exception actually happened in code from overlay64.dll (Unhandled exception at 0x00007FFECF0E9F7B (overlay64.dll) in watch_dogs.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.

I have an Intel Core i7 930 with 24 GB RAM and single nvidia geforce gtx 670 graphics card with latest drivers (2 days old) and running Windows Server 2012 R2 as OS, I know it's not officially supported but never had any problems with games so far. I also removed Hyper-V and disabled DEP, but that didn't help.

Mr_Shade
05-27-2014, 02:45 PM
Guys I have reported it - however we may need the information I requested.

Please do post that back!

tomislav0x
05-27-2014, 02:52 PM
Same problem here...
I get following error whenever I try to start a new game from game menu:

Problem signature:
Problem Event Name: APPCRASH
Application Name: Watch_Dogs.exe
Application Version: 0.1.0.1
Application Timestamp: 537507a1
Fault Module Name: Disrupt_b64.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5375077c
Exception Code: c0000005
Exception Offset: 0000000002346620
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1051
Additional Information 1: 97ff
Additional Information 2: 97ff3c62a2849bd8a171bd58c6cfe43e
Additional Information 3: 718f
Additional Information 4: 718f63883ebcda96601ee593cb351b3a


That's an access violation exception so some code in Disrupt_b64.dll is trying to read or write a memory segment it has no rights to (or is out of memory range). When I've debugged it in Visual Studio it told me that the exception actually happened in code from overlay64.dll (Unhandled exception at 0x00007FFECF0E9F7B (overlay64.dll) in watch_dogs.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.

I have an Intel Core i7 930 with 24 GB RAM and single nvidia geforce gtx 670 graphics card with latest drivers (2 days old) and running Windows Server 2012 R2 as OS, I know it's not officially supported but never had any problems with games so far. I also removed Hyper-V and disabled DEP, but that didn't help.

Interesting, that's the first of its kind, and yours is a GTX670 GPU (singleGPU on a PCB, unless you're running two in SLI). I believe your exception is OS related because overlay64.dll is an Uplay component unrelated to GPU problems which are the prominent source of disrupt_b64.dll exceptions (querying multigpu systems fails) [that's the primary engine (Disrupt) lib]

czuncz
05-27-2014, 03:13 PM
has somebody an idea for me? I got gpu driver issues with watchdogs, the game crashes constantly . I got a gtx780

here is the eventlog:

Name der fehlerhaften Anwendung: Watch_Dogs.exe, Version: 0.1.0.1, Zeitstempel: 0x537507a1
Name des fehlerhaften Moduls: d3d11.dll, Version: 6.2.9200.16570, Zeitstempel: 0x5153b56b
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000d6f09
ID des fehlerhaften Prozesses: 0x284c
Startzeit der fehlerhaften Anwendung: 0x01cf79912f4fde79
Pfad der fehlerhaften Anwendung: F:\Uplay\Watch_Dogs\bin\Watch_Dogs.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\d3d11.dll
Berichtskennung: 757e4f2c-e58b-11e3-8536-005056c00008

do I have to reinstall dx11 maybe?

dex8472
05-27-2014, 03:36 PM
I have this exact same problem.

However, if I go offline via Uplay and start the game, I don't get the crashing issues at all.

That's the problem though. I want to play online.

psdkp
05-27-2014, 03:48 PM
me too i don't know how to solve it

Mr_Shade
05-27-2014, 03:51 PM
Hi,

The issue has been reported - and is a known issue.

I will move this thread to the technical forum.

Please check the pinned 'known issues' thread for any updates.

lateraliss
05-27-2014, 05:59 PM
The game kept crashing right after the intro splash screen when I started the game. I had the disrupt_b64.dll error when I checked the event viewer. Disabling crossfire fixed the issue. What a mess.

RonnyBSC
05-27-2014, 06:16 PM
Hey

My System
Windows 7
AMD Phenom II X6 1100T Processor 3,30GHz
AMD HD 6990
12 GB Ram

When I start the game comes after the Ubisoft logo, this error message:
http://www.fotos-hochladen.net/uploads/unbenanntt8legdowf3.png

HELP :eek:

CainStar
05-27-2014, 08:42 PM
So I installed the latest beta drivers from AMD 14.6, and the game still crashes at the autosave info screen. Not mention it was even hard to login to my Uplay account so I could reply to this thread, kept loading and loading forever. Ubi come on!

voidpresence
05-27-2014, 08:52 PM
Can start the game fine, get into menus, but as soon as I try to start a New Game, it'll crash near the end of the load screen with a error message 'Watch Dogs has quit unexpectadly'. Error details:


Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000000ae669f
Faulting process id: 0x12f8
Faulting application start time: 0x01cf79c1e2c8dd86
Faulting application path: C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Watch_Dogs\bin\Watch_Dogs.exe
Faulting module path: C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Watch_Dogs\bin\Disrupt_b64.dll
Report Id: 45a8bae4-e5b5-11e3-be9c-1c6f65a0f765
Faulting package full name:


I have run the UPlay validate on the game and it's found and allegedly repaired, but i've done this at least 3 times now and it keeps finding a corrupt install.

One thing I noticed is that the game is installed in C:\Program Files (x86)\...which is the 32-bit application folder, even tho Watch Dogs is 64 bit.

knightley4
05-27-2014, 10:33 PM
I get this nasty bugger every time i try to go to the Loop district. Maybe it happens in other districts too, but i didn't check.


Problem signature:
Problem Event Name: APPCRASH
Application Name: Watch_Dogs.exe
Application Version: 0.1.0.1
Application Timestamp: 537507a1
Fault Module Name: Disrupt_b64.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5375077c
Exception Code: c0000005
Exception Offset: 00000000017343e9
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1049
Additional Information 1: 9f60
Additional Information 2: 9f605552b545d3185af014f7c4f8c024
Additional Information 3: 7fe3
Additional Information 4: 7fe39dfcdb3b9e196c9e786bcfb0431b

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Zinsane
05-27-2014, 10:45 PM
Game loads 70% of first map after clicking Play. Then crashes and I lose my mouse pointer.... eventually the error clears and this is all i find on my event viewer

Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000000134e54
Faulting process id: 0x1c08
Faulting application start time: 0x01cf79f35358f272
Faulting application path: E:\Uplay\Watch_Dogs\bin\Watch_Dogs.exe
Faulting module path: E:\Uplay\Watch_Dogs\bin\Disrupt_b64.dll
Report Id: b74b0440-e5e6-11e3-b21e-f46d04333e9d

bs90
05-28-2014, 12:20 AM
Yup , got the same problem, crashes when it's about done loading after the opening cinematic. And the mouse pointer also disappears.

"problem signature:
Problem Event Name: APPCRASH
Application Name: Watch_Dogs.exe
Application Version: 0.1.0.1
Application Timestamp: 537507a1
Fault Module Name: Disrupt_b64.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5375077c
Exception Code: c0000005
Exception Offset: 0000000000ae669f
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1044
Additional Information 1: ae09
Additional Information 2: ae09c43b3df4c26f8b1e634323336393
Additional Information 3: cbc0
Additional Information 4: cbc05b904372f84d5b04c59ab87cf36e

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt"

CptUndies
05-28-2014, 01:18 AM
I too, have the crash-to-desktop issue on game start. I get the Ubisoft logo and it crashes after about 2 seconds on the second splash screen.

Windows 8.1 64bit
Intel i7-980X
AMD 6990
3 x 1920x1200 screens
12GB RAM

Crash report:

Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000001d7433c
Faulting process id: 0x7b8
Faulting application start time: 0x01cf7a010381f899
Faulting application path: C:\Games\Steam\steamapps\common\Watch_Dogs\bin\Wat ch_Dogs.exe
Faulting module path: C:\Games\Steam\steamapps\common\Watch_Dogs\bin\Dis rupt_b64.dll
Report Id: 5141fe1f-e5f4-11e3-bf2f-6cf0495cb4e5
Faulting package full name:
Faulting package-relative application ID:

I have tried the following:

Uninstall/Reinstall
Ensure Crossfire isn't forced on for unsupported games (crossfire can not be disabled on the 6990)
Ensured clean Catalyst 14.4 drivers are installed
Run with a single monitor
Antivirus off
Offline mode
UPlay overlay off


Ubisoft support's response was this:

Can you please uninstall the game completely from your system and then either disables one of the Monitors or one of your graphic cards, as the game does not support Dual monitors or crossfire graphic cards.

As I had already stated I had tried it with a single monitor, I uninstalled, reinstalled and tried again. No difference.

Crazyauzzie2010
05-28-2014, 01:24 AM
Why in hells name would they not support dual monitors or crossfire. I can understand crossfire, maybe. Btu dual monitors? What's the issue with that...

Crazyauzzie2010
05-28-2014, 01:48 AM
Why not crossfire, its only been around now for aeons.

Because so many other games have issue with that. It's rare I've met a game that cant handle dual monitors.

MajikSpoon
05-28-2014, 03:32 AM
Country + Format: United States: Windows 7 PC

Usernames & Gamertags: MajikSpoon

Frequency: Every time

Since when does it happen: Played game for 45 minutes, quit, restarted and issue started from there

Describe what is the issue encountered: Game Crashes

Define the Flow of the error: While attempting to Continue an existing game, loading screen reaches 80+% and crashes

Anything else you think is useful:

Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000001887ca7
Faulting process id: 0xfc0
Faulting application start time: 0x01cf7a17e69c17bd
Faulting application path: D:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Watch_Dogs\bin\Watch_Dogs.exe
Faulting module path: D:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Watch_Dogs\bin\Disrupt_b64.dll
Report Id: 43783f0c-e60b-11e3-a953-240a64509e3e

Build:
Self Built i7-4770K, 16Gb Memory, Windows 7 Pro 64-bit, GTX780Ti Video

hrtrulz
05-28-2014, 07:23 AM
I was having the same issue with the Disrupt _b64.dll file.

I fixed the by firstly deleting this file and verifying the game in uPlay.

After verify was complete, I added the Disrupt _b64.dll file to the execption list in Windows Defender. I also disabled Automatic posts to social wall and now it works.

I also re-enabled 'Automatic posts to social wall' and the game crashed, so make sure you have this disabled.

KakTyCeHok
05-28-2014, 09:31 AM
Скопировав с DVD-1 файл disrupt_b64.dll, загрузка новой игры происходит 100%, но после этого ничего нет на мониторе, только черный экран, но время игры идет, и ресурсы скачут

Copying from DVD-1 file disrupt_b64.dll, download a new game is 100%, but after that nothing on the monitor, only a black screen, but the game goes, and resources jump
-----------------
Upd:
Таким образом я сейчас проиграл 28 минут не играя, и не видя ошибку
So now I have lost 28 minutes without playing, and not seeing the error
-----------------
And full no coincidence versions written in readme.txt (version 1.0), and in the executable version 0.1.0.1

TimPe84
05-28-2014, 10:34 AM
I was having the same issue with the Disrupt _b64.dll file.

I fixed the by firstly deleting this file and verifying the game in uPlay.

After verify was complete, I added the Disrupt _b64.dll file to the execption list in Windows Defender. I also disabled Automatic posts to social wall and now it works.

I also re-enabled 'Automatic posts to social wall' and the game crashed, so make sure you have this disabled.

I was having same error. This worked for me. Thx.

J05H4
05-28-2014, 11:07 AM
Thanks for your replies :) Here is the error message:

Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000001d7433c
Faulting process id: 0x1134
Faulting application start time: 0x01cf76b8afb48a43
Faulting application path: G:\Ubisoft\Ubisoft Game Launcher\Games\Watch_Dogs\bin\Watch_Dogs.exe
Faulting module path: G:\Ubisoft\Ubisoft Game Launcher\Games\Watch_Dogs\bin\Disrupt_b64.dll
Report Id: fb83f8f9-e2ab-11e3-9255-bcaec5309bf8

Yesterday I realized that servers were drastically overloaded. Today I was finally able to log into my Uplay Account and selected the repair option within Uplay.
It told me that there was several damaged data. Uplay did fix it, but when starting i still had the same problems with disrupt_b64.dll stopped working.

Now what you should try is taking out that data of its folder it should be located in your watchdogs location at the bin/ folder and place it in a different folder within the watchdogs location. For me it was D:/watchdogs/damaged/.
Next step was trying the repair option again and it finally loaded a new 3 Gigs of data from the ubisoft servers.

Now it works so try it out if servers a working today!

bs90
05-28-2014, 11:08 AM
I was having the same issue with the Disrupt _b64.dll file.

I fixed the by firstly deleting this file and verifying the game in uPlay.

After verify was complete, I added the Disrupt _b64.dll file to the execption list in Windows Defender. I also disabled Automatic posts to social wall and now it works.

I also re-enabled 'Automatic posts to social wall' and the game crashed, so make sure you have this disabled.

Thanks a lot man! this fixed it for me!

guest-zUzBrEoB
05-28-2014, 11:37 AM
I was having the same issue with the Disrupt _b64.dll file.

I fixed the by firstly deleting this file and verifying the game in uPlay.

After verify was complete, I added the Disrupt _b64.dll file to the execption list in Windows Defender. I also disabled Automatic posts to social wall and now it works.

I also re-enabled 'Automatic posts to social wall' and the game crashed, so make sure you have this disabled.

Thank you so much! It worked! You deserve praise from Ubisoft tech support :p

Crazyauzzie2010
05-28-2014, 11:51 AM
I was having the same issue with the Disrupt _b64.dll file.

I fixed the by firstly deleting this file and verifying the game in uPlay.

After verify was complete, I added the Disrupt _b64.dll file to the execption list in Windows Defender. I also disabled Automatic posts to social wall and now it works.

I also re-enabled 'Automatic posts to social wall' and the game crashed, so make sure you have this disabled.

Didn't fix it for me. Seems this game is determined to not run on an Radeon HD 6990...

Sariusus
05-28-2014, 12:00 PM
after updating the amd drivers to the 14.6 beta it worked yesterday wanted to continue today -> not working again Disrupt _b64.dll

this game rly makes me go crazy

DarkKillerSeb
05-28-2014, 02:32 PM
Hello everyone,

Regarding this error, I was able to move a little by disabling CrossfireX of my 2 ATI cards. But replanted after making a new game. Always this error Disrupt _b64.dll. It perhaps should move a little. Able when do you play on PC Watch Dogs correctly?

In addition, when I do a file check I still have a problem of corrupted file and I repair loop.

So many problem:

- Problem ATI Drivers / Nvidia SLI and CrossfireX modes?
- Does the Uplay servers provide all the files correctly?
- A patch?

Thank you for your return

Together we'll find a solution friends ... ;)

Sebastien, French gamer

Loup-Artic
05-28-2014, 04:35 PM
Didn't fix it for me. Seems this game is determined to not run on an Radeon HD 6990...

Hi,

Sorry its in french but i have HD6990 and found a fix to play.

http://forums-fr.ubi.com/showthread.php/71034-quot-Watch_Dogs-a-cess%C3%A9-de-fonctionner-quot?p=1031357&viewfull=1#post1031357

In brief :

Amd cleaner.
Download and extract beta package driver but not install.
Install manually driver with device manager.
Reboot.

I play in ultra, FXAA but only have 30 fps and one GPU enabled. Always better than crash :).
Waiting a patch for full performance.

RonnyBSC
05-28-2014, 06:11 PM
Hi,

Sorry its in french but i have HD6990 and found a fix to play.

http://forums-fr.ubi.com/showthread.php/71034-quot-Watch_Dogs-a-cess%C3%A9-de-fonctionner-quot?p=1031357&viewfull=1#post1031357

In brief :

Amd cleaner.
Download and extract beta package driver but not install.
Install manually driver with device manager.
Reboot.

I play in ultra, FXAA but only have 30 fps and one GPU enabled. Always better than crash :).
Waiting a patch for full performance.

Great :)
It Works:cool:

The driver I have unpacked with 7zip
and then manually installed via the device manager.
This recognizes now instead of HD 6990
two HD6900 cards, ...
I do not care, the main thing is this game is first:rolleyes:

eLeNzO1826
05-28-2014, 06:24 PM
Just want to know if anybody got a solution to this error because last night I was still playing and I try to play again but uplay did an update and now I have that error.

Really want a solution like in now because I paid good money for this yesterday.:mad::mad::mad::mad::mad::mad::mad::mad: :mad::mad::mad::mad:

soulwynd
05-28-2014, 09:29 PM
Just letting you guys know that deleting Disrupt_b64.dll and then telling the game to repair fixed it for me.

hrtrulz
05-29-2014, 03:27 AM
I found based on a different issue I has having the verify doesn't seem to verify everything correctly every time is run, you need to keep running the verify until you get know errors.

LudicrousLlama
05-29-2014, 08:19 AM
After the game stopped responding I checked the Event Viewer and it did say the the Disrupt_b64.dll was the fault. I was looking through the folders with .dll files and I could open them all except for the Disrupt_b64.dll. It would just try to load and go unresponsive leading to it needing to be closed. Another file that occurs along side the Disrupt file is the ntdll.dll. I'm not sure what the ntdll.dll does but it occurs almost every time the Disrupt_b64.dll does.

I deleted the Disrupt .dll and verified files but that didn't help.

Crazyauzzie2010
05-29-2014, 09:23 AM
After the game stopped responding I checked the Event Viewer and it did say the the Disrupt_b64.dll was the fault. I was looking through the folders with .dll files and I could open them all except for the Disrupt_b64.dll. It would just try to load and go unresponsive leading to it needing to be closed. Another file that occurs along side the Disrupt file is the ntdll.dll. I'm not sure what the ntdll.dll does but it occurs almost every time the Disrupt_b64.dll does.

I deleted the Disrupt .dll and verified files but that didn't help.

Don't touch ntdll.dll. I replaced it awhile ago, made my whole computer not start up and I ended up having to do a clean wipe install. For the love of all mighty, don't touch it.

Crazyauzzie2010
05-29-2014, 09:27 AM
Hi,

Sorry its in french but i have HD6990 and found a fix to play.

http://forums-fr.ubi.com/showthread.php/71034-quot-Watch_Dogs-a-cess%C3%A9-de-fonctionner-quot?p=1031357&viewfull=1#post1031357

In brief :

Amd cleaner.
Download and extract beta package driver but not install.
Install manually driver with device manager.
Reboot.

I play in ultra, FXAA but only have 30 fps and one GPU enabled. Always better than crash :).
Waiting a patch for full performance.

Nope, I just went through every step of that, and it didn't fix it. Even with Crossfire turned off.

knjava
05-29-2014, 11:10 AM
Sorry for my english

So, i had Disrupt B64.dll error.

In my case solution was very easy...Just disabling one of VGA cores in Device Manager...(I have 2x6990)

But i still can't use my screen's native resolution

Yamirkr
05-29-2014, 03:13 PM
this fixed it for me^^
http://forums.ubi.com/showthread.php/882948-Unable-to-play-with-AMD-HD6990s-mega-thread?p=9997284&viewfull=1#post9997284

cmoore66
05-29-2014, 03:32 PM
I had similar issue. Hit new game then ~70% into load bar it crashed.
Ran verify 3-4 times (each time different DL size on fix) and managed to get in game.
But now game crashes anytime I go near Loop district, same error.

soulwynd
05-29-2014, 05:46 PM
It's becoming clear that the problem seems to be related to uplay not being able to download the damn files correctly.

The problem for me is the windy_city.dat being corrupted. When I ask it to repair, it starts at 81%, then the game is playable until you move away from the starting zone, where it crashes again. If you repair again, it tries to download about 50mb and you get missing ground. If you repair again it goes back to 81% and this repeats over and over without fixing the file.

So I've just deleted windy_city.dat and am letting uplay download the entire file again in hope that it wont be corrupted this time around.

From what I've read, this appears to be happening to the ones having issue, I've read the 81% download thing in a few posts. From my 500gb+ of games, this is the only one using uplay and the only one with what appears to have a corrupted file issue. The culprit seems to be uplay itself not being able to handle the file right.

Well, I only have 2mbps, so It will take around 6 hours at least for the file to download, I will update later if this helps any.

Derija93
05-29-2014, 10:44 PM
It's becoming clear that the problem seems to be related to uplay not being able to download the damn files correctly.

The problem for me is the windy_city.dat being corrupted. When I ask it to repair, it starts at 81%, then the game is playable until you move away from the starting zone, where it crashes again. If you repair again, it tries to download about 50mb and you get missing ground. If you repair again it goes back to 81% and this repeats over and over without fixing the file.

So I've just deleted windy_city.dat and am letting uplay download the entire file again in hope that it wont be corrupted this time around.

From what I've read, this appears to be happening to the ones having issue, I've read the 81% download thing in a few posts. From my 500gb+ of games, this is the only one using uplay and the only one with what appears to have a corrupted file issue. The culprit seems to be uplay itself not being able to handle the file right.

Well, I only have 2mbps, so It will take around 6 hours at least for the file to download, I will update later if this helps any.

It's the exact thing that I've been having so far. I wrote a ticket Wednesday night, however since today was a holiday in my country it probably hasn't even been read yet. I honestly don't really expect a solution anyway. Last time I wrote a ticket it took the support team more than a week to simply tell me "can't do."
I'm eagerly waiting for your update. I do suspect the same, that UPlay simply fails to retrieve the correct files. Then again I'm wondering how the hell it works for a lot of other players. I don't get it. I bet Ubisoft doesn't get it either.

It would be awesome to have a mirror of the files somewhere just to be able to double-check.

Update: I've deleted windy_city.dat (and windy_city.fat just for the sake of it) and let it redownload it. Up until now, it's not perfect, but at least I can play the game somewhat.

saintpoida
05-30-2014, 12:41 AM
this fixed it for me^^
http://forums.ubi.com/showthread.php/882948-Unable-to-play-with-AMD-HD6990s-mega-thread?p=9997284&viewfull=1#post9997284

This fixed it for me also, at least im at main menu about to try play.

It seems the link above is fixing a few ppl with ATI 6990s and even an SLI so it might be a fix for dual gpus if other people want to give it a whirl

AtotehZ
05-30-2014, 05:20 AM
This is what I did to overcome the disrupt64 error:

1. Restart the computer

2.
http://www.mediafire.com/convkey/ceee/yxgt02qnz6x2crcfg.jpg

The image is in Danish, but I've translated the vital parts.

Vertical sync can be active if you need it, but it gives a huge blow to your frame rate. Prerendered frames gives more input delay, which sucks.
The rest are necessary.

Malk1967
05-30-2014, 08:01 AM
I was having the same issue with the Disrupt _b64.dll file. I fixed the by firstly deleting this file and verifying the game in uPlay.

I had consistently been unable to leave the stadium start zone as the game would crash as soon as I reached the checkpoint by the door. After a brief bit of googling I realised I had a common issue with the error in Error Reporting always citing Disrupt_b64.dll as the cause of the crash. I tried everything that had been mentioned as fixes but nothing ever changed the crash to desktop with me reaching the checkpoint.

And then I saw hrtrulz's solution. I was unable to check it last night as Uplay refused to let me go online but I was finally able to get it online and verifying the game files earlier this morning. It was a relatively quick check and re-download that removing Disrupt_b64.dll caused and this time the game crashed before even loading my previous progress so I told it to check the game again and this time it was a few GB it decided were needed. And after this second verification/re-download the game actually worked!

I was able to play and drive etc, all the way up to the first rest point where I had to stop playing. I was also able to easily change all the settings back to the auto-detected setup.

EDIT: Just had another go at the game and all still seems fine.

So if you're having trouble with Disrupt_b64.dll try deleting it and getting Uplay to verify the game and see if that works. If it doesn't make Uplay keep verifying and 'fixing' and hopefully you'll be able to play too.

DarkarChris
05-30-2014, 03:43 PM
Here you can find, the possible problem and my fix: http://forums.ubi.com/showthread.php/885077-Killing-Disrupt_b64-dll-error(fix)-at-New-Game-and-possibl-other-instance-of-the-game?p=10001461#post10001461

blair34
05-30-2014, 04:10 PM
Mine says "Disrupt_b64.dll is missing from your computer" can anyone help me ? pleaaaseee !!!

Derija93
05-30-2014, 05:24 PM
Mine says "Disrupt_b64.dll is missing from your computer" can anyone help me ? pleaaaseee !!!

First of all, how about you open your own thread instead of spamming several other ones?

Second: yes. UPlay provides you with a function called "Verify files". Access it by clicking the little arrow to the right of the "PLAY" button when you have Watch_Dogs selected. Run that, then after a while click "repair" and UPlay should download the file.
Nevertheless, it's only missing if you manually delete it... Not to blame anyone here. ~

archangel_80
06-01-2014, 09:40 AM
Hi!

I just found this thread where a user posted a solution that got his (and my) game to work again! We both experienced the Disrupt_b64.dll app crash problem.
http://forums.ubi.com/showthread.php/883909-Game-Crashes-Before-Main-Menu-SLI-Enabled-on-337-88-Drivers-Possible-Workaround?p=9995328&viewfull=1#post9995328

He has an SLI rig, and I tested it on my ADM Crossfire rig and also go it to work.

I didn't have to turn off in-game overlay, nor use offline mode or any other of the multiple suggestions in different threads. This little fix took care of my app crash problem.

Quoted solution

Here's my discovery. Even with the latest SLI drivers, the game still crashed for me. Disabling SLI would allow me to play the game at reduced performance. I finally found a way to fix my issue.

I modified the GamerProfile.xml file for Watch_Dogs located under My Games\Watch_Dogs\[hex-string]\GamerProfile.xml with Notepad
Note: I deleted this file first and let Watch_Dogs load (and ultimately close) first before changing my file.

I made a change to Quality within the RenderProfile section. Whenever it was on _runtime, optimal, or low, my game would crash at that screen. If I manually overwrote the value to medium, high, or ultra the game loaded without problems.

AtotehZ
06-01-2014, 10:31 AM
Here's my discovery. Even with the latest SLI drivers, the game still crashed for me. Disabling SLI would allow me to play the game at reduced performance. I finally found a way to fix my issue.

I modified the GamerProfile.xml file for Watch_Dogs located under My Games\Watch_Dogs\[hex-string]\GamerProfile.xml with Notepad
Note: I deleted this file first and let Watch_Dogs load (and ultimately close) first before changing my file.

I made a change to Quality within the RenderProfile section. Whenever it was on _runtime, optimal, or low, my game would crash at that screen. If I manually overwrote the value to medium, high, or ultra the game loaded without problems.

Confirmed, I will contact a moderator to get known issues updated. Good job :)

aynser
06-01-2014, 12:55 PM
This doesnt actually solve the problem though.
For a lot of ppl the problem is that Uplay seems to be unable to download files that arent corrupted and tries to repair the same files over and over again.
I tried the approach that archangel suggested but my game still crashes.

AtotehZ
06-01-2014, 05:31 PM
This doesnt actually solve the problem though.
For a lot of ppl the problem is that Uplay seems to be unable to download files that arent corrupted and tries to repair the same files over and over again.
I tried the approach that archangel suggested but my game still crashes.

You either did it wrong, or you are not getting the disrupt_b64.dll error, but something else. My buddy has a completely different system.. I have a GTX 690 from nvidia and he has a Radeon 6990 Reference 2x from ATI. We both had the error and this fixed it.

We're able to use dual-gpu as long as we use one of the presets above low.

It's this simple:

Move the file in Users\[name]\Documents\My Games\Watch_Dogs\[hex] while the game is shut down.
Start the game again again.


You can try experimenting with changing settings, but really, you should just set it to medium, high or ultra until they get around to fixing it. Any multi-gpu card is better off using 2 cores on medium than 1 core on low.

You can make it work with a single GPU by disabling everything related to multi-gpu in the control panel.

aynser
06-01-2014, 06:43 PM
I moved the file while uplay and the game werent running.
Then i started the game and quit to desktop.
I tried medium, high and ultra.
Before Trying that i was actually able to play for about 5-10 minutes without the game crashing, afterwards it crashed while loading (disrupt_b64.dll error).

Im happy that it worked for you (at least some people seem to be able to play :D)

[excuse my "bad english" - im neither a native speaker nor sober.. :nonchalance:]

aynser
06-01-2014, 08:12 PM
thought i just leave this (http://i.imgur.com/Kk30srY.png) here

AtotehZ
06-01-2014, 08:12 PM
I moved the file while uplay and the game werent running.
Then i started the game and quit to desktop.
I tried medium, high and ultra.
Before Trying that i was actually able to play for about 5-10 minutes without the game crashing, afterwards it crashed while loading (disrupt_b64.dll error).

Im happy that it worked for you (at least some people seem to be able to play :D)

[excuse my "bad english" - im neither a native speaker nor sober.. :nonchalance:]

You don't have to change the settings outside the game. Just use the presets in the game options. I don't know if it will make a difference for you when it crashes mid game, but it's worth a try.

Offtopic:
Epic cartoon btw. I couldn't agree more. I hate it when publishers use their own launchers, like people want to have 5 launchers running at the same time. It is bad enough with Origin from EA. Steam is powered by valve who also releases their own games, but they release games from anyone who is interested, even indie games from amateurs. If memory serves they released games other than the ones they published themselves from the very beginning, in 2003 I think it was.

It is probably because the publisher of a game on steam has to pay valve a percentage of the revenue, that can be costly with big titles.

Derija93
06-01-2014, 10:28 PM
You either did it wrong, or you are not getting the disrupt_b64.dll error, but something else. My buddy has a completely different system.. I have a GTX 690 from nvidia and he has a Radeon 6990 Reference 2x from ATI. We both had the error and this fixed it.

We're able to use dual-gpu as long as we use one of the presets above low.

It's this simple:

Move the file in Users\[name]\Documents\My Games\Watch_Dogs\[hex] while the game is shut down.
Start the game again again.


You can try experimenting with changing settings, but really, you should just set it to medium, high or ultra until they get around to fixing it. Any multi-gpu card is better off using 2 cores on medium than 1 core on low.

You can make it work with a single GPU by disabling everything related to multi-gpu in the control panel.

Excuse the language, but bull****. It's bold to just say "you either did it wrong, or you are not getting the disrupt_b64.dll error, but something else." You dare questioning the abilities of others to use their sane mind to see and read "faulting module name: disrubt_b64.dll"?

I hope you do realize that there is a different thread out there regarding SLI and Crossfire issues... your solution is posted in that thread for a reason.
While this may solve the problems for a lot of players out there, folks like me who don't even use two GPUs are likely to still have this exception. Why? Because apparently (unconfirmed but evidence is abundant) UPlay fails to correctly download all the files or even identify corrupted ones.

In general, it seems that if you are unable to even reach the main menu in the first place, you're having a graphics-settings-related issue. Otherwise, if your game crashes after loading your save, specifically after leaving or entering a certain area, then it's likely some of your game files are corrupt.

Now please, stop trying to tell us that we have to adjust our graphics card settings... there are more causes for this exception to arise than just one.

MrPlugin
06-01-2014, 10:54 PM
So I had the game running, then I changed some settings in the graphics menu after which I started to get that 'disrupt' crash on the second 'after logo' screen, whenever I launched the game.
After a lot of trial and error I thought I go to Nvidia GeForce experience app, there I added the game and pressed OPTIMiSE it reverted the settings for the game best performance I guess, after which I was able to launch the game again with no issues. Now need to figure out how to get rid of that terrible LAG and SCREENSHOT effect (when you have a screenshot of your first ingame frame popping up constantly as a opaque image.

I have:
Asus z87-Pro
Overclocked i7 4770
16GB RAM
GeForce 690 and
SSD

AtotehZ
06-02-2014, 09:36 AM
In general, it seems that if you are unable to even reach the main menu in the first place, you're having a graphics-settings-related issue. Otherwise, if your game crashes after loading your save, specifically after leaving or entering a certain area, then it's likely some of your game files are corrupt.


I don't know if it will make a difference for you when it crashes mid game, but it's worth a try.

Meaning, when it comes to in-game errors I don't know if it would work or not. It was never problems with your GPU and always badly coded files, not necessarily corrupt. Bad code can surface under specific circumstances and be harmless in others. Same goes for crashing before main menu. All of these solutions are workarounds till Ubisoft fixes it with a patch.


You dare questioning the abilities of others to use their sane mind to see and read "faulting module name: disrubt_b64.dll"?

Yes I do, and as you can see from aynsers post it did fix the Disrupt_b64.dll. It just took some prodding to make him mention it. He did not get Disrupt_b64.dll error when it crashed in-game. He had an another problem on top of it.

Oh, and it's my birthday today.

aynser
06-02-2014, 06:42 PM
Unfortunately it didnt solve the disrupt_b64.dll issue but lead to the game crashing without even loading the save.
Before i was able to play between 5 and 10, sometimes 30 minutes before the disrupt error occured.

If i can be honest though i really lost interest in the game at this point.
Ill just wait until Ubi releases a patch and make sure never to buy any of their games at launch again.

Hope you have a nice birthday...

MADi2K
06-03-2014, 11:50 AM
Got the some problems, in the beging. Used Verify many times, up to this moment when game starts (usually), and after few minuts i'm getting distrupt_b64.dll error.

Tried to verify files again, game alwas finds someting damaged. Downloads it. Then says everything is ok, i try too play.... back to square one.

1. Changed HDD's (SDD's) - game was installed on 3 diffrent media - so it's not a problem with storage
2. Latest updates, dirver (Nvidia 780, i7, 24Gram) - Machine is ROCK solid (i'm havy gamer and this is only one game i'm having issius right now - and at least 30 others installed on system working perfectly)


My question is :
Is there a source with checksums for game files to verify downloaded files? Why can't I find simple crc32, sha1 or whatever to see for myself witch files are bad? For example i calculated sha1 for windy_city (5G) file which after each verify is diffrent!. - Thought there mey be problem with internet connection (downloaded 5 diffrent full linux dvd and there checksums were ok).

People (UBI) do something about it!!!! Get us measns to repair/install the game - we are paying for it, god damn.

Broadeas
06-03-2014, 09:20 PM
Crashes Randomly
Sometimes after a few minutes of playing, sometimes it stays up for over an hour with no crashing.

ERROR:

Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000001d7cf99
Faulting process id: 0x1cdc
Faulting application start time: 0x01cf7f62a2156a72
Faulting application path: C:\Games\Steam\steamapps\common\Watch_Dogs\bin\Wat ch_Dogs.exe
Faulting module path: C:\Games\Steam\steamapps\common\Watch_Dogs\bin\Dis rupt_b64.dll
Report Id: 06ba6e64-eb58-11e3-8307-c86000e203b0

DxDIAG
------------------
System Information
------------------
Time of this report: 6/3/2014, 13:21:15
Machine name: COPYRIGHT-PC
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 08/13/13 18:22:21 Ver: 21.04
Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (8 CPUs), ~3.5GHz
Memory: 16384MB RAM
Available OS Memory: 16328MB RAM
Page File: 3104MB used, 14245MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Sound Tab 4: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 780
Manufacturer: NVIDIA
Chip type: GeForce GTX 780
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1004&SUBSYS_27843842&REV_A1
Display Memory: 4095 MB
Dedicated Memory: 2994 MB
Shared Memory: 1101 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: ASUS VG278
Monitor Id: ACI27F8
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,n vwgf2um,nvwgf2um
Driver File Version: 9.18.0013.3788 (English)
Driver Version: 9.18.13.3788
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 5/19/2014 19:44:03, 17480432 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-5344-11CF-3E55-89071CC2C435}
Vendor ID: 0x10DE
Device ID: 0x1004
SubSys ID: 0x27843842
Revision ID: 0x00A1
Driver Strong Name: oem40.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section0 93:9.18.13.3788:pci\ven_10de&dev_1004
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

Card name: NVIDIA GeForce GTX 780
Manufacturer: NVIDIA
Chip type: GeForce GTX 780
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1004&SUBSYS_27843842&REV_A1
Display Memory: 4095 MB
Dedicated Memory: 2994 MB
Shared Memory: 1101 MB
Current Mode: 1050 x 1680 (32 bit) (59Hz)
Monitor Name: HP Compaq LA2205 Wide LCD Monitor
Monitor Model: LA2205
Monitor Id: HWP2848
Native Mode: 1680 x 1050(p) (59.954Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,n vwgf2um,nvwgf2um
Driver File Version: 9.18.0013.3788 (English)
Driver Version: 9.18.13.3788
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 5/19/2014 19:44:03, 17480432 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-5344-11CF-3E55-89071CC2C435}
Vendor ID: 0x10DE
Device ID: 0x1004
SubSys ID: 0x27843842
Revision ID: 0x00A1
Driver Strong Name: oem40.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section0 93:9.18.13.3788:pci\ven_10de&dev_1004
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

-------------
Sound Devices
-------------
Description: Speakers (Creative SB X-Fi)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Digital Audio (S/PDIF) (High Definition Audio Device)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_104384FB&REV_1003
Manufacturer ID: 1
Product ID: 65535
Type: WDM
Driver Name: HdAudio.sys
Driver Version: 6.01.7601.17514 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 11/20/2010 20:23:47, 350208 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: SPDIF Out (Creative SB X-Fi)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Digital Audio (S/PDIF) (High Definition Audio Device)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_104384FB&REV_1003
Manufacturer ID: 1
Product ID: 65535
Type: WDM
Driver Name: HdAudio.sys
Driver Version: 6.01.7601.17514 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 11/20/2010 20:23:47, 350208 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
Description: Microphone (Creative SB X-Fi)
Default Sound Capture: Yes
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: S/PDIF-In (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: Line-In 2/Mic 2 (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: Yes
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: Auxiliary (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: "What U Hear" (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: Digital-In (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: Auxiliary 2 (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: Line-In (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0230.0004 (English)
Driver Attributes: Final Retail
Date and Size: 3/1/2014 00:55:20, 689048 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Controller (Afterglow Gamepad for Xbox 360)
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0E6F, 0x0213
FF Driver: n/a

Device Name: Razer Naga Hex
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1532, 0x0036
FF Driver: n/a

Device Name: Razer Naga Hex
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1532, 0x0036
FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x1E26
| Matching Device ID: usb\root_hub20
| Service: usbhub
|
+-+ Generic USB Hub
| | Vendor/Product ID: 0x8087, 0x0024
| | Location: Port_#0001.Hub_#0002
| | Matching Device ID: usb\class_09
| | Service: usbhub

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ HID Keyboard Device
| Vendor/Product ID: 0x04CF, 0x9811
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
|
+ Razer Naga Hex
| Vendor/Product ID: 0x1532, 0x0036
| Matching Device ID: hid\vid_1532&pid_0036&mi_01&col01
| Upper Filters: rzudd
| Service: kbdhid
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
|
+ Razer Naga Hex
| Vendor/Product ID: 0x1532, 0x0036
| Matching Device ID: hid\vid_1532&pid_0036&mi_00
| Upper Filters: rzudd
| Service: mouhid
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD

------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 136.9 GB
Total Space: 244.1 GB
File System: NTFS
Model: OCZ-VERTEX4 ATA Device

Drive: D:
Free Space: 825.3 GB
Total Space: 953.9 GB
File System: NTFS
Model: WDC WD1001FALS-00J7B1 ATA Device

Drive: F:
Free Space: 708.2 GB
Total Space: 953.9 GB
File System: NTFS
Model: WDC WD1001FALS-00J7B1

Drive: G:
Free Space: 416.3 GB
Total Space: 3815.3 GB
File System: NTFS
Model: ST4000DM000-1F2168

Drive: H:
Free Space: 1901.0 GB
Total Space: 1907.6 GB
File System: NTFS
Model: WDC WD20EARS-00MVWB0

Drive: I:
Free Space: 4.4 GB
Total Space: 1907.6 GB
File System: NTFS
Model: WDC WD20EARS-00MVWB0

Drive: E:
Model: HL-DT-ST BDDVDRW GGC-H20L
Driver: c:\windows\system32\drivers\cdrom.sys, 6.01.7601.17514 (English), , 0 bytes

--------------
System Devices
--------------
Name: Intel(R) USB 3.0 eXtensible Host Controller
Device ID: PCI\VEN_8086&DEV_1E31&SUBSYS_84CA1043&REV_04\3&11583659&0&A0
Driver: n/a

Name: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10
Device ID: PCI\VEN_8086&DEV_1E10&SUBSYS_84CA1043&REV_C4\3&11583659&0&E0
Driver: n/a

Name: Asmedia 106x SATA Controller
Device ID: PCI\VEN_1B21&DEV_0612&SUBSYS_84B71043&REV_01\4&2543D5D&0&00E3
Driver: n/a

Name: Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
Device ID: PCI\VEN_8086&DEV_1E2D&SUBSYS_84CA1043&REV_04\3&11583659&0&D0
Driver: n/a

Name: Creative SB X-Fi
Device ID: PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&36BEC05D&0&0800E4
Driver: n/a

Name: Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26
Device ID: PCI\VEN_8086&DEV_1E26&SUBSYS_84CA1043&REV_04\3&11583659&0&E8
Driver: n/a

Name: Intel(R) 82579V Gigabit Network Connection
Device ID: PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_04\3&11583659&0&C8
Driver: n/a

Name: NVIDIA GeForce GTX 780
Device ID: PCI\VEN_10DE&DEV_1004&SUBSYS_27843842&REV_A1\4&BAB4994&0&0008
Driver: n/a

Name: Intel(R) 7 Series/C216 Chipset Family SMBus Host Controller - 1E22
Device ID: PCI\VEN_8086&DEV_1E22&SUBSYS_84CA1043&REV_04\3&11583659&0&FB
Driver: n/a

Name: Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
Device ID: PCI\VEN_8086&DEV_0151&SUBSYS_84CA1043&REV_09\3&11583659&0&08
Driver: n/a

Name: High Definition Audio Controller
Device ID: PCI\VEN_10DE&DEV_0E1A&SUBSYS_27843842&REV_A1\4&BAB4994&0&0108
Driver: n/a

Name: Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller
Device ID: PCI\VEN_8086&DEV_2822&SUBSYS_84CA1043&REV_04\3&11583659&0&FA
Driver: n/a

Name: High Definition Audio Controller
Device ID: PCI\VEN_8086&DEV_1E20&SUBSYS_84FB1043&REV_04\3&11583659&0&D8
Driver: n/a

Name: Xeon(R) processor E3-1200 v2/3rd Gen Core processor DRAM Controller - 0150
Device ID: PCI\VEN_8086&DEV_0150&SUBSYS_84CA1043&REV_09\3&11583659&0&00
Driver: n/a

Name: Intel(R) 82801 PCI Bridge - 244E
Device ID: PCI\VEN_8086&DEV_244E&SUBSYS_84CA1043&REV_C4\3&11583659&0&E4
Driver: n/a

Name: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 8 - 1E1E
Device ID: PCI\VEN_8086&DEV_1E1E&SUBSYS_84CA1043&REV_C4\3&11583659&0&E7
Driver: n/a

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_1B21&DEV_1080&SUBSYS_84891043&REV_03\4&2AACEACC&0&00E4
Driver: n/a

Name: Intel(R) Z77 Express Chipset LPC Controller - 1E44
Device ID: PCI\VEN_8086&DEV_1E44&SUBSYS_84CA1043&REV_04\3&11583659&0&F8
Driver: n/a

Name: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 4 - 1E16
Device ID: PCI\VEN_8086&DEV_1E16&SUBSYS_84CA1043&REV_C4\3&11583659&0&E3
Driver: n/a

Name: ASMedia XHCI Controller
Device ID: PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&D432303&0&00E2
Driver: n/a

Name: Intel(R) Management Engine Interface
Device ID: PCI\VEN_8086&DEV_1E3A&SUBSYS_84CA1043&REV_04\3&11583659&0&B0
Driver: n/a

Name: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 3 - 1E14
Device ID: PCI\VEN_8086&DEV_1E14&SUBSYS_84CA1043&REV_C4\3&11583659&0&E2
Driver: n/a

Name: ASMedia XHCI Controller
Device ID: PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&3927C719&0&00E7
Driver: n/a

------------------
DirectShow Filters
------------------

DirectShow Filters:
WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,6.01.7601.17514
WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,6.01.7601.17514
WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,6.01.7601.17514
MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,6.01.7600.16385
Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,6.01.7600.16385
WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,6.01.7601.17514
WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,6.01.7601.18221
Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,6.01.7600.16385
Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,6.01.7600.16385
CT Upsampler filter,0x00100000,1,1,Upsample.ax,2.00.0005.0000
Creative Wave Writer,0x00200000,1,0,WavWrite.ax,3.01.0004.0000
DV Muxer,0x00400000,0,0,qdv.dll,6.06.7601.17514
Color Space Converter,0x00400001,1,1,quartz.dll,6.06.7601.1771 3
WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.7601.17514
Screen Capture filter,0x00200000,0,1,wmpsrcwp.dll,12.00.7601.1751 4
AVI Splitter,0x00600000,1,1,quartz.dll,6.06.7601.17713
VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,6.06.7601.17713
SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,6.06.7 601.17528
Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,12.00.9200. 16426
BPM Metadata,0x001fffff,1,1,MetaBPMu.ax,2.00.0002.0000
Creative Recording Wav_Asio Filter,0x00400000,0,1,AudioRec.ax,1.00.0002.0000
AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,6.06.7601.17528
CT Time-Scaling filter,0x00100000,1,1,TimeScal.ax,2.03.0009.0000
StreamBufferSink,0x00200000,0,0,sbe.dll,6.06.7601. 17528
MJPEG Decompressor,0x00600000,1,1,quartz.dll,6.06.7601.1 7713
MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,6.06.7601.17713
SAMI (CC) Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.7601.17514
MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,6.06.7601.1752 8
Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,6.06.7601.17514
SBE2FileScan,0x00200000,0,0,sbe.dll,6.06.7601.1752 8
Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,6.01.7601.17 514
Internal Script Command Renderer,0x00800001,1,0,quartz.dll,6.06.7601.17713
MPEG Audio Decoder,0x03680001,1,1,quartz.dll,6.06.7601.17713
DV Splitter,0x00600000,1,2,qdv.dll,6.06.7601.17514
Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,6.06.7601.17713
PCM to EXT,0x00200000,0,0,Pcm2Ext.ax,6.00.0002.0000
CT Karaoke filter,0x00100000,1,1,Karaoke.ax,2.00.0012.0000
Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,6.01.7601.17 514
Creative AC3 Source Filter,0x00400000,0,1,AC3Srcu.ax,3.02.0001.0000
Creative PCM Raw Writer,0x00200000,1,0,RawWritu.ax,1.00.0000.0000
CT PDP filter,0x00100000,1,1,PDP.ax,1.00.0008.0000
ACM Wrapper,0x00600000,1,1,quartz.dll,6.06.7601.17713
Video Renderer,0x00800001,1,0,quartz.dll,6.06.7601.17713
MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,6.06.7601.17528
Line 21 Decoder,0x00600000,1,1,qdvd.dll,6.06.7601.17835
Video Port Manager,0x00600000,2,1,quartz.dll,6.06.7601.17713
Video Renderer,0x00400000,1,0,quartz.dll,6.06.7601.17713
VPS Decoder,0x00200000,0,0,WSTPager.ax,6.06.7601.17514
CT SmartVolumeManagement filter,0x00100000,1,1,DSCompr.ax,1.00.0008.0000
Creative Audio Gain Filter,0x00200000,1,1,AudGain.ax,1.00.0000.0000
WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.7601.17514
VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,6.01.7601.1751 4
Creative Flac Source Filter,0x00400000,0,1,FlacSrcu.ax,1.00.0002.0000
File writer,0x00200000,1,0,qcap.dll,6.06.7601.17514
Creative MLP Source Filter,0x00400000,0,1,MlpSrcu.ax,3.01.0000.0000
Creative File Reader Filter,0x00400000,0,1,FilReadu.ax,1.00.0005.0000
iTV Data Sink,0x00600000,1,0,itvdata.dll,6.06.7601.17514
iTV Data Capture filter,0x00600000,1,1,itvdata.dll,6.06.7601.17514
SVM Metadata,0x001fffff,1,1,MetaSVMu.ax,2.00.0002.0000
CT HPVirtualizer filter,0x00100000,1,1,Virtual.ax,1.00.0000.0000
DVD Navigator,0x00200000,0,3,qdvd.dll,6.06.7601.17835
Overlay Mixer2,0x00200000,1,1,qdvd.dll,6.06.7601.17835
CT CMSS3 filter,0x00100000,1,1,CMSS3.ax,3.00.0013.0000
AVI Draw,0x00600064,9,1,quartz.dll,6.06.7601.17713
RDP DShow Redirection Filter,0xffffffff,1,0,DShowRdpFilter.dll,
Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,6.01.7601.17 514
WST Pager,0x00200000,1,1,WSTPager.ax,6.06.7601.17514
MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,6.06.7601 .17528
Creative Ogg Source Filter,0x00400000,0,1,OggSrcu.ax,1.00.0001.0000
DV Video Decoder,0x00800000,1,1,qdv.dll,6.06.7601.17514
Creative NVF Filter,0x00400000,0,1,NvfSrcu.ax,3.01.0001.0000
Noise Reduction,0x00100000,1,1,NoisRedu.ax,3.00.0007.000 0
SampleGrabber,0x00200000,1,1,qedit.dll,6.06.7601.1 8386
Null Renderer,0x00200000,1,0,qedit.dll,6.06.7601.18386
Creative WMA Writer,0x00200000,1,0,WMAWrite.ax,5.00.0001.0000
MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,6.06.7601.17514
Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,6.01.7601.1751 4
StreamBufferSource,0x00200000,0,0,sbe.dll,6.06.760 1.17528
Smart Tee,0x00200000,1,2,qcap.dll,6.06.7601.17514
Creative WMA Source Filter,0x00400000,0,1,WmaSrc.ax,3.01.0001.0000
Overlay Mixer,0x00200000,0,0,qdvd.dll,6.06.7601.17835
AVI Decompressor,0x00600000,1,1,quartz.dll,6.06.7601.1 7713
AVI/WAV File Source,0x00400000,0,2,quartz.dll,6.06.7601.17713
Wave Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
MIDI Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
Multi-file Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
File stream renderer,0x00400000,1,1,quartz.dll,6.06.7601.17713
Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,6.01.7140.0 000
StreamBufferSink2,0x00200000,0,0,sbe.dll,6.06.7601 .17528
AVI Mux,0x00200000,1,0,qcap.dll,6.06.7601.17514
Line 21 Decoder 2,0x00600002,1,1,quartz.dll,6.06.7601.17713
File Source (Async.),0x00400000,0,1,quartz.dll,6.06.7601.17713
File Source (URL),0x00400000,0,1,quartz.dll,6.06.7601.17713
Creative CDDA Source Filter,0x00400000,0,1,CDDA.ax,3.00.0003.0000
Creative LiveRecording Filter SxS,0x00400000,0,1,LiveRecu.ax,5.00.0001.0000
Creative Internet Source Filter,0x00400000,0,1,InetSrcu.ax,1.00.0000.0000
Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,6.06.7601.17514
Enhanced Video Renderer,0x00200000,1,0,evr.dll,6.01.7601.17514
BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,6.06.7601.17669
MPEG Video Decoder,0x40000001,1,1,quartz.dll,6.06.7601.17713

WDM Streaming Tee/Splitter Devices:
Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,6.01.7601.1751 4

Video Compressors:
WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,6.01.7600.16385
WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,6.01.7600.16385
MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,6.01.7600.16385
DV Video Encoder,0x00200000,0,0,qdv.dll,6.06.7601.17514
MJPEG Compressor,0x00200000,0,0,quartz.dll,6.06.7601.177 13
Cinepak Codec by Radius,0x00200000,1,1,qcap.dll,6.06.7601.17514
Intel IYUV codec,0x00200000,1,1,qcap.dll,6.06.7601.17514
Intel IYUV codec,0x00200000,1,1,qcap.dll,6.06.7601.17514
Microsoft RLE,0x00200000,1,1,qcap.dll,6.06.7601.17514
Microsoft Video 1,0x00200000,1,1,qcap.dll,6.06.7601.17514
RivaTuner Video Codec,0x00200000,1,1,qcap.dll,6.06.7601.17514

Audio Compressors:
WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,6.01.7600.16385
WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,6.01.7600.16385
IMA ADPCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
PCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
Microsoft ADPCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
GSM 6.10,0x00200000,1,1,quartz.dll,6.06.7601.17713
CCITT A-Law,0x00200000,1,1,quartz.dll,6.06.7601.17713
CCITT u-Law,0x00200000,1,1,quartz.dll,6.06.7601.17713
MPEG Layer-3,0x00200000,1,1,quartz.dll,6.06.7601.17713

Audio Capture Sources:
Microphone (Creative SB X-Fi),0x00200000,0,0,qcap.dll,6.06.7601.17514
"What U Hear" (Creative SB X-Fi,0x00200000,0,0,qcap.dll,6.06.7601.17514
Auxiliary (Creative SB X-Fi),0x00200000,0,0,qcap.dll,6.06.7601.17514
Auxiliary 2 (Creative SB X-Fi),0x00200000,0,0,qcap.dll,6.06.7601.17514
Digital-In (Creative SB X-Fi),0x00200000,0,0,qcap.dll,6.06.7601.17514
Line-In (Creative SB X-Fi),0x00200000,0,0,qcap.dll,6.06.7601.17514
Line-In 2/Mic 2 (Creative SB X-,0x00200000,0,0,qcap.dll,6.06.7601.17514
S/PDIF-In (Creative SB X-Fi),0x00200000,0,0,qcap.dll,6.06.7601.17514

PBDA CP Filters:
PBDA DTFilter,0x00600000,1,1,CPFilters.dll,6.06.7601.17 528
PBDA ETFilter,0x00200000,0,0,CPFilters.dll,6.06.7601.17 528
PBDA PTFilter,0x00200000,0,0,CPFilters.dll,6.06.7601.17 528

Midi Renderers:
Default MidiOut Device,0x00800000,1,0,quartz.dll,6.06.7601.17713
Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,6.06.7601.17713
SB X-Fi MIDI Port [C000],0x00200000,1,0,quartz.dll,6.06.7601.17713
SB X-Fi Synth A [C000],0x00200000,1,0,quartz.dll,6.06.7601.17713
SB X-Fi Synth B [C000],0x00200000,1,0,quartz.dll,6.06.7601.17713

WDM Streaming Capture Devices:
Digital-In,0x00000000,0,0,,
S/PDIF-In,0x00000000,0,0,,
Line-In 2/Mic 2,0x00000000,0,0,,
Auxiliary 2,0x00000000,0,0,,
,0x00000000,0,0,,
SB X-Fi MIDI Port [C000],0x00200000,2,2,ksproxy.ax,6.01.7601.17514
SB X-Fi Audio [C000],0x00200000,1,1,ksproxy.ax,6.01.7601.17514
SB Live!2K Audio [C000],0x00000000,0,0,,

WDM Streaming Rendering Devices:
HD Audio SPDIF out 5,0x00200000,1,1,ksproxy.ax,6.01.7601.17514
HD Audio SPDIF out,0x00200000,1,1,ksproxy.ax,6.01.7601.17514
,0x00000000,0,0,,
,0x00000000,0,0,,
,0x00000000,0,0,,
,0x00000000,0,0,,
SPDIF Out,0x00000000,0,0,,
SB X-Fi Synth A [C000],0x00200000,1,1,ksproxy.ax,6.01.7601.17514
SB X-Fi Synth B [C000],0x00200000,1,1,ksproxy.ax,6.01.7601.17514
SB X-Fi MIDI Port [C000],0x00200000,2,2,ksproxy.ax,6.01.7601.17514
SB X-Fi Audio [C000],0x00200000,1,1,ksproxy.ax,6.01.7601.17514
,0x00000000,0,0,,

BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,6.06.7601.17514

Multi-Instance Capable VBI Codecs:
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.7601.17514

BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,6.06.7601.17669
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,6.06.7601.17514

BDA CP/CA Filters:
Decrypt/Tag,0x00600000,1,1,EncDec.dll,6.06.7601.17708
Encrypt/Tag,0x00200000,0,0,EncDec.dll,6.06.7601.17708
PTFilter,0x00200000,0,0,EncDec.dll,6.06.7601.17708
XDS Codec,0x00200000,0,0,EncDec.dll,6.06.7601.17708

WDM Streaming Communication Transforms:
Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,6.01.7601.1751 4

Audio Renderers:
Speakers (Creative SB X-Fi),0x00200000,1,0,quartz.dll,6.06.7601.17713
Default DirectSound Device,0x00800000,1,0,quartz.dll,6.06.7601.17713
Default WaveOut Device,0x00200000,1,0,quartz.dll,6.06.7601.17713
Digital Audio (S/PDIF) (High De,0x00200000,1,0,quartz.dll,6.06.7601.17713
DirectSound: Digital Audio (S/PDIF) (High Definition Audio Device),0x00200000,1,0,quartz.dll,6.06.7601.17713
DirectSound: SPDIF Out (Creative SB X-Fi),0x00200000,1,0,quartz.dll,6.06.7601.17713
DirectSound: Speakers (Creative SB X-Fi),0x00200000,1,0,quartz.dll,6.06.7601.17713
SPDIF Out (Creative SB X-Fi),0x00200000,1,0,quartz.dll,6.06.7601.17713

---------------
EVR Power Information
---------------
Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality)
Quality Flags: 2576
Enabled:
Force throttling
Allow half deinterlace
Allow scaling
Decode Power Usage: 100
Balanced Flags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 50
PowerFlags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 0



Specs:
Win 7 home premium 64bit
Video:EVGA 780GTX
Motherboard: Asus P8Z77-V Pro
CPU: I7 3770K
Sound: Creative X-Fi Fatality
OS drive (and location watch_dogs is installed): OCZ Vertex 4

Stuff done to try to fix the issue:
Formatted HDD and re-installed OS
All video,sound,motherboard drivers are updated
Motherboard Bios updated
SSD drive FW updated

But no fix thus Far

JuanCala
06-05-2014, 09:50 PM
Got the some problems, in the beging. Used Verify many times, up to this moment when game starts (usually), and after few minuts i'm getting distrupt_b64.dll error.

Tried to verify files again, game alwas finds someting damaged. Downloads it. Then says everything is ok, i try too play.... back to square one.

1. Changed HDD's (SDD's) - game was installed on 3 diffrent media - so it's not a problem with storage
2. Latest updates, dirver (Nvidia 780, i7, 24Gram) - Machine is ROCK solid (i'm havy gamer and this is only one game i'm having issius right now - and at least 30 others installed on system working perfectly)


My question is :
Is there a source with checksums for game files to verify downloaded files? Why can't I find simple crc32, sha1 or whatever to see for myself witch files are bad? For example i calculated sha1 for windy_city (5G) file which after each verify is diffrent!. - Thought there mey be problem with internet connection (downloaded 5 diffrent full linux dvd and there checksums were ok).

People (UBI) do something about it!!!! Get us measns to repair/install the game - we are paying for it, god damn.

Regarding 2: Same here, I have a lot of games installed and deinstalled during my initial set up of Win7 Ultimate on my PC and all of them are / were running perfectly. There was never a problem. Only WD is crashing all over again. German support suggested to delete manually windy_city.dat, start Uplay as admin and repair. They also suggested to fidddle around with MSCONFIG, geez. No way, that is not necessary. It´s the fault game...please patch...

Mr_Shade
06-06-2014, 10:42 AM
Guys quick update:

We are still investigating on this issue. To help us make some progress, please follow these instructions:

Game crashing and freezing:


If you have a crash/freeze when playing Watch_Dogs, please send us your save game files which are located in "C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\savegames".

If the game crashes and you get the "Watch_Dogs has stopped working" dialog, click on "View problem details".

http://i.imgur.com/YGQse0C.png



This will show some technical details about the crash.
Select *all* the text (by clicking inside the text box, and pressing Ctrl-A), then copy it to the clipboard (by pressing Ctrl-C).


Please update your Support ticket with that text; this will help the programmers see where the game crashed.

If you have not yet made a support ticket - please do so at - www.support.ubi.com

http://i.imgur.com/gywoW9e.png



Advanced users can also send us a mini-dump, which will help the programmers pinpoint the crash more precisely.
To do so, you will have to install "Process Explorer" from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx.

When the game has crashed, and the "Watch_Dogs has stopped working" dialog appears:
Open Process Explorer, then right-click on Watch_Dogs.exe and select "Create Dump", and then "Create Minidump..."

This will allow you to save a Watch_Dogs.dmp file. This file, once compressed, should not take more than 2-3 MB, so you should be able to email to us.
If the file is a lot larger, that means you probably accidentally clicked on "Create Full Dump...".

http://i.imgur.com/zqbruqm.jpg



To upload your files to your Support case, follow the instructions below:

- Click on this link: http://support.ubi.com
- Type in your Uplay login name and password and click Login. Click on 'My Questions'
- Click on 'Ask a Question' and choose the appropriate Platform/Product, Category, and Subject/Question
- After you have explained your issue, please click 'Choose File' and upload your save file from your computer
- Finally, click 'continue' to complete the process

Once we receive your save files we will forward them up to the development team for further review.

Broadeas
06-07-2014, 09:08 PM
Well a day and a half with several hours of playing and no disrupt errors

1 of these steps, not sure which as I ran all of them in 1 go, seems to have fixed the Disrupt_b64.dll error. (I still get a few crashes, but not related to disrupt and not as often)

First I deleted the Folder in this directory: Documents\My Games\Watch_Dogs

then ran the dx,dotnet,and vcredist located here:
...\Steamapps\common\Watch_Dogs_CommonRedist\Direc tX\Jun2010\DXSETUP.exe ...\Steamapps\common\Watch_Dogs_CommonRedist\DotNe t\3.5\dotnetfx35.exe ...\Steamapps\common\Watch_Dogs_CommonRedist\DotNe t\3.5 Client Profile\DotNetFx35Client.exe ...\Steamapps\common\Watch_Dogs_CommonRedist\vcred ist\2008\vcredist_x64.exe ...\Steamapps\common\Watch_Dogs_CommonRedist\vcred ist\2010\vcredist_x64.exe ...\Steamapps\common\Watch_Dogs_CommonRedist\vcred ist\2008\vcredist_x86.exe ...\Steamapps\common\Watch_Dogs_CommonRedist\vcred ist\2010\vcredist_x86.exe

Next I deleted the files in this folder: data_win64\worlds\windy_city\

lastly I deleted the Disrupt_b64.dll file

Ran the check file integrity in Steam and it downloaded the missing files

Played game and no disrupt crashes.

I suspect the deleting of the game files was not what fixed it as I already re-installed the game which made no difference, and re-installed windows too which made no difference.

Armin-Tanzarian
06-09-2014, 03:40 PM
I have the same exactly problem. Disabling crossfirex option in catalyst 14.4 works fine for me.

The game runs again, with his own ton of Ultra random bugs


-CPU-
Intel Core i7 3930K @ 3.20GHz
Sandy Bridge-E 32nm Technology ☣//☣
-COOLER-
Corsair H110 ☣//☣
-RAM-
16,0GB DDR3 @ 1600MHz (9-9-9-24) ☣//☣
-Motherboard-
ASUSTeK COMPUTER INC. P9X79 PRO (LGA2011) ☣//☣
-Graphics-
DELL U2913WM (2560x1080@60Hz)
3072MB ATI AMD Radeon HD 7970 Series (Sapphire/PCPartner)
3072MB ATI AMD Radeon HD 7970 Series (Sapphire/PCPartner)
CrossFire Enabled ☣//☣
-Hard Drives-
112GB KINGSTON SV300S37A120G (SSD)
100GB OCZ (SSD)
2795GB TOSHIBA DT01ACA300 (SATA)
2795GB TOSHIBA DT01ACA300 (SATA)
1863GB Western Digital WDC WD20EARS-00MVWB0 (SATA)
106GB Microsoft Storage Space Device (TMax) ☣//☣
-Operating System-
Windows 8 Pro 64-bit ☣//☣

Broadeas
06-11-2014, 05:59 AM
Had a few days error free,
No changes to my PC
No driver or windows updates ect


Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x537507a1
Faulting module name: Disrupt_b64.dll, version: 0.0.0.0, time stamp: 0x5375077c
Exception code: 0xc0000005
Fault offset: 0x0000000001d7d216
Faulting process id: 0x16e4
Faulting application start time: 0x01cf852ce1aafbd4
Faulting application path: C:\Games\Steam\steamapps\common\Watch_Dogs\bin\Wat ch_Dogs.exe
Faulting module path: C:\Games\Steam\steamapps\common\Watch_Dogs\bin\Dis rupt_b64.dll
Report Id: 976c1382-f124-11e3-a37e-c86000e203b0

VkStyle123
06-11-2014, 05:04 PM
Guys quick update:

We are still investigating on this issue. To help us make some progress, please follow these instructions:

Game crashing and freezing:


If you have a crash/freeze when playing Watch_Dogs, please send us your save game files which are located in "C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\savegames".

If the game crashes and you get the "Watch_Dogs has stopped working" dialog, click on "View problem details".

http://i.imgur.com/YGQse0C.png



This will show some technical details about the crash.
Select *all* the text (by clicking inside the text box, and pressing Ctrl-A), then copy it to the clipboard (by pressing Ctrl-C).


Please update your Support ticket with that text; this will help the programmers see where the game crashed.

If you have not yet made a support ticket - please do so at - www.support.ubi.com

http://i.imgur.com/gywoW9e.png



Advanced users can also send us a mini-dump, which will help the programmers pinpoint the crash more precisely.
To do so, you will have to install "Process Explorer" from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx.

When the game has crashed, and the "Watch_Dogs has stopped working" dialog appears:
Open Process Explorer, then right-click on Watch_Dogs.exe and select "Create Dump", and then "Create Minidump..."

This will allow you to save a Watch_Dogs.dmp file. This file, once compressed, should not take more than 2-3 MB, so you should be able to email to us.
If the file is a lot larger, that means you probably accidentally clicked on "Create Full Dump...".

http://i.imgur.com/zqbruqm.jpg



To upload your files to your Support case, follow the instructions below:

- Click on this link: http://support.ubi.com
- Type in your Uplay login name and password and click Login. Click on 'My Questions'
- Click on 'Ask a Question' and choose the appropriate Platform/Product, Category, and Subject/Question
- After you have explained your issue, please click 'Choose File' and upload your save file from your computer
- Finally, click 'continue' to complete the process

Once we receive your save files we will forward them up to the development team for further review.

I can't upload watchdogs,dmp because dump is too big ~71 mb. Qfter 3% upoload page crash. I'm sure that it's thw MINI dump - i do this some times.

May be i send this to email or upload another site?

PS: i hope watch dogs's problemswill be solved soon

Broadeas
06-11-2014, 05:53 PM
I attached my dmp file to my ticket, tho My ticket has not yet been responded to yet. (been 5 days since I opened it)

Mr_Shade
06-11-2014, 06:23 PM
Hi,

As long as you have sent the ticket - they will have your information.

they might not reply, until they have an update on the issue as a whole.

Broadeas
06-11-2014, 06:26 PM
Yea dump file is too big
76 mb

Tried Ziping it too, gets to 60% then starts over at 0, then gets to 60% or so and fails.

I can span it to 3 files and upload each file 1 at a time I guess.

Broadeas
06-11-2014, 06:40 PM
"The total uploaded files size should not exceed 20Mb"

so cant upload even with splitting the file up

Broadeas
06-11-2014, 06:54 PM
Uploaded to google drive and dropsend
Put the links in my support ticket so they can download the file

Mr_Shade
06-11-2014, 08:01 PM
Hi Guys,

we no longer need any more info:

We have identified the factors that are creating this particular issue and are currently working on a fix. We’ll keep you updated when we know more on when we’ll be able to release it.

Thanks for your understanding.

aynser
06-11-2014, 10:13 PM
Hi Guys,

we no longer need any more info:

We have identified the factors that are creating this particular issue (...)

Let me guess...
Does it have to do with uplay???

... (http://www.funnyjunk.com/Fastest+selling+IP/funny-pictures/5174857/)

JabBauer
06-12-2014, 04:24 AM
Let me guess...
Does it have to do with uplay???

... (http://www.funnyjunk.com/Fastest+selling+IP/funny-pictures/5174857/)

Perhaps.. but uPlay will also be the solution ;)

Narvask
06-14-2014, 01:02 PM
Shame when the patch comes out I still can't play as I get 'there is a problem connecting to a Uplay service'

Mr_Shade
06-14-2014, 05:20 PM
Shame when the patch comes out I still can't play as I get 'there is a problem connecting to a Uplay service'

Hi,

If you have not already - it's important you are in contact with support - since they can help with connection issues

http://forums.ubi.com/showthread.php/881509-FAQ-s-for-main-questions-and-issues-PLEASE-READ!

There is a list of required ports there - and if you need further help - www.support.ubi.com

MaxxATotten
06-17-2014, 08:15 AM
Quote Originally Posted by MaxxATotten View Post
Completed the game, updated mobo drivers to hopefully fix the stuttering(which I'm thinking has to do with a combination of three things, shaders, menu stuffs and cellphone things, and draw distance for whatever reason[especially noticable on last mission before the
Spoiler:
]) and got the disrupt b(s)64 error. Now, it was either from completing the game, or from updating mobo drivers.


ubisoft
so I rolled everything back... everything but my network drivers... game still wont launch...

here is the actual error file

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-06-17T18:46:10.000000000Z" />
<EventRecordID>6966</EventRecordID>
<Channel>Application</Channel>
<Computer>Owner-PC</Computer>
<Security />
</System>
- <EventData>
<Data>Watch_Dogs.exe</Data>
<Data>0.1.0.1</Data>
<Data>537507a1</Data>
<Data>Disrupt_b64.dll</Data>
<Data>0.0.0.0</Data>
<Data>5375077c</Data>
<Data>c0000005</Data>
<Data>0000000001d7433c</Data>
<Data>e64</Data>
<Data>01cf8a5c5a951f06</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Watch_Dogs\bin\Watch_ Dogs.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Watch_Dogs\bin\Disrup t_b64.dll</Data>
<Data>a58b0a5b-f64f-11e3-826b-448a5b816641</Data>
<Data />
<Data />
</EventData>
</Event>

So with that being said, I could previously run the game until I completed it so the error is caused by the game, unless it has something to do with network drivers...

I wouldn't be in any bit of shock if this were the case either. This is the same error the game gives when it doesn't meet the hardware specs... (being that I upgraded my system since first buying the game.) If this error has something to do with system specs and network connections... it would probably mean... you're running a system check before allowing us to play the game. Making sure we are using the stuff your affiliates want us to use before we can even attempt to run it. That's what pissed me off to begin with, before I could even run the game. I technically met system requirements in regards to speeds, cores, gpus, memory, etc. In some instances I was beyond it, but since it didn't fit in your little spectrum of hardware I couldn't run it. I bet you guys had to fight intel and amd to allow people to run it on phenom ii x6 and the minimum intel one. I got an intel i7 4930k. dual sli 550ti's. The game ran on my comp for 3 days. Today... it goes back to the error it gave me before I upgraded. You kinda suck Ubisoft. Plus the stuttering, that's something wrong with your software. this game hardly looks better than any gta game, the character animations sure don't compare to their engine, it's your software, and not peoples systems. Release a patch for this error first. Then worry about optimizing your stuff because it's obviously going to take you a year.


Please don't **** up The Division. Tom Clancy games came from back in the day when I'm pretty sure they were porting PC games to consoles... It deserves to work on PC right... You built these games on PCs... for ****s sake. And the stunt with the requiring people to beg to put it on PC is just insulting. Whoever thought that **** up deserves are beating. "Yeah, why should we put it on pc? we will only sell 15 million copies"
Either A. you were trying to make sure it was worth the money to ignore the console exclusives deals (a greedy **** move), or B. you were trying to hype it up even more(a greedy **** move.) There is also C. you were sick of making PC games that had almost no one playing the multiplayer because you make ****ty multiplayer.

So hopefully, this failure, as profitable as it was for you despite it, marks a turning point. You got Unity, which looks like it actually has a good multiplayer coop mode, and you got the division. These two games are critical to make a good pc release. Why the divisions system requirements are lower than watchdogs is beyond me... well no, its not... watchdogs had so much hype because of the deals with gpus and cpu companies.

Anyways... Fix the disrupt x64 error... fix it the moral way if I am right about what is causing it.
and btw even if I am wrong about what is causing it... You're still becoming a shady company in my book... your games always have political agendas embedded in the story. Commentary on American culture when half the games are made in Canada."a corrupt Chicago mayor, what a surprise" after gaining an endless file of blackmail agains corruption discovered through a security state... Gimme a break with your implications. It's worse in Assassin's Creed...


Patriots get cancelled because clancy wouldn't deal?

Mrbitosql
06-19-2014, 11:23 PM
Still being worked on? Still stuck with a game I cannot play :(



Hi Guys,

we no longer need any more info:

We have identified the factors that are creating this particular issue and are currently working on a fix. We’ll keep you updated when we know more on when we’ll be able to release it.

Thanks for your understanding.

Amjo31
06-20-2014, 05:26 PM
Seriously Ubisoft?... after months since launch almost 20% of your market is screaming for a fix, and you slap us with a "working on a fix"?... 2 weeks passed, how much of a complication are you really in?...

Faulting module name: Disrupt_b64.dll

Seriously you should start sharing a means for refund!...

davis8537ac
06-21-2014, 03:01 AM
The Patch do not fix the Disrupt_b64.dll crash.

When u will fix this F*****g game?

McFreshfleisch
06-28-2014, 05:35 PM
Hey Guys!
I got a solution for you!
http://forums.ubi.com/showthread.php/892700-Watch-Dogs-Patch-(6-18-14)/page55
In my post there I've got a link from that guy who solved the issue. I'm posting that thread, because you need to read my text. Haha not because I want you to read it so someone have read it, I want you to do that because it's important!

Mr_Shade
06-28-2014, 05:45 PM
Hi Guys,

If you are still having issues with this - after the patch - please make sure support are aware:

www.support.ubi.com

McFreshfleisch
06-28-2014, 06:11 PM
Hi Guys,

If you are still having issues with this - after the patch - please make sure support are aware:

www.support.ubi.com

I'm in contact with the support since 26 days already. Right now they don't know either how to solve this. They told me to try some things, but these didn't help. Can you say me, if Ubisoft will give you your money back, if you're having really bad trouble with the game? (And you pre-ordered it)

Mr_Shade
06-28-2014, 06:57 PM
I'm not support so I would be unable to offer advice on that.

I would tell them that the suggestions did not fix the issue and they will alert the dev team.

McFreshfleisch
06-28-2014, 08:06 PM
I'm not support so I would be unable to offer advice on that.

I would tell them that the suggestions did not fix the issue and they will alert the dev team.

I know that! I thought it would be able that you know that somehow.
Well, I told them everything I know right now and what is working and what isn't working.

McFreshfleisch
07-08-2014, 05:17 PM
Okay, so now on my way to fix that Disrupt Error, I finally found a working solution.
Don't buy games from Ubisoft (They WILL be broken)
If you already bought a game, uninstall it + uPlay and play other games.

JasonChucky
07-29-2014, 08:02 PM
It's almost August and I still can't play the game because of this error. C'mon Ubisoft.