random BSOD, possibly related with installation failure of CS GO

[ethyl]

I have installed a Xeon X5492 (modded) on my 775 socket mainboard using a modded bios. When booted first time on windows I managed to play CS GO for one minute and then I was kicked out of the game with a message like .pak (or something like that) file does not match server's. Since then I have tried EVERYTHING and nothing works. Formatted multiple times, getting latest drivers. I deleted steam and cs go and now everytime steam is installing cs go I get the message corrupted update files. I have no clue what is going on. I do not have problems with other programs or games. Just with cs go. I occasionaly get a BSOD since when I installed the new CPU and I am trying to find out if this is related to my problem. If anyone can help as I am desperate.

I have attached all the files

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff780c0000000
Arg3: 000000000000df06
Arg4: 0000ff040001fe0c

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 7601.19045.amd64fre.win7sp1_gdr.151019-1254

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_VERSION: System Version

BIOS_VENDOR: Phoenix Technologies, LTD

BIOS_VERSION: ASUS STRIKER II EXTREME ACPI BIOS Revision 1402

BIOS_DATE: 01/28/2010

BASEBOARD_MANUFACTURER: ASUSTeK Computer INC.

BASEBOARD_PRODUCT: STRIKER II EXTREME

BASEBOARD_VERSION: 1.XX

DUMP_TYPE: 2

BUGCHECK_P1: 5003

BUGCHECK_P2: fffff780c0000000

BUGCHECK_P3: df06

BUGCHECK_P4: ff040001fe0c

BUGCHECK_STR: 0x1a_5003

CPU_COUNT: 4

CPU_MHZ: d48

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 17

CPU_STEPPING: a

CPU_MICROCODE: 6,17,a,0 (F,M,S,R) SIG: A07'00000000 (cache) A07'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: ETHYL-PC

ANALYSIS_SESSION_TIME: 12-27-2015 19:45:00.0286

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from fffff80002aefb8f to fffff80002a85c40

STACK_TEXT:
fffff880`03164678 fffff800`02aefb8f : 00000000`0000001a 00000000`00005003 fffff780`c0000000 00000000`0000df06 : nt!KeBugCheckEx
fffff880`03164680 fffff800`02a9be53 : fffff6fc`c016a998 00000000`00000001 fffffa80`0000000d fffffa80`006a1250 : nt! ?? ::FNODOBFM::`string'+0x29969
fffff880`031647f0 fffff800`02a746fe : fffff980`2d533000 00000000`0030d000 fffffa80`00000000 fffffa80`03945b01 : nt!MmCheckCachedPageStates+0x4a3
fffff880`031649a0 fffff800`02ceb121 : 00000000`00000000 00000000`c00000d8 fffffa80`03945b10 fffffa80`011f9780 : nt!CcFetchDataForRead+0x10e
fffff880`03164a00 fffff800`02a327f8 : fffffa80`03945b10 00000000`06cf3000 00000000`0000d000 fffffa80`00cc0170 : nt!CcMapAndCopyFromCache+0xc5
fffff880`03164a90 fffff800`02acb4ee : fffffa80`03945b10 fffff880`00000000 fffffa80`00000005 fffffa80`01116a01 : nt!CcPerformReadAhead+0x3b8
fffff880`03164bc0 fffff800`02a8fb69 : fffffa80`00ccbc70 fffff800`02d7f401 fffff800`02c92990 00000000`00000002 : nt!CcWorkerThread+0x21e
fffff880`03164c70 fffff800`02d1fb86 : 00000000`00000000 fffffa80`00cc0170 00000000`00000080 fffffa80`00c9b040 : nt!ExpWorkerThread+0x111
fffff880`03164d00 fffff800`02a770e6 : fffff880`02f63180 fffffa80`00cc0170 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03164d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 3c0536671cd9b0424aeba918d07ac08393917f8c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 156a13183bc421304fa11f867ae38fdbb20256c3

THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+29969
fffff800`02aefb8f cc int 3

FAULT_INSTR_CODE: cf8b4ccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+29969

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5625815c

IMAGE_VERSION: 6.1.7601.19045

FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29969

BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29969

PRIMARY_PROBLEM_CLASS: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29969

TARGET_TIME: 2015-12-27T16:42:41.000Z

OSBUILD: 7601

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2015-10-20 02:48:44

BUILDDATESTAMP_STR: 151019-1254

BUILDLAB_STR: win7sp1_gdr

BUILDOSVER_STR: 6.1.7601.19045.amd64fre.win7sp1_gdr.151019-1254

ANALYSIS_SESSION_ELAPSED_TIME: 453

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1a_5003_nt!_??_::fnodobfm::_string_+29969

FAILURE_ID_HASH: {8ef6be9c-005d-e4e1-947e-b7f0fc96af0f}

Followup: MachineOwner

 

[BorisTheAnimal]

Hi ethyl and welcome to sevenforums, I hope you'll enjoy your stay here!

I would suggest that you run memtest, at least 8 runs and post back the results:

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Cheers!
Boris

 

[ethyl]

I have run Memtest for 8 hours straight without any errors coming up

 

[BorisTheAnimal]

Alright well I would recommend you updating your system specs because that will help us solve your problem.

Please use this:

http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

Cheers!
Boris!

 

[Laith]

Did you run MemTest86 or MemTest86+?

 

[axe0]

How many passes were completed?

 

[ethyl]

I have updated my system specs. Do not get confused by the 1gb ram. I have 3 ddr3 dimms of 1gb I have onboard just 1 of them because I was running tests. I get the BSOD and the CS GO problems even with just one dimm. I have used memtest86 for the testing and each pass was around 15 minutes so I guessed my computer have run around 16 passes straight

 

[Laith]

You MUST use MemTest86+ for at least 8 passes.

 

[Layback Bear]

8 continues test. No stopping and starting.

 

[ethyl]

I will do that and post back although I do not think that it is RAM problem

 

[axe0]

A memory management is usually a memory problem, MemTest86+ is better in finding errors on DDR3 then MemTest86.
However, a memory management dump usually doesn't flag any drivers. If the test doesn't give any errors then you should run driver verifier

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[ethyl]

memetest86+ does not boot from usb. It says UI or Kernel configuration directive found or something like that

 

[axe0]

Please be more specific about the error, make a clear photo of it.

 

[ethyl]

It is very common error as i see it on google "SYSLINUX: No DEFAULT or UI configuration directive found"

 

[axe0]

From the solutions I found it is a faulty USB/CD problem.

 

[ethyl]

I was using the same usb with memtest 86 and it was working fine

 

[Laith]

Try to burn MemTest86+ to a DVD.

 

[ethyl]

I fixed it. I run memtest86+ 20 passes no errors!! So what now

 

[ethyl]

Also I am running driver verifier and i have zero unsigned drivers. All are signed from microsoft

 

[axe0]

That shouldn't be possible with installed software like Nvidia and Paragon..