I'm not sure what to say about your BSODs. In my opinion, it's not something too serious (Based on what you've described and what I saw from the DMP analysis). The stop code 8E with exception code c000005 make me think that this can indicates that a memory access violation occurred.
Quote:
STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
Make sure you have
enough disk space. Besides that, Let's test your Ram: Download a copy of
Memtest86 and burn the ISO to a CD using
Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
What antivirus are you using?
BUGCHECK SUMMARY:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.769\080910-34850-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x81e42000 PsLoadedModuleList = 0x81f8a810
Debug session time: Mon Aug 9 20:57:33.849 2010 (UTC + 7:00)
System Uptime: 0 days 0:37:10.614
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 91f1c98f, b16c4a6c, 0}
Probably caused by : win32k.sys ( win32k!UnsetRedirectedWindow+28 )
Followup: MachineOwner
--------- Regard,
Tuan