Windows 7: BSOD when using steam/valve games

monster528 · 06 Feb 2012

ive been using this brand new computer for about 7 months now

all of the system details are in my system specs, so if u need more info dont hesitate to ask

ive been playing dota 2 and at random times it freezes my computer completely. usually it doesnt even BSOD. it just freezes and i have to hard restart it and sometimes i have to restart again because it will only show a black screen

i have no idea what has been happening, but the only thing i know is that this has only happened when im in dota 2 or in one instance right after i closed it. i only managed to BSOD once so far and my computer froze about 6 times in the past 10 days

if you guys need more info ill gladly update you on anything else, i have no idea what else i can do. never had to ask for something like this so help me to help you

thank you in advance

JMH · 06 Feb 2012

> Symantec is a frequent cause of BSOD's.
I suggest you remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

> The following drivers need to be updated too...

Attachment 197046

zigzag3143 · 06 Feb 2012

Quote: Originally Posted by monster528

ive been using this brand new computer for about 7 months now

all of the system details are in my system specs, so if u need more info dont hesitate to ask

ive been playing dota 2 and at random times it freezes my computer completely. usually it doesnt even BSOD. it just freezes and i have to hard restart it and sometimes i have to restart again because it will only show a black screen

i have no idea what has been happening, but the only thing i know is that this has only happened when im in dota 2 or in one instance right after i closed it. i only managed to BSOD once so far and my computer froze about 6 times in the past 10 days

if you guys need more info ill gladly update you on anything else, i have no idea what else i can do. never had to ask for something like this so help me to help you

thank you in advance

In addition to JMH's suggestions (do them first) I would remove dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd as it is often a cause of crashes.

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files

monster528 · 07 Feb 2012

hey thanks for the replies guys. one question though, how would i update those drivers? i have their name and locations, but i don't know what programs they are linked too or how i could update them individually.

writhziden · 07 Feb 2012

Here are the links to find the drivers. Best of luck!

RtNdPt60.sys
lirsgt.sys
mv61xx.sys
spldr.sys
LHidFilt.Sys
LMouFilt.Sys
AsUpIO.sys

monster528 · 11 Feb 2012

didn't work ive gotten like 5 crashes in the past 3 hours

iit might be my hardware now, the problem is i have no idea which piece of hardware is causing the issue. i even ran some memory tests, but everything checks out. i dont know what else i can do. it seems to be happening more and more. any ideas?

Code:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 2/11/2012 4:49:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021012-21808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFA60AFFFFA60A, 0x2, 0x8, 0xFFFFA60AFFFFA60A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 2/11/2012 4:49:43 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0xFFFFA60AFFFFA60A, 0x2, 0x8, 0xFFFFA60AFFFFA60A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 2/11/2012 4:30:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021012-20280-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880045DACEE, 0xFFFFF88003CD76A8, 0xFFFFF88003CD6F00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Sat 2/11/2012 3:20:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021012-28828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x61940, 0x173A2000, 0x88900000CE2DC886, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

writhziden · 11 Feb 2012

You updated the drivers? Could you please upload the crash report again so we may take a look at the new crashes?

Those bugchecks indicate memory, drivers, or hardware conflicts as the likely cause of the crashes. It is difficult to determine which without the full report to provide troubleshooting techniques to narrow it down.

monster528 · 11 Feb 2012

yea i tried updating drivers and ive just formatted my hard drive and did a new windows 7 install, but i just crashed twice today, but no blue screen

sometimes when i start my computer it will freeze on the black screen when it says "loading asus express gate" also when it shows the windows logo

on top of which when i start my computer and try to open google chrome for the first time it ALWAYS shows a screen with an error on it that says possible hardware failure

if it shows another bsod ill post the results up again. anyone have any idea what piece of hardware is failing?

writhziden · 11 Feb 2012

Likely hard disk or memory.

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Follow the steps to do an HD Diagnostic.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.

monster528 · 12 Feb 2012

so far ive ran the disk check and hd diagnostic and have come up with nothing, from what i can see.

ill be running memtest and windows memory test later tonight, but my computer is still crashing. i dont know if it matters, but ill show you a picture of what it looks like

Windows 7: BSOD when using steam/valve games

BSOD when using steam/valve games problems?