Heresy 1st MRB

USA (68) England (42) Norway (46) Sweden (54) Germany (27)

Ugh, Mr. Bean...

USA (66) Mexico (2) England (42) Norway (47) Sweden (55) Germany (25)

Did you get a chance to call them yet? I'm eager to know since it makes me mad since they did not fix it the first time for you!

I am going to close the ticket now, but if the problem happens again we can re-open this thread or reference it.

Adding on to what Hess said, we had tried various things with your config, applications, and HUD. What is the current state of all of these things? Is it back to the way that you had it before?

USA (65) Mexico (3) England (41) Norway (47) Sweden (56) Germany (25)

This make me laugh so hard this morning... pure greatness!

USA (62) Mexico (8) England (40) Norway (48) Sweden (57) Finland (1) Germany (23)

USA (60) Mexico (8) England (40) Norway (48) Sweden (56) Finland (4) Germany (23)

USA (59) Mexico (8) England (40) Norway (48) Sweden (57) Finland (4) Germany (23)

Happy birthday!

Have you seen the garbaled screen since you made the change to the SATA connections? What is the red text that you are seeing?

Are you getting that screen every time you load Palermo connected to a remote server, or just sometimes?

Done, you should see the coupon trade/gift in your Steam inbox now

Bump... If anyone wants these coupons that I have left just let me know.

Japan (2) USA (57) Mexico (10) England (40) Norway (47) Sweden (56) Finland (4) Germany (23)

Happy Birthday!

Japan (4) USA (56) Mexico (11) England (39) Norway (47) Sweden (55) Finland (5) Germany (22)

The last dump was pointing to your disk subsystem. After you changed your SATA setup you have been booting okay now right? Do you still have that issue when loading the Palermo map? Does it happen when you load Palermo locally (i.e. host it yourself)? Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\temp\011114-23400-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv*c:\windows\Symbols*c:\symbols*C:\WINDOWS\Symbols\Itanium*C:\WINDOWS\Symbols_x86_Checked*c:\windows\symbols\*c:\msftpdbs*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`034926d0 Debug session time: Sat Jan 11 09:13:53.824 2014 (UTC - 7:00) System Uptime: 0 days 20:29:59.839 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7A, {20, ffffffffc000009d, fffffa80088707c8, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+50080 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_DATA_INPAGE_ERROR (7a) The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error. Also see KERNEL_STACK_INPAGE_ERROR. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, it means the disk subsystem has experienced a failure. If the error status is 0xC000009A, then it means the request failed because a filesystem failed to make forward progress. Arguments: Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc000009d, error status (normally i/o status code) Arg3: fffffa80088707c8, current process (virtual address for lock type 3, or PTE) Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED DISK_HARDWARE_ERROR: There was error with disk hardware BUGCHECK_STR: 0x7a_c000009d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from fffff800032b8c8c to fffff800032c4bc0 STACK_TEXT: fffff880`033d9818 fffff800`032b8c8c : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`088707c8 : nt!KeBugCheckEx fffff880`033d9820 fffff800`032adb97 : fffffa80`08870760 00000000`c000009d 00000000`00000000 fffffa80`088707f8 : nt! ?? ::FNODOBFM::`string'+0x50080 fffff880`033d98e0 fffff800`032b75f7 : fffffa80`05b7e660 fffffa80`05b7e6b0 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57 fffff880`033d9910 fffff800`032ba7fd : fffffa80`05b7e660 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7 fffff880`033d9990 fffff800`032c70ea : 00000000`00000000 00000000`00000000 00000103`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x3dd fffff880`033d9a20 fffff800`0325ba5f : fffffa80`00000002 fffff880`033d9d20 fffffa80`00000001 00000000`00000013 : nt!KeWaitForMultipleObjects+0x272 fffff880`033d9ce0 fffff800`035612ea : fffffa80`05b7e660 0df90df9`38bc38bc 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf fffff880`033d9d40 fffff800`032b58e6 : fffff880`009b2180 fffffa80`05b7e660 fffff880`009bd0c0 cfa0cfa0`ab5aab5a : nt!PspSystemThreadStartup+0x5a fffff880`033d9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+50080 fffff800`032b8c8c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+50080 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035 FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+50080 BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+50080 Followup: MachineOwner ---------

You should see the coupon in your inbox now.

Tell them to "Clamp it down and FIX IT!" https://screen.yahoo.com/thursday-fix-000000027.html

It does look pretty cool. Would be entertaining to have a group of people playing.

No problem! You should see the trade offer now in your Steam inbox.