Blue screen

[r2u]

Hello :d

i have bleu screen


thanks for all :d

 

[r2u]

hello

 

[mickey megabyte]

hi

you can't expect a post with a detailed technical reply in 20 minutes on a free forum!

have a little patience, someone will read your post soon.

sorry i can't help, i'm a bsod noob.

 

[writhziden]

Why did you start a new thread? Please continue your thread in http://www.sevenforums.com/crashes-debugging/208393-bugcheck-code-0x1000008e.html and upload the new blue screen crashes there.

Nevermind, my apologies. This is for a different system. I will post my analysis here of the new system.

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\r2u\Windows_NT6_BSOD_jcgriff2\011512-30640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.21847.x86fre.win7sp1_ldr.111025-1501
Machine Name:
Kernel base = 0x8283e000 PsLoadedModuleList = 0x8297e230
Debug session time: Sun Jan 15 06:18:49.675 2012 (UTC - 7:00)
System Uptime: 0 days 0:32:04.837
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00000403, The subtype of the bugcheck.
Arg2: c00052a4
Arg3: 2ee0c867
Arg4: c00052a0

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

*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS

BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 828c6c5a to 8291033c

STACK_TEXT:  
a314b91c 828c6c5a 0000001a 00000403 c00052a4 nt!KeBugCheckEx+0x1e
a314b9f4 828c6582 c00052a4 c00052b4 8456d978 nt!MiDeletePteRun+0x52f
a314bad8 828bb81f 8456d978 014adfff 8515ba38 nt!MiDeleteVirtualAddresses+0x33b
a314bb70 8e91c3d2 ffffffff a314bcd8 a314bce4 nt!NtFreeVirtualMemory+0x60b
WARNING: Stack unwind information not available. Following frames may be wrong.
a314bbb4 8287382a ffffffff a314bcd8 a314bce4 aswSP+0xa3d2
a314bbb4 828717e1 ffffffff a314bcd8 a314bce4 nt!KiFastCallEntry+0x12a
a314bc3c 820ebb7c ffffffff a314bcd8 a314bce4 nt!ZwFreeVirtualMemory+0x11
a314bcdc 820eb8da 00000000 00000000 00000000 win32k!SURFACE::bDeleteSurface+0x291
a314bcf0 820d5ea6 00000000 00000000 ff810630 win32k!SURFREF::bDeleteSurface+0x14
a314bd04 820d11dd 90051286 857729b0 90051286 win32k!bDeleteSurface+0x20
a314bd18 87ef5d74 90051286 0020e618 a314bd34 win32k!NtGdiDeleteObjectApp+0x7f
a314bd28 8287382a 90051286 0020e62c 77db7134 aswSnx+0x16d74
a314bd28 77db7134 90051286 0020e62c 77db7134 nt!KiFastCallEntry+0x12a
0020e62c 00000000 00000000 00000000 00000000 0x77db7134


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswSP+a3d2
8e91c3d2 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  aswSP+a3d2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4e6684a0

FAILURE_BUCKET_ID:  0x1a_403_aswSP+a3d2

BUCKET_ID:  0x1a_403_aswSP+a3d2

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

Your new blue screen crash was due to memory management, which could be the result of a device driver or memory. It was blamed on Avast. Use the Avast Uninstall Utility to uninstall Avast and replace it with Microsoft Security Essentials to run alongside Windows firewall.

Please start by updating the following drivers. Use Driver Reference Table - sysnative.com - MVP,
Drivers and Downloads,
http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html,
http://www.sevenforums.com/tutorials/99402-driver-install-add-hardware-wizard.html,
and http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html as references for finding drivers, finding driver manufacturers, updating driver procedures, installation procedures through the hardware wizard, and installation procedures through device manager respectively.

ac97via	8e992000	8e9b1000	Mon Nov 22 13:29:55 2004 (41a24c43)	0001a0ad		ac97via.sys
AN983	8ef46000	8ef4f880	Wed Jan 12 18:27:59 2005 (41e5ce9f)	0000b28c		AN983.sys
nv4_disp	8a000000	8a3ed380	Thu Jan 27 01:42:39 2005 (41f8a97f)	003ed569		nv4_disp.dll
nv4_mini	8ec06000	8ef45e40	Thu Jan 27 01:47:35 2005 (41f8aaa7)	0034a22c		nv4_mini.sys
btnetdrv	8eaeb000	8eaed9e0	Sat Apr 30 00:48:57 2005 (42732a59)	0000672b		btnetdrv.sys
blueletaudio	8ec00000	8ec05000	Tue May 31 01:40:18 2005 (429c14e2)	0000a349		blueletaudio.sys