BSOD playing Mabinogi

[chaos35789]

So while playing the game, Mabinogi, there are times when my computer crashes and gives me a BSOD. I do not have any knowledge about computers or how they work so I do not why this keeps happening. This started on Saturday, January 4, 2014 and keeps persisting when I play mabinogi. I have crashed in total 5 times from playing yesterday and today. When I tested other games such as Tera, my computer does not crash for a prolong play time, so I believe it is only mabinogi, but I have no idea. By following the instructions of the BSOD thread, I have made a zip file with the dump files that were made on my computer from these crashes.

Edit: I forgot that the error message that I see is, "A clock interrupt was not received on the secondary processor."

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

[B][COLOR="red"]BugCheck 101[/COLOR][/B], {19, 0, fffff880009b3180, 4}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

fffff880`03b62030  fffff880`138d09aaUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for[B][COLOR="Red"] nvlddmkm.sys[/COLOR][/B]
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xbd9aa

Bugcheck 101's can be difficult to analyse, but I see a pattern related to your video driver. Please search here and see if there is an updated driver available:
Drivers | GeForce

If so, uninstall the existing driver/s, and install the newer driver.

 

[chaos35789]

I checked the website that you posted and updated my video driver, however, the problem is still occurring.
If anything, it looks like the crashes happen more frequently. This is the updated dump files.

 

[Golden]

Ok. I'll look at this tonight.

 

[carwiz]

It looks like your system is folding up around the disk drive. Check all the connectors--Unplug/plug a few times to clean the connectors. (Powered off, of course.) If you can, try and run Chkdsk on each partition (drive). If you can get through that, run SFC /scannow and report back any console messages.

 

[chaos35789]

I have done everything that you have told me carwiz, and both of those scans shown that there were no errors.

 

[carwiz]

Ok, that's good but there should have been three. You need to do both logical drives.

Run Memtest86+ and pay particular attention to the extended run. (7-8 passes) If you start getting errors right away, stop the test and follow the instructions for individual modules.

 

[carwiz]

By the way, did you replace the GPU recently?

Also, what motherboard and model are you using?

 

[chaos35789]

My motherboard is an Asus M5A88-M, and the only time I updated my GPU was when Golden suggested to update mine. Also, I have tested both drives, but I lost my USB and do not have any spare CDs on me to test my ram sticks, but I'll see if I can find my USB.

 

[carwiz]

The GPU is the video card not the drivers; I should have been more specific. Sorry. There's an old atipcie.sys driver running that I can't account for.

In the meantime, Uninstall Daemon Tools Lite and Pando Media Booster. What appeared to be a failing disk drive may be an application or driver corrupting memory. If the BSODs continue, we'll have to do a clean boot to isolate the problem. But still run Memtest.

 

[chaos35789]

I finally managed to do the memtest. After one pass, it shows no errors, but I'm keeping it on just incase. Also, I never updated my video card. Also, I uninstalled daemon tools and pando media but I'm still getting bsods.

 

[Golden]

After one pass, it shows no errors, but I'm keeping it on just incase.

Be sure to do a minimum of 8 consecutive passes - leave it running overnight.

 

[chaos35789]

After running 8 times, memtest showed no errors detected.

 

[chaos35789]

Update, I tested mabinogi on my laptop, and it worked perfectly so I believe that the problem may be only on my desktop.

 

[chaos35789]

I know this is an old thread, however, I am still experiencing this problem and would like some help D:

 

[carwiz]

Rerun the SF Utility with Grab All and post a fresh zip file. Be sure to let it capture all the files. This can take five minutes or more.

 

[chaos35789]

Oh, okay, here it is

 

[carwiz]

There's plenty of dumps but no report files. We need to see the current status of your system and logs as it stands today. The old reports may have changed. The last few dumps are processor timeouts (0x101) and a hardware fault (0x124) indicating a processor bus timeout. It looked like a pending disk failure before but if you've run the chkdsks and memtest64, indicators are pointing to a failing CPU.

About the only suggestion I have at this point would be to try reseating the processor and apply new heat sink compound. AMD processors don't throttle on an overheat so they'll run until they go up in smoke. Another cause could be old compound coming in contact with the motherboard and/or CPU contacts. Check around CPU socket carefully. When reinstalling the CPU, make sure all the contacts look clean but do NOT touch them with your bare hands. If you're not comfortable with this maintenance, print this response and take your system to a service center.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003717180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.
Debugging Details:
------------------
 
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  d
STACK_TEXT:  
fffff880`06990328 fffff800`02edda4a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03717180 : nt!KeBugCheckEx
fffff880`06990330 fffff800`02e906f7 : 00000000`00000000 fffff800`00000006 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`069903c0 fffff800`03400895 : fffff800`03426460 fffff880`06990570 fffff800`03426460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`069904c0 fffff800`02e83113 : fffff800`03001e80 00000000`00000001 00000000`00000001 fffff800`02e11000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`069904f0 fffff800`02e5b939 : fffff880`06990880 00000000`00000000 fffffa80`07490010 fffffa80`08909000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`06990680 fffff800`03191d4f : 00000000`00000000 fffff880`06990b60 00000000`00000000 fffff880`1379bcad : nt!KeFlushProcessWriteBuffers+0x65
fffff880`069906f0 fffff800`031923ad : 00000000`03159c20 fffff800`0317ccce 00000000`00000000 fffff800`02e85cd8 : nt!ExpQuerySystemInformation+0x13af
fffff880`06990aa0 fffff800`02e85e53 : 00000000`00000000 fffff880`06990b60 ffffffff`fffe7960 000007fe`fa7a0b00 : nt!NtQuerySystemInformation+0x4d
fffff880`06990ae0 00000000`76f6161a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0378f378 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f6161a
 
STACK_COMMAND:  kb
SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME:  Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
0: kd> !pcr fffff88003717180
Cannot get PRCB address

Forgot to add the 0x124 BC

2: kd> !errrec fffffa8008646038
===============================================================================
Common Platform Error Record @ fffffa8008646038
-------------------------------------------------------------------------------
Record Id     : 01cf11812702f3ca
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/14/2014 23:34:28
Flags         : 0x00000002 PreviousError
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80086460b8
Section       @ fffffa8008646190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f12
Processor ID  : 0x0000000000000000
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008646100
Section       @ fffffa8008646250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000000
CPU Id        : 12 0f 60 00 00 08 08 00 - 0b 22 98 1e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0  @ fffffa8008646250
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008646148
Section       @ fffffa80086462d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xb880000000020f0f

 

[chaos35789]

Ok, thanks, I'll try to find a service center to get it fixed, might take a little while.