Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD (or complete freeze) mostly when playing L4D2


25 Jan 2013   #1

Windows 7 Ultimate x64
 
 
BSOD (or complete freeze) mostly when playing L4D2

Hi,
I've been getting random BSOD during last 4 months. There's not much in common among them, lately it happens when I play Left4Dead2, but since it's the only game I play it does not say much.
Previous BSODs were sometimes related to (un)mounting SD card in card reader or external hard drive, but I can't say there is any direct connection.
Today it happened twice. First I got L4D freeze (sound froze but I was able to switch to system), I couldn't end the game, then the system became blackscreen (probably when I tried Alt+Tab to the game), then I reset the computer. It froze on BIOS screen (the graphic one), so I reset it again and an old system from the other disk was booted. The main disk was not found at all. I checked BIOS, neither there was it found. So I disconnected one of my disk (the secondary one), BIOS found my main disk, so I reconnected my secondary and both were found. Then I played L4D for like 3 hours and then - BSOD again, something with dxgmms1.sys.

I hope I will find some answers here. Thanks everyone.

My System SpecsSystem Spec
.

25 Jan 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Please post the following report before we proceed:
My System SpecsSystem Spec
26 Jan 2013   #3

Windows 7 Ultimate x64
 
 

I hope it doesn't mind it's in Czech? I see it in English in the dialog but when copied, it's Czech ...
Code:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-BHMXF-34T36-H6KD2
Windows Product Key Hash: kErx5zRsyCx+aj2PE6OKmHVOaBM=
Windows Product ID: 00426-293-5640175-85776
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {56513D97-DD9A-4A9F-9FCD-8CCF6ADA5254}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120830-0333
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\shrap\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{56513D97-DD9A-4A9F-9FCD-8CCF6ADA5254}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-H6KD2</PKey><PID>00426-293-5640175-85776</PID><PIDType>5</PIDType><SID>S-1-5-21-102527367-1805033130-1276282498</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>GA-MA785GT-UD3H</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F8</Version><SMBIOSVersion major="2" minor="4"/><Date>20100525000000.000000+000</Date></BIOS><HWID>E6B83C07018400FA</HWID><UserLCID>0405</UserLCID><SystemLCID>0405</SystemLCID><TimeZone>Střední Evropa (běžný čas)(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Verze služby SLS (Software Licensing Service): 6.1.7601.17514

Název: Windows(R) 7, Ultimate edition
Popis: Windows Operating System - Windows(R) 7, RETAIL channel
ID aktivace: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
ID aplikace: 55c92734-d682-4d71-983e-d6ec3f16059f
Rozšířené PID: 00426-00170-293-564017-00-1029-7600.0000-2522012
ID instalace: 002414174491772046331922063151127786315266500881350470
Adresa URL certifikátu procesoru:   http://go.microsoft.com/fwlink/?LinkID=88338
Adresa URL certifikátu počítače:     http://go.microsoft.com/fwlink/?LinkID=88339
Adresa URL licence k použití:             http://go.microsoft.com/fwlink/?LinkID=88341
Adresa URL certifikátu kódu Product Key: http://go.microsoft.com/fwlink/?LinkID=88340
Část kódu Product Key: H6KD2
Stav licence: Licencováno
Zbývající počet obnovení aktivačního období Windows: 4
Důvěryhodný čas: 26.1.2013 12:03:30

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 1:7:2013 13:21
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: PgAAAAIABAABAAEAAQACAAAABQABAAEAHKJeNdFQis1U8hAz4KgYiO6/EuSN74qbKs8o33KGehIiLTRwji4=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			GBT   		GBTUACPI
  FACP			GBT   		GBTUACPI
  HPET			GBT   		GBTUACPI
  MCFG			GBT   		GBTUACPI
  SSDT			PTLTD 		POWERNOW
  TAMG			GBT   		GBT   B0
My System SpecsSystem Spec
.


26 Jan 2013   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

I've called a friend to take a look at that. So, while we wait for his reply. Here are the output of your recent dump files.

As you can see, it appears to be caused by dokan.sys. *I have no idea what software it belongs to but,
I would recommend you to uninstall any related software (similar to the sys file name) that you are aware of.
Please do not use any Adobe software while troubleshooting.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {13d448, 2, 1, fffff800022f144f}

*** WARNING: Unable to verify timestamp for dokan.sys
*** ERROR: Module load completed but symbols could not be loaded for dokan.sys
Probably caused by : dokan.sys ( dokan+a4b8 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000013d448, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800022f144f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002507100
GetUlongFromAddress: unable to read from fffff800025071c0
 000000000013d448 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExTryAcquireSpinLockExclusiveAtDpcLevel+2f
fffff800`022f144f f00fb111        lock cmpxchg dword ptr [rcx],edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  lightroom.exe

TRAP_FRAME:  fffff8800db66560 -- (.trap 0xfffff8800db66560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000013d448
rdx=0000000080000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800022f144f rsp=fffff8800db666f0 rbp=000000000013d400
 r8=0000000000000000  r9=fffff88001ece180 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExTryAcquireSpinLockExclusiveAtDpcLevel+0x2f:
fffff800`022f144f f00fb111        lock cmpxchg dword ptr [rcx],edx ds:00000000`0013d448=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800022d7569 to fffff800022d7fc0

STACK_TEXT:  
fffff880`0db66418 fffff800`022d7569 : 00000000`0000000a 00000000`0013d448 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0db66420 fffff800`022d61e0 : 00000000`00000100 fffffa80`12e1b0b0 fffffa80`12e1b060 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`0db66560 fffff800`022f144f : 00000000`00000000 fffff800`0245f580 00000000`0000ff90 fffff800`022f7d6d : nt!KiPageFault+0x260
fffff880`0db666f0 fffff800`02319136 : fffffa80`11565860 00000000`00000000 fffffa80`00000258 00000000`00000801 : nt!ExTryAcquireSpinLockExclusiveAtDpcLevel+0x2f
fffff880`0db66730 fffff800`0231962d : fffffa80`0ce94080 fffff880`0db66920 00000000`00000000 fffff880`0db66810 : nt!MiComputeFlushRange+0xae
fffff880`0db667c0 fffff800`02318d3c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmFlushSection+0x49
fffff880`0db66880 fffff880`0bd874b8 : fffffa80`13335250 fffffa80`00000000 00000000`00000000 fffffa80`0ffb65b0 : nt!CcFlushCache+0x7bc
fffff880`0db66980 fffffa80`13335250 : fffffa80`00000000 00000000`00000000 fffffa80`0ffb65b0 fffffa80`11146260 : dokan+0xa4b8
fffff880`0db66988 fffffa80`00000000 : 00000000`00000000 fffffa80`0ffb65b0 fffffa80`11146260 fffffa80`12e1b168 : 0xfffffa80`13335250
fffff880`0db66990 00000000`00000000 : fffffa80`0ffb65b0 fffffa80`11146260 fffffa80`12e1b168 fffffa80`0f9ec1e0 : 0xfffffa80`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dokan+a4b8
fffff880`0bd874b8 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dokan+a4b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dokan

IMAGE_NAME:  dokan.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d2b0059

FAILURE_BUCKET_ID:  X64_0xA_dokan+a4b8

BUCKET_ID:  X64_0xA_dokan+a4b8

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

3: kd> lmvm dokan
start             end                 module name
fffff880`0bd7d000 fffff880`0bd9d000   dokan    T (no symbols)           
    Loaded symbol image file: dokan.sys
    Image path: dokan.sys
    Image name: dokan.sys
    Timestamp:        Mon Jan 10 18:49:29 2011 (4D2B0059)
    CheckSum:         000244E4
    ImageSize:        00020000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Another dump files comes with bug check 100007E which has no usual causes but looks like it's graphics related.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88007423d78, fffff8800945d688, fffff8800945cee0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88007423d78, The address that the exception occurred at
Arg3: fffff8800945d688, Exception Record Address
Arg4: fffff8800945cee0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
fffff880`07423d78 4939040a        cmp     qword ptr [r10+rcx],rax

EXCEPTION_RECORD:  fffff8800945d688 -- (.exr 0xfffff8800945d688)
ExceptionAddress: fffff88007423d78 (dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x000000000000004c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800945cee0 -- (.cxr 0xfffff8800945cee0)
rax=00000000000250d9 rbx=fffff8a004a20e50 rcx=f7fff8a00e736b28
rdx=0000000000000004 rsi=0000000000000004 rdi=0000000000000009
rip=fffff88007423d78 rsp=fffff8800945d8c8 rbp=0000000000000000
 r8=0000000000000004  r9=0000000000000009 r10=0000000000000020
r11=fffffa800ea4a3c8 r12=0000000000000001 r13=0000000000000000
r14=fffffa800fad1790 r15=00000000000000a3
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c:
fffff880`07423d78 4939040a        cmp     qword ptr [r10+rcx],rax ds:002b:f7fff8a0`0e736b48=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800024ba100
GetUlongFromAddress: unable to read from fffff800024ba1c0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
fffff880`07423d78 4939040a        cmp     qword ptr [r10+rcx],rax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800742102a to fffff88007423d78

STACK_TEXT:  
fffff880`0945d8c8 fffff880`0742102a : fffff8a0`04a20e50 fffffa80`0dbb1710 fffffa80`0ea49000 fffffa80`0fad1790 : dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c
fffff880`0945d8d0 fffff880`0741e8af : 00000000`00000000 fffffa80`0f441008 00000000`0000009a fffffa80`0d1f7020 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xda
fffff880`0945d910 fffff880`0743865d : 00000000`00000000 fffff8a0`0df4c660 fffffa80`00000000 fffffa80`0fad1790 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`0945dae0 fffff880`07438398 : fffff880`01e61f40 fffff880`07437d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0945dcd0 fffff880`07437e96 : 00000000`00000000 fffffa80`0fe95840 00000000`00000080 fffffa80`0deb3410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0945dd00 fffff800`02521e5a : 00000000`0300f301 fffffa80`0e754b50 fffffa80`0ca1cb30 fffffa80`0e754b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0945dd40 fffff800`0227bd26 : fffff880`01e5d180 fffffa80`0e754b50 fffff880`01e67fc0 00000000`2cddb000 : nt!PspSystemThreadStartup+0x5a
fffff880`0945dd80 00000000`00000000 : fffff880`0945e000 fffff880`09458000 fffff880`0945d680 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff8800945cee0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

Followup: MachineOwner
---------
Perform a fresh installation of your video card drivers. Follow this quote:
Quote:
Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:
Drivers: AMD Driver Autodetect

Please select custom install and de-select "Catalyst Control Manager - CCC" during installation.
Check for an update on your BIOS version:
Code:
Verze systému BIOS/Datum	Award Software International, Inc. F8, 25.5.2010
Video Card - Stress Test with Furmark:
warning   Warning
Video Card Stress test with Furmark can damage your GPU if temperatures are not watched.

Monitor your temps during this test with programs like HWMonitor or Speccy:Then test video memory with this app:Test for 20 passes at a minimum.

Daemon Tools:
Code:
DAEMON Tools Lite	"c:\program files (x86)\daemon tools lite\dtlite.exe" -autorun	shrap-PC\shrap	HKU\S-1-5-21-102527367-1805033130-1276282498-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
Quote:
As an alternative, many people recommend the use of Total Mounter or Magic ISO
Code:
Start Menu\Programs\Avira\AntiVir Desktop	Public:Start Menu\Programs\Avira\AntiVir Desktop	Public
Not the best security software to have, please remove with its removal tool:Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
warning   Warning
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.
Perform a System File Check:
  1. Click on the start
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow
Full tutorial here:Disk Check on your hard drive for file system errors and bad sectors on it:Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.
Let us know the results.
My System SpecsSystem Spec
26 Jan 2013   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

My friend said the mgadiag report is okay
My System SpecsSystem Spec
26 Jan 2013   #6

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by koolkat77 View Post
My friend said the mgadiag report is okay
Great. Although I am not sure I know what is it good for

Anyway, thanks for the very detailed answer. I have reinstalled the video drivers, did the FutureMark test, removed Daemon Tools and BIOS update (although it probably didn't go well. But I have the second latest BIOS available, the newer one is only 2 month younger so I don't think it matters).

I will test if it help, if I get another BSOD, I will make the rest of your suggestions. Thanks a lot again!
My System SpecsSystem Spec
26 Jan 2013   #7

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

You're welcome and look forward to hearing from you

Edit: http://dokan-dev.net/en/download/
My System SpecsSystem Spec
16 Mar 2013   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Are you still having BSOD's?
My System SpecsSystem Spec
17 Mar 2013   #9

Windows 7 Ultimate x64
 
 

Hi,
I was about to write here in a few days, I had no single BSOD since my last message. I try to keep Adobe software off when I play L4D2 and so far so good. Thank you very much again, I hope it will stay ok in the future.

Regards
shrap
My System SpecsSystem Spec
17 Mar 2013   #10

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Nice to hear... Good luck
My System SpecsSystem Spec
Reply

 BSOD (or complete freeze) mostly when playing L4D2




Thread Tools



Similar help and support threads for2: BSOD (or complete freeze) mostly when playing L4D2
Thread Forum
BSOD or Complete Freeze After ~1 Hour PC Usage BSOD Help and Support
Complete lock up (No BSOD) while playing games Gaming
Solved BSOD playing gta4 and L4D2 and every hour or so BSOD Help and Support
Complete Computer Freeze, No BSOD, Happening more frequently BSOD Help and Support
Complete Freeze up in GTA 4 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 02:05 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33