Hello all. To start my name is Chris and I'm kinda a computer noob =p. Been having some pretty constant crashing lately during almost anything I do. Gaming or just surfing the net can produce a crash. It will error to a blue screen so I went and got the dump information. I could really use any help diagnosing this problem thats available. Here is the dump info.



Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071107-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available




Symbol search path is: *** Invalid ***
*************************************************************************** *
* Symbol loading may be 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 is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> 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 be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jul 11 13:12:58.515 2007 (GMT-5)
System Uptime: 0 days 0:08:05.105
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> 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 be loaded for ntoskrnl.exe
Loading Kernel Symbols
........................................................................... ................................................
Loading User Symbols
Loading unloaded module list
..........
Unable to load image windev-43d4-4b80.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for windev-43d4-4b80.sys
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8053aa92, b064dc98, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : windev-43d4-4b80.sys ( windev_43d4_4b80+64b )





I dont really know how to pick out what information is actually what you need but thats the whole thing. Kinda in a rush right now for work so I'll be back and add in some more information later.

The computer was built a year or two ago so all the specs arent too fresh on my mind if you need those. I'll try looking some up in the mean time.

Thanks for the help guys.

Probably (was) caused by : windev-43d4-4b80.sys. This is an infection. Go HERE.