Screen Freezes, Sound Skips into BSOD while Playing League of Legends

[Hogemister]

Hi,
I'm having a serious problem more and more frequently mostly while playing League of Legends my Laptop crashes with BSODs.

Also sometimes when the crashes happen the screen distorts and really loud screeching sound occurs (These crashes don't get recorded i'm just mentioning maybe it means something)

I've Reinstalled Windows a few times in the past and that usually gives me a few weeks to a couple months of Bliss before the BSODs become more frequent.

View attachment 276622

Please help
- Maxx

 

[koolkat77]

Do you have BSOD's only while playing LOL or other games as well?
Is your laptop under warranty?

I believe there is a problem with your Graphic card in particular.

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7
​

Your Antivirus software is basically whats just needed there.

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors​

Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:

Piriform - Speccy

CPUID - HWMonitor​

Upload a screen shot of the Summary Tab of Speccy.

• For how to upload a screenshot or file, read here

Problem Drivers:

You need to either update these drivers to latest version available or uninstall them and their software completely.

sncduvc.SYS Mon Dec 29 15:14:26 2008 (495894F2)
Suyin USB 2.0 Webcam driver
Driver Reference Table - sncduvc.SYS

snp2uvc.sys Wed May 20 14:11:05 2009 (4A13BB19)
Suyin USB 2.0 Webcam driver
Driver Reference Table - snp2uvc.sys

iaStor.sys Fri Jun 5 07:53:40 2009 (4A287AA4)
Intel Storage drivers
Driver Reference Table - iaStor.sys

enecir.sys Mon Jun 29 08:17:30 2009
ENE Consumer IR Driver for eHome
Driver Reference Table - enecir.sys

Make scans with -

TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US

Online Virus Scanner Eset​

Bugcheck

[FONT="Lucida Console"]Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Jul 16 07:23:07.593 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:30.717
BugCheck 4A, {76dc167a, 2, 0, fffff88007101ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  RAISED_IRQL_FAULT
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Jul 16 07:01:06.267 2013 (UTC + 6:00)
System Uptime: 0 days 0:57:10.267
BugCheck 3B, {c0000005, fffff88004453580, fffff88007ff1f40, 0}
Probably caused by : netbt.sys ( netbt+1580 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Jul 16 05:52:55.738 2013 (UTC + 6:00)
System Uptime: 0 days 0:10:11.737
BugCheck 3B, {c0000005, fffff800030f3cbe, fffff880067e08c0, 0}
Probably caused by : ntkrnlmp.exe ( nt!SepMandatoryIntegrityCheck+2ae )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Jul 16 04:31:41.126 2013 (UTC + 6:00)
System Uptime: 0 days 0:14:43.125
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sun Jul 14 22:31:55.919 2013 (UTC + 6:00)
System Uptime: 0 days 1:32:17.707
BugCheck 1E, {ffffffffc0000005, fffff88009974c60, 0, 0}
Probably caused by : partmgr.sys ( partmgr+10af )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  LolClient.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sun Jul 14 08:35:55.595 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:27.594
BugCheck 50, {ffffdd000c1d28e2, 0, fffff88004d06027, 7}
Probably caused by : hardware ( dxgkrnl!DXGPRESENT::GrowRectList+13 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[Hogemister]

My BSOD's primarily occur during League, i haven't played any other video games on my laptop in a while so idk if it's only this specific game however They have happened when streaming videos and rarely as soon as i sign into my desktop.

after the Clean Startup in Windows seven i experienced a Blue screen, it took longer to crash that usual but still crashed.
View attachment 276770

SFC and disk check ran fine i don't know where to post the results of my Risk check but i have the SFC file
View attachment 276769

Picture of Speccy
View attachment 276771

The Drivers I don't believe I uninstalled them correctly, i couldn't find the correct files so i kind of just went into my driver folder and deleted that specific item

TDSSKiller came back with one threat so i quarantined it
Eset came back with that one file in Quarantine so i deleted it

It was a variant of a windows file IDriverT

Thanks for taking the time to help koolkat77 it's very appreciated
-Maxx

 

[koolkat77]

Same video memory errors. Is the laptop under warranty?

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8027413e98, 1, fffff8800559a12b, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8027413e98, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800559a12b, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003304100
GetUlongFromAddress: unable to read from fffff800033041c0
 fffffa8027413e98 Nonpaged pool

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`0559a12b 48894108        mov     qword ptr [rcx+8],rax

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009693700 -- (.trap 0xfffff88009693700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80076948b0 rbx=0000000000000000 rcx=fffffa8027413e90
rdx=fffff8a00fccc710 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800559a12b rsp=fffff88009693890 rbp=0000000000000000
 r8=fffffa800a53fbe0  r9=0000000000000001 r10=0000000000000000
r11=fffffa800766f3c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3:
fffff880`0559a12b 48894108        mov     qword ptr [rcx+8],rax ds:fffffa80`27413e98=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800031495d4 to fffff800030ccc00

STACK_TEXT:  
fffff880`09693598 fffff800`031495d4 : 00000000`00000050 fffffa80`27413e98 00000000`00000001 fffff880`09693700 : nt!KeBugCheckEx
fffff880`096935a0 fffff800`030cad2e : 00000000`00000001 fffffa80`27413e98 00000000`00000000 fffff8a0`18035a60 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`09693700 fffff880`0559a12b : fffff8a0`17cc2e50 fffffa80`073ca890 fffffa80`0766e000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`09693890 fffff880`055979d3 : 00000000`00000000 fffffa80`097142a8 00000000`0000012b fffffa80`0ab56800 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3
fffff880`096938d0 fffff880`055b17d9 : 00000000`00000000 fffff8a0`163525c0 fffffa80`00000000 fffffa80`0aa15950 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`09693aa0 fffff880`055b1514 : fffff800`00b96080 fffff880`055b0f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`09693c90 fffff880`055b1012 : 00000000`00000000 fffffa80`09600d50 00000000`00000080 fffffa80`086b9410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`09693cc0 fffff800`0336aede : 00000000`00000000 fffffa80`08b9cb50 fffffa80`06a209e0 fffffa80`00000001 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`09693d00 fffff800`030bd906 : fffff800`03247e80 fffffa80`08b9cb50 fffff800`03255cc0 fffffa80`09362620 : nt!PspSystemThreadStartup+0x5a
fffff880`09693d40 00000000`00000000 : fffff880`09694000 fffff880`0968e000 fffff880`09693640 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`0559a12b 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

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

 

[Hogemister]

Unfortunately no,
Ibuypower offer repairs but you need a serial number that was only included in the original email they sent you after purchasing a system from them.

and the only problem with that is this was a gift and the family member who bought me the laptop no longer has that email.

 

[Arc]

We need to know two more things.

• Is it BSODing at any other usage?
• If it is during games, is it BSODing with any other games?

Other than those info, it will be hard to draw a conclusion.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Also try to take this test: https://simtk.org/project/xml/downloads.xml?group_id=385

Let us know th results of the tests, too.

 

[Hogemister]

Hey Arc okay

today my laptop is just not working im messaging from my phone.

I recieve BSODs from acessing the internet or even running Microsoft Security Essentials and various other video games (Smite/ WoW/ SWtoR).

everytime I restart my laptop it wants to run the Disk checker and the past 4 times it has ran it found a corrupt file and BSOD follows it immediatley.

I don't know what to do, It's too unstable to even turn on.

Also thank you 2 for responding to my post.

:Edit:
CHKDSK ran 5-7 times before completing would you like me to upload the Mini dump files

For the Furmark test, i got a BSOD on first try and is there a way to see my logged results after i choose to quit the test my Temperature leveled out at 67 degrees Celsius after 5 mins when i toggled the Fuzzy rendering it dropped to 63 and leveled out

and for the memtest i can't seem to download the test from that link i have another version on a flash drive memtest86+ could i use that one

:Edit:

Memtest86+ has just stopped at 4:43 because it found an error test at 7% pass at 100% errors reading 35000 and counting.

 

[Arc]

It appears to be a lot of mess, but simply failing may cause all of those.

As you are getting errors in test, stop testing. Go to part 3 of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

It is time consuming, but good to have this test.

If you cannot, Simply RMA the RAM, or buy a new kit.

Let us know how it is running on the replaced RAM.

 

[Hogemister]

hey Arc

looks like I have a motherboard issue both RAM failed in the same slot but were able to run 7+ passes in the 2nd

is this fixable?
thank you for the assistance this far
- Maxx

 

[Arc]

Hello Hogemister,

Sorry to say, but the only feasible fix here is to change the motherboard. And here appears the most important question ... is it a OEM license that you are using?

If it is OEM license, get the laptop to Compal servicing center .... as the OEM license is tagged to the motherboard, it is better that the vendor replace the motherboard themselves. So they can take care of the license issue properly.

 

[Hogemister]

I'm not sure
how would I know

 

[Arc]

I'm not sure
how would I know

Press Windows key (at the left of the left alter key) and Pause/Break key (should be at the top row of the num slot of the keyboard) simultaneously. The window will open, the location in the address bar is "Control Panel > All Control Panel Items > System " Scroll down to the window. At teh bottom line, there is the Product ID.

Dont let us know the product ID, but observe it the ID contains the OEM word in the second part of the ID.

 

[Hogemister]

Okay yea it contains OEM

thank you very much for all your help Arc

 

[Arc]

Okay yea it contains OEM

thank you very much for all your help Arc

But I am not happy. I wished it would be retail, which would be better for you.

Take the computer to a Compal servicing center only. Ask them to manage the motherboard replacement in a way that your OEM license does not die.

Let us know how it goes.

And, if you face any problem while clean installing windows after the motherboard replacement, inform us. Our activation experts will try their best to help you.

All the best.

 

[Hogemister]

where would someone find a compal servicing center could that be any computer repair place only with a certain certificate from Compal or are they specific locations

Edit
I found a computer shop and they told me my OEM licesnse died when my warranty with Ibuypower was over.

 

[Arc]

where would someone find a compal servicing center could that be any computer repair place only with a certain certificate from Compal or are they specific locations

Edit
I found a computer shop and they told me my OEM licesnse died when my warranty with Ibuypower was over.

Technically true.

But NoelDP will be able to guide you the most desired action. I am requesting him to have a look.

For now, you dont use the failing DIMM slot, Use RAMs in the other slot/slots.

 

[NoelDP]

ALL commercial (not Volume) licenses for Windows are perpetual - they NEVER run out.

Your system appears to be based on a OEM System Builder license - you should have a COA sticker on the case with the product Key on it. The warranty and software support is up to the manufacturer, but they are obliged to support the OS for at least 90 days after purchase.

A clean install with a OEM System Builder disk is almost identical to one using a Retail disk - there is no functional difference, merely a marginal difference in one of the licensing files.