BSOD playing dota2

[Chefaso]

Hello.

I had a few random BSOD playing this game and i had it one just one moment ago. The last BSOD before this one was almost 1 month ago probably.

Files attached.

Thanks!

 

[koolkat77]

Welcome

Is this a new computer? How many sticks of ram do you have? Your dump shows memory corruption.

BSOD Analyze

SYSTEM_SERVICE_EXCEPTION (3b) STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, memory

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

Use !analyze -v to get detailed debugging information.

[COLOR="Red"]BugCheck 3B[/COLOR], {c0000005, fffff800032e8484, fffff8800bd97ca0, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR="Red"]memory_corruption[/COLOR]

Followup: [COLOR="red"]memory_corruption[/COLOR]
---------

MODULE_NAME: [COLOR="red"]memory_corruption[/COLOR]

IMAGE_NAME:  [COLOR="red"]memory_corruption
[/COLOR]
FOLLOWUP_NAME:  [COLOR="red"]memory_corruption
[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

STACK_COMMAND:  .cxr 0xfffff8800bd97ca0 ; kb

FAILURE_BUCKET_ID:  [COLOR="red"]X64_MEMORY_CORRUPTION_ONE_BIT_LARGE[/COLOR]

BUCKET_ID:  [COLOR="red"]X64_MEMORY_CORRUPTION_ONE_BIT_LARGE[/COLOR]

Followup: [COLOR="red"]memory_corruption[/COLOR]

Start with running memtest86+ preferably overnight for 8 passes.
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Also recommend uninstalling DAEMON Tools. Its a known cause for blue screens.

Post back when done

 

[Chefaso]

Hey, thank you for fast reply.

Yes, this computer has less than a year. It's dual stick memory.

Passed the memtest86 on both sticks and got 1 red error. Also i passed the memest 86+ on the stick on the slot 1 and didnt get errors. Couldnt pass the memtest86 on the other because i have to dismantle the CPU Fan and its not an easy job D


By the way i just found that my GPU drivers were bugged. When i tried to launch the nvidia control panel i got an error, so i installed the last beta drivers on othe nvidia site and im going to unninstal daemon tools too.


Going back to the RAM, could be something related to energy problems? Since i get errors when both sticks are active... Could try to check with memtest the other stick but might be fine since its a pack of 2.


Thanks!

 

[koolkat77]

If you're having issues with the video drivers..uninstall them with using Driver Sweeper from this link |MG| Driver Fusion (Driver Sweeper) 1.2.0 Download by going to safe mode from advanced boot http://www.sevenforums.com/tutorials/666-advanced-boot-options.html.. Now reboot in normal mode and install the latest using option two from here: Drivers - Download NVIDIA Drivers

As for ram.. insert the stick that didn't show the error and see how your computer performs. If you have a friend near by or a neighbor..lend a stick of ram and see how it works on your computer. (probably the one with the 1 error has gone bad)

Let us know

 

[Chefaso]

Im gonna try to dismantle the Fan and check the other stick with memtest. But if both sticks are fine when they are not together, what should i do? :S

 

[koolkat77]

Im gonna try to dismantle the Fan and check the other stick with memtest. But if both sticks are fine when they are not together, what should i do? :S

Purchase new ram as they're really cheap these days
+Make sure they are compatible with your pc

 

[Chefaso]

No, if the stick is corrupted i will return it to the shop still have warranty. But i have to be sure that it is bad to do that. Is there any way to test each stick without extract? The problem with the fan is that is really big and i cant extract the memory on the slot 1 without dismantle the fan.

Thanks for replys!

 

[koolkat77]

No, if the stick is corrupted i will return it to the shop still have warranty. But i have to be sure that it is bad to do that. Is there any way to test each stick without extract? The problem with the fan is that is really big and i cant extract the memory on the slot 1 without dismantle the fan.

Thanks for replys!

OK, good idea. Sorry I didn't ask if it had its warranty.
Doesn't seem like you have an option without dismantling the fan as you say its big.

 

[Chefaso]

Just found a video guide of how to dismantle the fan so maybe i will try to check the other stick if i keep getting the BSOD related to memory.

Thanks for the help!

 

[koolkat77]

You're welcome
Keep us posted!

 

[Chefaso]

Almost a week since the BSOD.

I just installad new nvidia drivers and deleted daemon tools, no more BSOD.

Gonna keep the thread open, maybe a wild BSOD will appear on my screen.

 

[koolkat77]

Thanks for the update
Do keep us posted

 

[koolkat77]

So did you get any BSoD after your last post?

 

[Chefaso]

All working fine. Should we close this?

 

[koolkat77]

All working fine. Should we close this?

Yes

If you have problems you can come back here

 

[Chefaso]

Thanks for the help

 

[koolkat77]

You're welcome

 

[tEhfO]

Oh ****, u think it was DAEMON TOOLS??????????? :|||||||||
I'm having a lot of BSOD while playing Dota 2, but it's totally random.
I'll uninstall it!

 

[Chefaso]

Hello!

I'm back again with more BSOD, i was using steam friends interface and paff, BSOD

More than 3 months since the last 1 i get, maybe its just random but you never know, i let you the files.

Thanks for the help!

 

[koolkat77]

Hello!

I'm back again with more BSOD, i was using steam friends interface and paff, BSOD

More than 3 months since the last 1 i get, maybe its just random but you never know, i let you the files.

Thanks for the help!

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8001eca590, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8001eca590
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  LoLLauncher.ex

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003302b50 to fffff80003296fc0

STACK_TEXT:  
fffff880`0e6dc818 fffff800`03302b50 : 00000000`0000001a 00000000`00041790 fffffa80`01eca590 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0e6dc820 fffff800`0328381f : fffffa80`00000000 00000000`0aa3ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0e6dc9e0 fffff800`03296253 : ffffffff`ffffffff 00000000`0008e320 00000000`0008e318 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0e6dcae0 00000000`773314fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773314fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35054
fffff800`03302b50 cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

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

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.