Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD 10 times a Day


  • Please log in to reply
No replies to this topic

#1 JaceX

JaceX

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:46 PM

Posted 11 June 2009 - 05:49 PM

Build

Intel Wolfsdale E8400 @ 3.00 ghz processor
(Intel included heatsink)
Gigabyte GA-EP45-UD3R motherboard
G.SKILL PI Black 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 ram
EVGA Nvidia GTX 260 Core 216 SCed video card
Seagate Barracuda 7200.11 1TB HDD
Corsair 650W PSU
Acer 19" widescreen monitor
HP 22X DVD±R DVD Burner with LightScribe

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Problem

My problem is this. Before, I was running Windows 7 with no BSOD, but I felt the OS was very buggy and so I went back to Windows Vista.

After this, I started one by one installing my old programs. After installing ESET, utorrent, and L4D, I began to experience problems while running all 3 at the same time. I tried running my computer without L4D running, and just utorrent and ESET and BSOD. I tried running with just ESET and going online and BSOD. My current belief is that the BSOD is either related to viruses (I wouldn't know how, I have been installing my programs from CD and external HDD. Or it is related to ESET. As I have been getting BSOD whenever I even try to go online to this website (which is why I am on a different computer now). After looking over the debug code, I now believe that my problem is hardware related, please advise.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
DEBUG Code


Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`01c5e000 PsLoadedModuleList = 0xfffff800`01e23db0
Debug session time: Thu Jun 11 13:05:36.118 2009 (GMT-5)
System Uptime: 0 days 1:51:20.982
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd6018). Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffffa6002230d01, fffffa6008caba18, fffffa6008cab3f0}

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 907a9 not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : hardware ( nvlddmkm+2fd01 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa6002230d01, The address that the exception occurred at
Arg3: fffffa6008caba18, Exception Record Address
Arg4: fffffa6008cab3f0, Context Record Address

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

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

Page 907a9 not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you 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 that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80001c5e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nvlddmkm+2fd01
fffffa60`02230d01 010f add dword ptr [rdi],ecx

EXCEPTION_RECORD: fffffa6008caba18 -- (.exr 0xfffffa6008caba18)
ExceptionAddress: fffffa6002230d01 (nvlddmkm+0x000000000002fd01)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000001
Attempt to write to address 0000000000000001

CONTEXT: fffffa6008cab3f0 -- (.cxr 0xfffffa6008cab3f0)
rax=00000000000000a0 rbx=fffffa8008b305c0 rcx=0000000000000000
rdx=fffffa8006b9a000 rsi=0000000000000001 rdi=0000000000000001
rip=fffffa6002230d01 rsp=fffffa6008cabc50 rbp=0000000000000001
r8=fffffa8008b30500 r9=0000000000000004 r10=0000000000000000
r11=0000000000000000 r12=fffffa80087122a0 r13=fffffa800931e1b0
r14=0000000000000004 r15=fffffa6008cac030
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0x2fd01:
fffffa60`02230d01 010f add dword ptr [rdi],ecx ds:002b:00000000`00000001=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

MISALIGNED_IP:
nvlddmkm+2fd01
fffffa60`02230d01 010f add dword ptr [rdi],ecx

LAST_CONTROL_TRANSFER: from fffffa60022a14fa to fffffa6002230d01

STACK_TEXT:
fffffa60`08cabc50 fffffa60`022a14fa : fffffa80`087122a0 fffffa60`08cabf01 fffffa60`08cabf78 fffffa60`08cac584 : nvlddmkm+0x2fd01
fffffa60`08cabf10 fffffa60`027e81e7 : fffffa80`08905000 fffffa80`08b2f740 fffffa80`00000000 fffffa60`0000c000 : nvlddmkm+0xa04fa
fffffa60`08cac0f0 fffffa60`02d537e5 : fffffa60`027e815b fffffa80`08b2f740 fffffa60`08cac550 fffffa60`0c050000 : nvlddmkm+0x5e71e7
fffffa60`08cac180 fffffa60`02d7d0af : fffffa60`ffffe101 fffffa80`08b309e0 fffff880`0095c880 fffffa60`00000003 : dxgkrnl+0x397e5
fffffa60`08cac1d0 fffffa60`02d7cb89 : 00000000`000005ef 00000000`00000002 fffff880`4000ff00 00000000`c000fe80 : dxgkrnl+0x630af
fffffa60`08cac4e0 fffffa60`02d601ef : fffff880`0095c880 fffffa60`08cac960 fffff880`00000000 fffffa60`02d5ff6b : dxgkrnl+0x62b89
fffffa60`08cac6e0 fffff960`006034b4 : fffff900`c0087960 00000000`0104003c 00000000`0104003c fffff800`01c8c8d0 : dxgkrnl+0x461ef
fffffa60`08cac780 fffff960`00604568 : fffff900`c0087960 00000000`00000000 00000000`00000000 00000000`0104003c : cdd+0x34b4
fffffa60`08cacc40 fffff800`01ed6fd3 : 00000000`1077c05a fffffa80`08b2ebb0 00000000`00000080 fffff900`c0087960 : cdd+0x4568
fffffa60`08cacd50 fffff800`01cec816 : fffff800`01dd2680 fffffa80`08b2ebb0 fffffa80`04d23bb0 00000000`00000001 : nt!ProbeForRead+0xbd3
fffffa60`08cacd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!_misaligned_access+0x4e6


FOLLOWUP_IP:
nvlddmkm+2fd01
fffffa60`02230d01 010f add dword ptr [rdi],ecx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nvlddmkm+2fd01

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

STACK_COMMAND: .cxr 0xfffffa6008cab3f0 ; kb

FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys

BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys

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

Edited by JaceX, 11 June 2009 - 06:00 PM.


BC AdBot (Login to Remove)

 


m



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users