BSOD on New Build

[sruschill]

I have recently, this weekend, built a new computer using fairly standard parts. The system is periodically giving me the BSOD. I have followed your instructions for how to troubleshoot. Thanks in advance for any help.

Here are the system components I am using:

These are the new items:
Intel i5 650
4 GB of OCZ DDR3
Gigabyte MB H55-USB3
Seagate Barracuda 1TB

Using these as "legacy" but not very old
ASUS G100 Video card
OCZ 650w PS

I have attached the requested documents, note as requested the .html file is in the .zip.

I did just swap the memory but would like your thoughts on if something else is happening.


Thanks!

 

[zigzag3143]

I have recently, this weekend, built a new computer using fairly standard parts. The system is periodically giving me the BSOD. I have followed your instructions for how to troubleshoot. Thanks in advance for any help.

Here are the system components I am using:

These are the new items:
Intel i5 650
4 GB of OCZ DDR3
Gigabyte MB H55-USB3
Seagate Barracuda 1TB

Using these as "legacy" but not very old
ASUS G100 Video card
OCZ 650w PS

I have attached the requested documents, note as requested the .html file is in the .zip.

I did just swap the memory but would like your thoughts on if something else is happening.


Thanks!

Hi and welcome

These were caused by a few things. First Norton (ccHPx64.sys). Then two year old drivers

First remove Norton and replace with Microsoft Security Essentials.
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials

Then Update the below drivers
How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Let us know if you need hep.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\100910-15506-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a52000 PsLoadedModuleList = 0xfffff800`02c8fe50
Debug session time: Sat Oct  9 19:01:54.186 2010 (GMT-4)
System Uptime: 0 days 0:08:35.341
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa800386a800, fffffa800386a850, 4050006}

Unable to load image \SystemRoot\system32\drivers\NISx64\1106000.020\ccHPx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ccHPx64.sys
*** ERROR: Module load completed but symbols could not be loaded for ccHPx64.sys
Probably caused by : ccHPx64.sys ( ccHPx64+7d08 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800386a800, The pool entry we were looking for within the page.
Arg3: fffffa800386a850, The next pool entry.
Arg4: 0000000004050006, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfa0e0
 fffffa800386a800 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002bf56d3 to fffff80002ac3f00

STACK_TEXT:  
fffff880`07095138 fffff800`02bf56d3 : 00000000`00000019 00000000`00000020 fffffa80`0386a800 fffffa80`0386a850 : nt!KeBugCheckEx
fffff880`07095140 fffff880`082c4d08 : fffffa80`040d87f8 fffffa80`04113e48 00000000`63747673 fffff880`082ebbdc : nt!ExFreePool+0xda4
fffff880`070951f0 fffffa80`040d87f8 : fffffa80`04113e48 00000000`63747673 fffff880`082ebbdc fffffa80`040ddd78 : ccHPx64+0x7d08
fffff880`070951f8 fffffa80`04113e48 : 00000000`63747673 fffff880`082ebbdc fffffa80`040ddd78 fffff880`0832c71b : 0xfffffa80`040d87f8
fffff880`07095200 00000000`63747673 : fffff880`082ebbdc fffffa80`040ddd78 fffff880`0832c71b 00000000`00000000 : 0xfffffa80`04113e48
fffff880`07095208 fffff880`082ebbdc : fffffa80`040ddd78 fffff880`0832c71b 00000000`00000000 fffffa80`03c55888 : 0x63747673
fffff880`07095210 fffffa80`040ddd78 : fffff880`0832c71b 00000000`00000000 fffffa80`03c55888 00000000`00000080 : ccHPx64+0x2ebdc
fffff880`07095218 fffff880`0832c71b : 00000000`00000000 fffffa80`03c55888 00000000`00000080 fffff880`0832c70c : 0xfffffa80`040ddd78
fffff880`07095220 00000000`00000000 : fffffa80`03c55888 00000000`00000080 fffff880`0832c70c fffffa80`03c55888 : ccHPx64+0x6f71b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ccHPx64+7d08
fffff880`082c4d08 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ccHPx64+7d08

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ccHPx64

IMAGE_NAME:  ccHPx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b6c8829

FAILURE_BUCKET_ID:  X64_0x19_20_ccHPx64+7d08

BUCKET_ID:  X64_0x19_20_ccHPx64+7d08

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

drivers

GVTDrv64.sys        fffff880`065d1000    fffff880`065db000    0x0000a000    0x44fd22ca    9/5/2006 03:10:02                        
gdrv.sys        fffff880`06597000    fffff880`065a0000    0x00009000    0x49b9d175    3/12/2009 23:22:29                        
NuidFltr.sys        fffff880`06849000    fffff880`06852000    0x00009000    0x4a03f30b    5/8/2009 04:53:31                        
spldr.sys        fffff880`017db000    fffff880`017e3000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
spsys.sys        fffff880`06400000    fffff880`06471000    0x00071000    0x4a085e7a    5/11/2009 13:20:58                        
nvlddmkm.sys        fffff880`04adf000    fffff880`055e6b00    0x00b07b00    0x4a0c8387    5/14/2009 16:48:07                        
amdxata.sys        fffff880`012a4000    fffff880`012af000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

 

[sruschill]

Thanks. I will do what you recommend and let you know the results.