BSOD new computer

[Handi]

Hello guys, it's my first time here, thanks for providing this forum.

I've recently built a new computer and I start having BSODs. 3 BSODs in 2 days already.

Here's the last message I received:

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7600.2.0.0.256.48
  Locale ID:	4105

Additional information about the problem:
  BCCode:	109
  BCP1:	A3A039D8967C7752
  BCP2:	B3B7465EE8F94980
  BCP3:	FFFFF80002ABE12A
  BCP4:	0000000000000001
  OS Version:	6_1_7600
  Service Pack:	0_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\032110-43056-01.dmp
  C:\Users\Pavel\AppData\Local\Temp\WER-57626-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I've included the minidump files.

Here are the system specs:

OS
  Win7 x64
CPU
  Intel Core2 Quad Q8400 2.66GHz
Motherboard
  Gigabyte EP45-UD3P
Memory
  Patriot Extreme performance 2x2GB PC2-6400 DDR2-800
Graphics Card(s)
  Powercolor Radeon Hd 5770 850 MHz 512MB
Hard Drives
  Western Digital Caviar Black 640GB
PSU
  Corsair TX750W
Case
  Coolermaster CAC-T05 Centurion 5

Thank you in advance

 

[zigzag3143]

Hello guys, it's my first time here, thanks for providing this forum.

I've recently built a new computer and I start having BSODs. 3 BSODs in 2 days already.

Here's the last message I received:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.48
  Locale ID:    4105

Additional information about the problem:
  BCCode:    109
  BCP1:    A3A039D8967C7752
  BCP2:    B3B7465EE8F94980
  BCP3:    FFFFF80002ABE12A
  BCP4:    0000000000000001
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\032110-43056-01.dmp
  C:\Users\Pavel\AppData\Local\Temp\WER-57626-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I've included the minidump files.

Here are the system specs:

OS
  Win7 x64
CPU
  Intel Core2 Quad Q8400 2.66GHz
Motherboard
  Gigabyte EP45-UD3P
Memory
  Patriot Extreme performance 2x2GB PC2-6400 DDR2-800
Graphics Card(s)
  Powercolor Radeon Hd 5770 850 MHz 512MB
Hard Drives
  Western Digital Caviar Black 640GB
PSU
  Corsair TX750W
Case
  Coolermaster CAC-T05 Centurion 5

Thank you in advance

Pretty straight forward. Memory corruption.
download memtestx86 and run it for at least 6 passes.

Run a system file check
(type cmd in search>right click and run as admin>sfc /scannow (note the space between sfc and "/"))

Let u s know if you need help

Ken

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


Loading Dump File [C:\Users\K\Desktop\New folder (3)\032110-43056-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a04000 PsLoadedModuleList = 0xfffff800`02c41e50
Debug session time: Sun Mar 21 14:57:04.568 2010 (GMT-4)
System Uptime: 0 days 0:08:25.238
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8967c7752, b3b7465ee8f94980, fffff80002abe12a, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8967c7752, Reserved
Arg2: b3b7465ee8f94980, Reserved
Arg3: fffff80002abe12a, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002a75f00

STACK_TEXT:  
fffff880`031a8598 00000000`00000000 : 00000000`00000109 a3a039d8`967c7752 b3b7465e`e8f94980 fffff800`02abe12a : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002abe19b - nt! ?? ::FNODOBFM::`string'+19d91
    [ e8:c8 ]
1 error : !nt (fffff80002abe19b)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

 

[Handi]

Thanks for the quick reply.

I'm performing the memtest right now (posting from another computer) and it's pretty slow. From the report it seems quite obvious that the problem comes from memory. The first two times the bsod came after the computer came back from sleep mode, thus if it loaded the kernel in corrupted memory then no wonder that it crashed. Besides my motherboard and graphic card drivers were up to date and I didn't really have time to install any special software.

Anyway, I wonder if directcanada will accept to replace the faulty memory

 

[Handi]

Heh, here it goes, it just found a copy error:

Memory error detected! Copying between f46d6c4 and f46d598 did not result in accurate copy.

EDIT: And now a 2nd error at barely 20%. 171cdec4 to 171cdeb0.

So I'll try swapping the ram sticks of slots for now to prevent further errors on disk and I guess I will have to ask for replacement asap.