Windows 7: WIN 7 x64 BSOD/RAM issues

protoolsuser · 27 Oct 2010

Need some advice from an expert these problems im having our beyond my knowledge.

Heres a rundown of the situation....

Built new computer

Gigabyte x58 motherboard
i7 950 CPU
OCZ gold 1600 mhz ddr3 triple channel ram 3x2 (PC3 12800)
Radeon graphics card
corsair power supply
caviar black HD's

Built system, had ram problems, thought i had fixed them (ran good for a few days).
Back to having ram problems, at first i was getting hardware issue error in memory diagnostic. Found out RAM is rated for 1.65v was running at 1.5v. Changed the voltage in BIOS to 1.64v now running at 1.61...can start windows with networking in safe mode (still running below par). Can start windows regulary about 1/5 times the other times i am getting various BSOD messages. memory_management, no page file, special pool detected.... i attached the dump files. I believe it is ram/driver issue but i am just guessing from what i have read. Any help will be greatly appreciated, will pay you on paypal if completely fixed!

i am at my wits end. I just want my new computer to run smoothly like it should

also would not let me run perfmon report (maybe because i am in safe mode?)

Also i enabled driver verifier, not sure how to get the results though....

Thanks

protoolsuser · 27 Oct 2010

from the boot menu i selected start from last known good configuration and was able to get into windows without a BSOD. It is still running poorly though and i dont believe the error has been corrected. here is the performance report.

Also was able to get a trueimage backup done without it crashing, makes me feel a little better, at least i wont lose all my data if i have to reinstall Windows 7

protoolsuser · 27 Oct 2010

well if anyone cares the fix was related to RAM. Did not know you had to change multiplier, voltage, CAS latency, etc to match you RAM to motherboard....everything seems to be running smoothly now, hopefully it will last this time!

wish · 28 Oct 2010

Hi,
Your 2 latest dumps file triggered by driver verifier and it blame on diginet.sys (part of Ethernet Packet Driver). So it's better to remove that driver until your system stable.

Code:

diginet.sys
File description : Ethernet Packet Driver (Digidesign, A Division of Avid Technology, Inc.)

Another dump point at memory corruption, the cause could be RAM itself or 3rd driver that make corruption.
Since Rtvscan.exe process get involved, better to remove it as well.
Rtvscan.exe is part of symantec antivirus, uninstall it and replace with MSE.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 6cf17, 2, 6bc16}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
PROCESS_NAME:  Rtvscan.exe

Since you have memory management issue (0x1A ; 0x50)
Do memory test at least 7 passes
RAM - Test with Memtest86+

Reinstall and update chicony device driver.
Welcome to visit Chicony Website

And in the performance report :
"The average disk queue length is 1. The disk may be at its maximum transfer capacity due to throughput and disk seeks"
--> Open command prompt (as admin) --> chkdsk /r /f
--> Perform hardrive diagnostic to make sure your hardrive is in good condition
Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Log

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff9800e674f90, fffff9800e674ffc, 754074, 24}

Unable to load image \SystemRoot\system32\DRIVERS\diginet.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for diginet.sys
*** ERROR: Module load completed but symbols could not be loaded for diginet.sys
Probably caused by : diginet.sys ( diginet+1525 )

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

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff9800e674f90, address trying to free
Arg2: fffff9800e674ffc, address where bits are corrupted
Arg3: 0000000000754074, (reserved)
Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten

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


BUGCHECK_STR:  0xC1_24

SPECIAL_POOL_CORRUPTION_TYPE:  24

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dc2843 to fffff80002cbb740

STACK_TEXT:  
fffff880`06ce16d8 fffff800`02dc2843 : 00000000`000000c1 fffff980`0e674f90 fffff980`0e674ffc 00000000`00754074 : nt!KeBugCheckEx
fffff880`06ce16e0 fffff800`02dee356 : 00000000`000006df 00000000`6b636150 00000000`00000074 fffffa80`08870bd0 : nt!MmFreeSpecialPool+0x383
fffff880`06ce1810 fffff880`07424525 : fffff980`0e674f90 fffff880`07425eb0 fffff980`0e674fa0 fffff880`014ab028 : nt!ExDeferredFreePool+0xf13
fffff880`06ce18c0 fffff980`0e674f90 : fffff880`07425eb0 fffff980`0e674fa0 fffff880`014ab028 fffffa80`00000000 : diginet+0x1525
fffff880`06ce18c8 fffff880`07425eb0 : fffff980`0e674fa0 fffff880`014ab028 fffffa80`00000000 fffff800`02d7ec01 : 0xfffff980`0e674f90
fffff880`06ce18d0 fffff980`0e674fa0 : fffff880`014ab028 fffffa80`00000000 fffff800`02d7ec01 fffff880`06ce1928 : diginet+0x2eb0
fffff880`06ce18d8 fffff880`014ab028 : fffffa80`00000000 fffff800`02d7ec01 fffff880`06ce1928 fffffa80`04e7a000 : 0xfffff980`0e674fa0
fffff880`06ce18e0 fffffa80`00000000 : fffff800`02d7ec01 fffff880`06ce1928 fffffa80`04e7a000 00000000`00000086 : ndis!__PchSym_ <PERF> (ndis+0x69028)
fffff880`06ce18e8 fffff800`02d7ec01 : fffff880`06ce1928 fffffa80`04e7a000 00000000`00000086 fffff800`0314800b : 0xfffffa80`00000000
fffff880`06ce18f0 fffff880`014a5110 : 00000000`c0000001 fffffa80`08870a80 fffffa80`006e006c fffff980`0e674f90 : nt!RtlCaptureStackBackTrace+0x21
fffff880`06ce1920 00000000`c0000001 : fffffa80`08870a80 fffffa80`006e006c fffff980`0e674f90 fffff880`014a5110 : ndis!WPP_GLOBAL_Control
fffff880`06ce1928 fffffa80`08870a80 : fffffa80`006e006c fffff980`0e674f90 fffff880`014a5110 00000000`c0000001 : 0xc0000001
fffff880`06ce1930 fffffa80`006e006c : fffff980`0e674f90 fffff880`014a5110 00000000`c0000001 00000000`00000000 : 0xfffffa80`08870a80
fffff880`06ce1938 fffff980`0e674f90 : fffff880`014a5110 00000000`c0000001 00000000`00000000 fffffa80`083a11a0 : 0xfffffa80`006e006c
fffff880`06ce1940 fffff880`014a5110 : 00000000`c0000001 00000000`00000000 fffffa80`083a11a0 fffff980`03e88f08 : 0xfffff980`0e674f90
fffff880`06ce1948 00000000`c0000001 : 00000000`00000000 fffffa80`083a11a0 fffff980`03e88f08 fffffa80`04f9ebb0 : ndis!WPP_GLOBAL_Control
fffff880`06ce1950 00000000`00000000 : fffffa80`083a11a0 fffff980`03e88f08 fffffa80`04f9ebb0 fffff980`0e6b4d00 : 0xc0000001


STACK_COMMAND:  kb

FOLLOWUP_IP: 
diginet+1525
fffff880`07424525 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  diginet+1525

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: diginet

IMAGE_NAME:  diginet.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c189063

FAILURE_BUCKET_ID:  X64_0xC1_24_VRF_diginet+1525

BUCKET_ID:  X64_0xC1_24_VRF_diginet+1525

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

2: kd> lmvm diginet
start             end                 module name
fffff880`07423000 fffff880`0742b000   diginet  T (no symbols)           
    Loaded symbol image file: diginet.sys
    Image path: \SystemRoot\system32\DRIVERS\diginet.sys
    Image name: diginet.sys
    Timestamp:        Wed Jun 16 01:50:43 2010 (4C189063)
    CheckSum:         0000630D
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

protoolsuser · 28 Oct 2010

hey thanks for the input i will give all of that a shot....i did a system restore to a earlier point and set my ram settings correctly in the BIOS also uninstalled pro tools going to do a clean install with that....seems to be running smoothly since i fixed the ram settings...

Windows 7: WIN 7 x64 BSOD/RAM issues

WIN 7 x64 BSOD/RAM issues problems?