Hey all,
I am getting the dreaded BSOD. It happens very randomly. From playing an online game to working with a word document. I am running:
Windows 7 x64 Ultimate
DFI Lanparty UT/LT P35
Intel Core 2 Quad 2.40Ghz
8GB Corsair Ballistix ddr2-400 Ram ( 4 2gb sticks )
C: drive = 500GB sata
D: drive = 1TB sata
2 dvd/rw sata
Nvidia Geforce gtx 275
I have installed a fresh/clean copy of windows. The install process went fine w/o a hitch. After installing 1 application, bsod happened. Initially I thought maybe it was a program, but the only program that I installed was firefox. I was searching the net, then bam! I ran memtest86+, to figure out if it was my memory. I placed 1 stick at a time and ran the test for approximately 1 hour for each stick. All the memory passed. But when I installed all the memory, and ran the test, it failed. Also, when I removed the memory, they were all pretty hot. Right now, I only have 6gb installed. They are warm, but not hot. I have attached the minidump file below. Quick question: is it possible that my 800watt power supply could be going bad, if the ram is getting hot. Meaning that it is not supplying the correct voltage?
Maybe someone here can make some head way, since I have no clue what to look for.
Thanks,
Neal
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\DMG\Desktop\122710-27015-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0285a000 PsLoadedModuleList = 0xfffff800`02a97e50
Debug session time: Mon Dec 27 17:29:18.171 2010 (GMT-6)
System Uptime: 0 days 0:02:00.015
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d89870e50a, b3b7465eeaedb700, fffff8000287648c, 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
---------
3: 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: a3a039d89870e50a, Reserved
Arg2: b3b7465eeaedb700, Reserved
Arg3: fffff8000287648c, 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 fffff800028ca740
STACK_TEXT:
fffff880`031b65d8 00000000`00000000 : 00000000`00000109 a3a039d8`9870e50a b3b7465e`eaedb700 fffff800`0287648c : nt!KeBugCheckEx
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff800028764c4-fffff80002876f44)
fffff800028764c0 48 8b 01 48 *3a c8 75 0e 48 8b c1 48 8b 5c 24 38 H..H:.u.H..H.\$8
...
fffff80002876f40 00 f7 66 41 *82 84 24 c6 01 00 00 01 75 0f 49 8d ..fA..$.....u.I.
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
3: kd> lmvm memory_corruption
start end module name
I am getting the dreaded BSOD. It happens very randomly. From playing an online game to working with a word document. I am running:
Windows 7 x64 Ultimate
DFI Lanparty UT/LT P35
Intel Core 2 Quad 2.40Ghz
8GB Corsair Ballistix ddr2-400 Ram ( 4 2gb sticks )
C: drive = 500GB sata
D: drive = 1TB sata
2 dvd/rw sata
Nvidia Geforce gtx 275
I have installed a fresh/clean copy of windows. The install process went fine w/o a hitch. After installing 1 application, bsod happened. Initially I thought maybe it was a program, but the only program that I installed was firefox. I was searching the net, then bam! I ran memtest86+, to figure out if it was my memory. I placed 1 stick at a time and ran the test for approximately 1 hour for each stick. All the memory passed. But when I installed all the memory, and ran the test, it failed. Also, when I removed the memory, they were all pretty hot. Right now, I only have 6gb installed. They are warm, but not hot. I have attached the minidump file below. Quick question: is it possible that my 800watt power supply could be going bad, if the ram is getting hot. Meaning that it is not supplying the correct voltage?
Maybe someone here can make some head way, since I have no clue what to look for.
Thanks,
Neal
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\DMG\Desktop\122710-27015-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0285a000 PsLoadedModuleList = 0xfffff800`02a97e50
Debug session time: Mon Dec 27 17:29:18.171 2010 (GMT-6)
System Uptime: 0 days 0:02:00.015
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d89870e50a, b3b7465eeaedb700, fffff8000287648c, 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
---------
3: 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: a3a039d89870e50a, Reserved
Arg2: b3b7465eeaedb700, Reserved
Arg3: fffff8000287648c, 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 fffff800028ca740
STACK_TEXT:
fffff880`031b65d8 00000000`00000000 : 00000000`00000109 a3a039d8`9870e50a b3b7465e`eaedb700 fffff800`0287648c : nt!KeBugCheckEx
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff800028764c4-fffff80002876f44)
fffff800028764c0 48 8b 01 48 *3a c8 75 0e 48 8b c1 48 8b 5c 24 38 H..H:.u.H..H.\$8
...
fffff80002876f40 00 f7 66 41 *82 84 24 c6 01 00 00 01 75 0f 49 8d ..fA..$.....u.I.
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
3: kd> lmvm memory_corruption
start end module name