BSOD Crash

[bboyoxygen]

I just built a new computer for my inlaws and had several BSODs with different bccodes (1, 1a, a). I formatted and reinstalled the OS, updates, as well as clean installs of all recent drivers downloaded from the manufacturer websites. I had another BSOD after this and I am worried that it may be related to the memory I have installed. Specs are as follows:

Windows 7 Home Premium x64
CPU: AMD Phenom II 555 3.2Ghz Quad Core
Motherboard: Asus M4A785-M onboard sound, video, wired lan
Memory: G.Skill 4GB DDR2-800 (2x2gb) F2-6400CL5D-4GBNT
HDD: Seagate Barracuda 320gb SATA2


If you need more information please let me know.

I should add that I have not seen any possible triggers for these BSODs. They just happen as I am using the computer.

I have also updated to the most current motherboard bios.

 

[yowanvista]

Seems to be related to your HDD, run http://www.sevenforums.com/tutorials/433-disk-check.html and SeaTools
Remove any Asus system tuners such as PC Probe, these tend to create BSODs

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88002fbd348, fffff88002fbcba0, fffff880010553e1}

Probably caused by : Ntfs.sys ( Ntfs!memmove+1d1 )


NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88002fbd348
Arg3: fffff88002fbcba0
Arg4: fffff880010553e1

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


EXCEPTION_RECORD:  fffff88002fbd348 -- (.exr 0xfffff88002fbd348)
ExceptionAddress: fffff880010553e1 (Ntfs!memmove+0x00000000000001d1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002fbcba0 -- (.cxr 0xfffff88002fbcba0)
rax=fffff8a00958bfc0 rbx=0000000000000000 rcx=fffffa80045d2550
rdx=006d05adfc0edb8c rsi=7fffffffffffffff rdi=000000001106192b
rip=fffff880010553e1 rsp=fffff88002fbd588 rbp=fffff80002e26260
 r8=0000000000000072  r9=0000000000000000 r10=fffff80002e10348
r11=fffffa80045d24e0 r12=fffffa8003b66e50 r13=fffffa8004563180
r14=0000000000000001 r15=fffffa80045d24dc
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Ntfs!memmove+0x1d1:
fffff880`010553e1 668b040a        mov     ax,word ptr [rdx+rcx] ds:002b:006d002e`006c00dc=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb8100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!memmove+1d1
fffff880`010553e1 668b040a        mov     ax,word ptr [rdx+rcx]

FAULTING_IP: 
Ntfs!memmove+1d1
fffff880`010553e1 668b040a        mov     ax,word ptr [rdx+rcx]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8800110c20d to fffff880010553e1

STACK_TEXT:  
fffff880`02fbd588 fffff880`0110c20d : fffff8a0`00000000 00000000`00000000 fffff880`02fbdab0 00000000`000007ff : Ntfs!memmove+0x1d1
fffff880`02fbd590 fffff880`0110f8db : fffff880`02fbdab0 fffffa80`04563180 fffff880`02fbda00 fffff880`01062000 : Ntfs!NtfsCheckpointVolume+0x6ed
fffff880`02fbd990 fffff880`0110e27b : fffff880`02fbdab0 fffffa80`04563180 fffffa80`04563188 fffff880`01055020 : Ntfs!NtfsCheckpointAllVolumesWorker+0x4b
fffff880`02fbd9e0 fffff880`01110398 : fffff880`02fbdab0 00000000`00000000 fffff880`0110f890 fffff880`02fbdcb8 : Ntfs!NtfsForEachVcb+0x167
fffff880`02fbda80 fffff800`02c93021 : fffff800`02e26200 fffff800`02f7f000 fffff800`02e26200 00000000`00000005 : Ntfs!NtfsCheckpointAllVolumes+0xb8
fffff880`02fbdcb0 fffff800`02f2532e : 00000000`00000000 fffffa80`037b5040 00000000`00000080 fffffa80`0366b9e0 : nt!ExpWorkerThread+0x111
fffff880`02fbdd40 fffff800`02c7a666 : fffff880`009e9180 fffffa80`037b5040 fffff880`009f3f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fbdd80 00000000`00000000 : fffff880`02fbe000 fffff880`02fb8000 fffff880`02fbd9e0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!memmove+1d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792f9

STACK_COMMAND:  .cxr 0xfffff88002fbcba0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!memmove+1d1

BUCKET_ID:  X64_0x24_Ntfs!memmove+1d1

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

 

[bboyoxygen]

Thanks! I have run discheck with the autofix options and there were no bad sectors. I have run all the basic tests on SeaTools and am running the long generic test right now. Everything has passed so far. I haven't had a BSOD since starting these tests.

I do not have any system tuners installed.

 

[bboyoxygen]

I had an unexpected restart during the long scan. There was no bluescreen or dump file. Attempting the long scan again with SeaTools

 

[bboyoxygen]

I did the long test and SeaTools reported the hard drive passed the tests. I went immediately after closing to post on here and got another BSOD. I ran the BSOD tool and performance monitor again. Attachment will be on the original post.

UPDATE (6:20PM Central): I reseated the ram and un/replugged the ata cables for the hdd and dvdrw drive. Also, I had the hdd and dvdrw running off of 2 power cables on the same line from the psu so I took one out and hooked up a different one and they are on different lines completely now. I don't know if that might make a difference but I need to get this computer running well before the wife and I go back home later this week.

UPDATE (6:45PM Central): Had nother BSOD. I will zip this badboy up if need be. Let me know. Thank you for your help.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002CCF337
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\052411-27393-01.dmp
C:\Users\Tebeest\AppData\Local\Temp\WER-43274-0.sysdata.xml

 

[yowanvista]

I did the long test and SeaTools reported the hard drive passed the tests. I went immediately after closing to post on here and got another BSOD. I ran the BSOD tool and performance monitor again. Attachment will be on the original post.

UPDATE (6:20PM Central): I reseated the ram and un/replugged the ata cables for the hdd and dvdrw drive. Also, I had the hdd and dvdrw running off of 2 power cables on the same line from the psu so I took one out and hooked up a different one and they are on different lines completely now. I don't know if that might make a difference but I need to get this computer running well before the wife and I go back home later this week.

UPDATE (6:45PM Central): Had nother BSOD. I will zip this badboy up if need be. Let me know. Thank you for your help.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002CCF337
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\052411-27393-01.dmp
C:\Users\Tebeest\AppData\Local\Temp\WER-43274-0.sysdata.xml

Zip the dump files

 

[bboyoxygen]

I did the long test and SeaTools reported the hard drive passed the tests. I went immediately after closing to post on here and got another BSOD. I ran the BSOD tool and performance monitor again. Attachment will be on the original post.

UPDATE (6:20PM Central): I reseated the ram and un/replugged the ata cables for the hdd and dvdrw drive. Also, I had the hdd and dvdrw running off of 2 power cables on the same line from the psu so I took one out and hooked up a different one and they are on different lines completely now. I don't know if that might make a difference but I need to get this computer running well before the wife and I go back home later this week.

UPDATE (6:45PM Central): Had nother BSOD. I will zip this badboy up if need be. Let me know. Thank you for your help.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002CCF337
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\052411-27393-01.dmp
C:\Users\Tebeest\AppData\Local\Temp\WER-43274-0.sysdata.xml

Zip the dump files

I just attached another zip file with the dump files all together.

 

[bboyoxygen]

I ran memtest throught 3 passes a little while ago and no errors were present. I don't know what else I can do or what I might need to replace.

 

[yowanvista]

Your last crash was cause by an AVG software, please remove any AVG antivirus and use MSE

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa800365d180, fffffa800365d580, fffffa800365d580}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )


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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa800365d180, the pool entry being checked.
Arg3: fffffa800365d580, the read back flink freelist value (should be the same as 2).
Arg4: fffffa800365d580, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  avgchsva.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dbe4b3 to fffff80002c93d00

STACK_TEXT:  
fffff880`06dd6718 fffff800`02dbe4b3 : 00000000`00000019 00000000`00000003 fffffa80`0365d180 fffffa80`0365d580 : nt!KeBugCheckEx
fffff880`06dd6720 fffff800`02cab174 : 00000000`00000000 fffffa80`03c6dc80 00000000`000f001f 00000000`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`06dd6810 fffff800`02c77f5c : fffff880`06dd6b88 00000000`00000001 00000000`00000000 fffff880`06dd6910 : nt!MiAddViewsForSection+0x1d4
fffff880`06dd68a0 fffff800`02fac4ed : 00000000`00000001 00000000`00000007 00000000`00000000 fffff880`06dd6b58 : nt!MiAddViewsForSectionWithPfn+0x98
fffff880`06dd6910 fffff800`02fac9bb : fffffa80`03c6dc00 fffffa80`04f43480 fffff880`06dd6b50 fffffa80`05e02060 : nt!MiMapViewOfDataSection+0x64d
fffff880`06dd69f0 fffff800`02face1e : fffffa80`00000001 fffffa80`04f43480 fffff880`06dd6b50 00000000`00000000 : nt!MiMapViewOfSection+0x20b
fffff880`06dd6ae0 fffff800`02c92f93 : 00000000`00000458 fffffa80`05e02060 00000000`02bfe518 00000000`00001001 : nt!NtMapViewOfSection+0x2bd
fffff880`06dd6bb0 00000000`77a1159a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02bfe4f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a1159a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a53
fffff800`02dbe4b3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a53

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

Followup: Pool_corruption
---------

 

[bboyoxygen]

AVG removed and MSE installed. Could the other crashes be caused by AVG too?

 

[yowanvista]

AVG removed and MSE installed. Could the other crashes be caused by AVG too?

Yes they could be, upload any new dumps if you still get BSODs

 

[bboyoxygen]

Okay, I'm also running memtest on the individual sticks of ram right now. I'm going to do 7 passes on each stick just to make sure. Replying from my phone. Lol

No errors on 7 passes per stick.

 

[yowanvista]

Okay, I'm also running memtest on the individual sticks of ram right now. I'm going to do 7 passes on each stick just to make sure. Replying from my phone. Lol

No errors on 7 passes per stick.

Is your computer still having BSODs?

 

[bboyoxygen]

Okay, I'm also running memtest on the individual sticks of ram right now. I'm going to do 7 passes on each stick just to make sure. Replying from my phone. Lol

No errors on 7 passes per stick.

Is your computer still having BSODs?

Yes it had one last night. I am uploading it to my original post.

 

[bboyoxygen]

So I checked the bios for the voltages and the stupid auto voltage was running at 1.5 for the ram and the ram is 1.8v. I changed that and am now running Prime95 torture test to see if I get any bluescreens. I might have fixed the problem and I HOPE SO. I will report back if I get another BSOD.