WIN7 blue Screen Code 1000008E solution

Win7 Blue Screen code 1000008E solution
The problem reflects: Win7 computer in browsing the web when the blue screen, the use of the browser is IE 11,win7 blue screen code 008e, with a blue log information, please help solve.

The blue screen log is as follows:

The code is as follows:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [c:documents and Settingsadministrator desktop 71614-18203-01.dmp]

Mini Kernel Dump file:only registers and stack trace are available

Symbol Search Path is: * * * Invalid * * *

*********************************************************************

* symbol loading may unreliable without a symbol search path. *

* use. Symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use. Reload to refresh symbol locations. *

*************************************************************

Executable Search Path is:

*********************************************************************

* Symbols can not be loaded because symbol path isn't initialized. *

* *

* The Symbol Path can be set by: *

* Using the _NT_SYMBOL_PATH environment variable. *

* Using the-y argument when starting the debugger. *

* using. Sympath and. sympath+ *

*********************************************************************

Unable to load image Ntoskrnl.exe, Win32 error 0N2

Warning:unable to verify timestamp for Ntoskrnl.exe

Error:module load completed but symbols could not is loaded for Ntoskrnl.exe

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) free x86 compatible

Product:winnt, Suite:terminalserver Singleuserts

Machine Name:

Kernel base = 0x83e15000 PsLoadedModuleList = 0x83f5e5b0

Debug session time:wed June 02:24:00.417 2014 (gmt+8)

System uptime:0 days 4:08:35.290

*****************************************************************

* Symbols can not be loaded because symbol path isn't initialized. *

* *

* The Symbol Path can be set by: *

* Using the _NT_SYMBOL_PATH environment variable. *

* Using the-y argument when starting the debugger. *

* using. Sympath and. sympath+ *

*********************************************************************

Unable to load image Ntoskrnl.exe, Win32 error 0N2

Warning:unable to verify timestamp for Ntoskrnl.exe

Error:module load completed but symbols could not is loaded for Ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

................

Loading User Symbols

Loading unloaded Module List

............

Unable to load image Fltmgr.sys, Win32 error 0N2

Warning:unable to verify timestamp for Fltmgr.sys

Error:module load completed but symbols could not is loaded for Fltmgr.sys

Bugcheck Analysis * * * *!analyze-v to get detailed debugging Informa tion.

Bugcheck 1000008E, {c0000005, 89bca885, 9edd2714, 0}

Warning:unable to verify timestamp for Qutmdrv.sys

Error:module load completed but symbols could not is loaded for Qutmdrv.sys

Warning:unable to verify timestamp for Qqprotect.sys

Error:module load completed but symbols could not is loaded for Qqprotect.sys

Kernel symbols are wrong. Please fix symbols.

*****************************************************************

*** ***

*** ***

Your Debugger is not using the correct symbols * * *

*** ***

In order for this command to work properly, your symbol path * * *

Must point to. pdb files, have full type information. ***

*** ***

Certain. pdb files (such as the public OS symbols) does not * * * * * *

contain the required information. Contacts the group that * * *

Provided you have these symbols if your need this command to * * *

Work. ***

*** ***

Type REFERENCED:NT!_KPRCB * * *

*** ***

******************************************************************

Your Debugger is not using the correct symbols * * *

*** ***

In order for this command to work properly, your symbol path * * *

Must point to. pdb files, have full type information. ***

*** ***

Certain. pdb files (such as the public OS symbols) does not * * * * * *

contain the required information. Contacts the group that * * *

Provided you have these symbols if your need this command to * * *

Work. ***

*** ***

Type REFERENCED:NT!_KPRCB * * *

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

Your Debugger is not using the correct symbols * * *

*** ***

In order for this command to work properly, your symbol path * * *

Must point to. pdb files, have full type information. ***

*** ***

Certain. pdb files (such as the public OS symbols) does not * * * * * *

contain the required information. Contacts the group that * * *

Provided you have these symbols if your need this command to * * *

Work. ***

*** ***

Type REFERENCED:NT!_KPRCB * * *

*** ***

*************************************************************************

*********************************************************************

* Symbols can not be loaded because symbol path isn't initialized. *

* *

* The Symbol Path can be set by: *

* Using the _NT_SYMBOL_PATH environment variable. *

* Using the-y argument when starting the debugger. *

* using. Sympath and. sympath+ *

*********************************************************************

*********************************************************************

* Symbols can not be loaded because symbol path isn't initialized. *

* *

* The Symbol Path can be set by: *

* Using the _NT_SYMBOL_PATH environment variable. *

* Using the-y argument when starting the debugger. *

* using. Sympath and. sympath+ *

*********************************************************************

Probably caused By:qutmdrv.sys (qutmdrv+cd12)

Followup:machineowner

---------

"Edit analysis and suggestions" after viewing the file to learn Qutmdrv.sys caused by.