I need a help to resolve the below error, Safe Mode works fine.
Operating System: Windows 7 Home Premium 64bit (6.1, Build 7601) Service Pack 1 (7601.win7Sp1_gdr.110622-1506)
Language: English (Regional Setting: English)
System Manufacturer: Hewlett-Packard
System Model: HP Pavilion P6000 Series
BIOS: BIOS Date: 03/22/11 14:31:33 Ver: 6.06
Processor: AMD Phenom(tm) II X4 840T Processor (4 CPUs), ~2.9GHz
Memory: 6144MB RAM
Available OS Memory: 5888MB RAM
Page File: 1305MB used, 10466MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
every time it gives me same message.
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7601
Service Pack: 1_0
Files that help describe the problem:
I have analyzed your latest crash dump. It seems that the file "kdcom.dll" is responsible for the problem. I cant find what the file is good for but recommendations in other forums are to reinstall windows :-/
There are generally three different causes for this bug check:
1.A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.
2.A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.
3.A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
kdcom.dll is part of the kernal debugger, so its not a surprise it crashed as a result of this blue screen. Odds are though, some OTHER problem caused this dll to crash, and not the dll itself.
The most important question, is do you get other BSOD error messages/STOP codes aside from Bcode: 109? If not, then you likely have a driver problem somewhere. Otherwise, you might have a hardware problem instead.
[Note, I can't get to the dumps at work, so I really can't dig right now].
*Probably* a driver side problem then, which may take a while to track down.
The main problem is the driver that the BSOD message reports is usually not the one that actually caused the problem, but instead the one that crashed because of the problem that resulted. So tracking this down could take some digging...
The most obvious question: Has this been happening since you got the PC?
Check and see what Windows updated; you should be able to view the past update history.
Really, it would be nice if Windows had a menu that tracked ALL install/update dates in one nice spot. Would aid debugging of issues like this a ton...
This is an odd one, since this is a type of BSOD you typically don't see unless you are developing low-level device drivers; you should never see this on a consumer system...Can't rule out a botched windows update, HW, or some other driver related problem yet.