BSOD while playing Heroes Of Newerth and using windows explorer

ahbao1992 · 20 Mar 2012

Okay I've updated my Lachesis USB Optical Mouse Driver already. Removed Bitdefender.
And also what anti-virus programs do you recommend to use to protect the computer?

JMH · 20 Mar 2012

Microsoft Security Essentials is the one we recommend.

Microsoft Security Essentials - Free Antivirus for Windows

ahbao1992 · 21 Mar 2012

Ok i've installed Microsoft Security Essentials and so far I've do not had any bluescreen so far. By the way, just a question what is the SP1 for?

ahbao1992 · 21 Mar 2012

Ok Today i just received BSOD again. Here's the dmp Attachment 203823

writhziden · 22 Mar 2012

Possible out of date driver:

Code:

Lachesis	fffff880`05b8d000	fffff880`05b94680	Fri Aug 17 01:48:44 2007 (46c552dc)	00016fc6		Lachesis.sys

Lachesis.sys

Code:


Loading Dump File [D:\Kingston\BSODDmpFiles\ahbao1992\Minidump\032212-16146-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`0324ee70
Debug session time: Wed Mar 21 20:24:35.663 2012 (UTC - 6:00)
System Uptime: 0 days 0:04:36.177
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8000a190d0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030f562e to fffff80003082540

STACK_TEXT:  
fffff880`0911c4f8 fffff800`030f562e : 00000000`0000001a 00000000`00041790 fffffa80`00a190d0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0911c500 fffff800`030b56d9 : 00000000`00000000 00000000`11648fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33476
fffff880`0911c6c0 fffff800`033964d0 : fffffa80`072e0200 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0911c7e0 fffff800`033968db : 00000000`00000000 00000000`11000000 fffffa80`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0911c8a0 fffff800`03081793 : 00000000`110b9000 00000000`00000000 fffffa80`0a3af730 fffff880`0911cb10 : nt!NtUnmapViewOfSection+0x5f
fffff880`0911c8f0 fffff800`0307dd30 : fffff960`00105e3c fffff880`0911cc60 fffffa80`089ae640 00000000`000de038 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0911ca88 fffff960`00105e3c : fffff880`0911cc60 fffffa80`089ae640 00000000`000de038 fffff800`0304b3fb : nt!KiServiceLinkage
fffff880`0911ca90 fffff800`03081793 : 00000000`5c01077c 00000000`00000248 00000000`00000000 00000000`00000000 : win32k!NtGdiCreateDIBSection+0x3e4
fffff880`0911cb70 00000000`750b077a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000de018 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x750b077a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!NtGdiCreateDIBSection+3e4
fffff960`00105e3c 488bcf          mov     rcx,rdi

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  win32k!NtGdiCreateDIBSection+3e4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f2b5f64

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4

BUCKET_ID:  X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4

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

Possible causes are Memory problems... Drivers...

Update to Service Pack 1 (SP1)

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

Do the following steps to determine what is causing your crashes:

If you are overclocking any hardware, please stop.
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.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. In Windows 7:
- Click the Start Menu
- Type verifier in Search programs and files (do not hit enter)
- Right click verifier and click Run as administrator
- Put a tick in Create custom settings (for code developers) and click next
- Put a tick in Select individual settings from a full list and click next
- Set up the individual settings as in the image and click next
  Attachment 203946
- Put a tick in Select driver names from a list
- Put a tick next to all non-Microsoft drivers.
- Click Finish.
- Restart your computer.
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.