Overclock.net › Forums › Graphics Cards › NVIDIA › BSOD after 470 install
New Posts  All Forums:Forum Nav:

BSOD after 470 install - Page 2

post #11 of 23
I'm going with drivers on this one. Try a different set
post #12 of 23
Thread Starter 
I can do a hard drive check after I get back from lunch.
The drivers I am currently using are 266.58
The power supply I have had since July 2009.


I will have to go for a bit but when I return I will do a hard drive check and get back to you.
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 Asus P6X58D Premium SLI GTX 470s Zotac/Asus 6gb G Skill Ripjaws 
Hard DriveOSMonitorKeyboard
500gb Windows 7 Ultimate 64bit 22" AOC Saitek Eclipse 
PowerCaseMouse
Corsair 850w CM 690 Logitech G5 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 Asus P6X58D Premium SLI GTX 470s Zotac/Asus 6gb G Skill Ripjaws 
Hard DriveOSMonitorKeyboard
500gb Windows 7 Ultimate 64bit 22" AOC Saitek Eclipse 
PowerCaseMouse
Corsair 850w CM 690 Logitech G5 
  hide details  
Reply
post #13 of 23
Try increase small amount IOH voltage.
post #14 of 23
Thread Starter 
Ok, I did a hard drive scan and no errors were found. I also tried out the 260.99 drivers but am having the same results.
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 Asus P6X58D Premium SLI GTX 470s Zotac/Asus 6gb G Skill Ripjaws 
Hard DriveOSMonitorKeyboard
500gb Windows 7 Ultimate 64bit 22" AOC Saitek Eclipse 
PowerCaseMouse
Corsair 850w CM 690 Logitech G5 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 Asus P6X58D Premium SLI GTX 470s Zotac/Asus 6gb G Skill Ripjaws 
Hard DriveOSMonitorKeyboard
500gb Windows 7 Ultimate 64bit 22" AOC Saitek Eclipse 
PowerCaseMouse
Corsair 850w CM 690 Logitech G5 
  hide details  
Reply
post #15 of 23
load bios defaults and double check that the gpu is set to pcie also check the mount of the psu and double check the connectors the error code is pointing to power failure i would pull then replug the power plugs its not only the gpu what is erroring its also pointing to memory in loop... which is why im suggesting a bios refresh if you have an overclock you should be able to reset it after sometimes the irq assignment from the new gpu is the same as what is on another component what can cause the memory loop error...

post back if it happens again..
post #16 of 23
Thread Starter 
It looks like a small boost in the IOH did the trick, been playing BFBC2 for about 45 minutes now without any problems.
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 Asus P6X58D Premium SLI GTX 470s Zotac/Asus 6gb G Skill Ripjaws 
Hard DriveOSMonitorKeyboard
500gb Windows 7 Ultimate 64bit 22" AOC Saitek Eclipse 
PowerCaseMouse
Corsair 850w CM 690 Logitech G5 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 Asus P6X58D Premium SLI GTX 470s Zotac/Asus 6gb G Skill Ripjaws 
Hard DriveOSMonitorKeyboard
500gb Windows 7 Ultimate 64bit 22" AOC Saitek Eclipse 
PowerCaseMouse
Corsair 850w CM 690 Logitech G5 
  hide details  
Reply
post #17 of 23
@OP

If you dig out the memory.dmp file from C:\\Windows\\Minidump and post it here for download, I can debug it and tell you exactly what caused the BSOD.
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
post #18 of 23
Thread Starter 
Here are three from today.
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 Asus P6X58D Premium SLI GTX 470s Zotac/Asus 6gb G Skill Ripjaws 
Hard DriveOSMonitorKeyboard
500gb Windows 7 Ultimate 64bit 22" AOC Saitek Eclipse 
PowerCaseMouse
Corsair 850w CM 690 Logitech G5 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 Asus P6X58D Premium SLI GTX 470s Zotac/Asus 6gb G Skill Ripjaws 
Hard DriveOSMonitorKeyboard
500gb Windows 7 Ultimate 64bit 22" AOC Saitek Eclipse 
PowerCaseMouse
Corsair 850w CM 690 Logitech G5 
  hide details  
Reply
post #19 of 23
Quote:
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80065558f8, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80065558f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`035626f0 fffff800`03328d29 : fffffa80`065558d0 fffffa80`055a9740 fffffa80`00000009 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03562c10 fffff800`03208217 : fffffa80`065558d0 fffff800`03282658 fffffa80`055a9740 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03562c40 fffff800`0316f865 : fffff800`032e43a0 00000000`00000001 fffffa80`065b4820 fffffa80`055a9740 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03562c80 fffff800`030efa21 : fffff880`00c30e00 fffff800`0316f840 fffffa80`055a9700 33ba33ba`46374637 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03562cb0 fffff800`03382cce : 983a983a`b3c8b3c8 fffffa80`055a9740 00000000`00000080 fffffa80`05506040 : nt!ExpWorkerThread+0x111
fffff880`03562d40 fffff800`030d6fe6 : fffff880`0336a180 fffffa80`055a9740 fffff880`033750c0 03da03da`92d092d0 : nt!PspSystemThreadStartup+0x5a
fffff880`03562d80 00000000`00000000 : fffff880`03563000 fffff880`0355d000 fffff880`035620a0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

Followup: MachineOwner
---------
That is directly related to your CPU. Either unstable, not enough voltage, or setup incorrectly. There are two more you sent in the ZIP, those I did not do because I inadvertently saved the module path (darnit.....) and buggered my debug. Will post back soon as I can fix WinDBG
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
post #20 of 23
Quote:

Loading User Symbols
Loading unloaded module list
..........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 1001, 0, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000000001001
Arg3: 0000000000000000
Arg4: fffff70001080000

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


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: AvastSvc.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800030d9767 to fffff80003082640

STACK_TEXT:
fffff880`07105918 fffff800`030d9767 : 00000000`0000001a 00000000`00041284 00000000`00001001 00000000`00000000 : nt!KeBugCheckEx
fffff880`07105920 fffff800`030b46f0 : fffff700`01080000 94700000`12f67867 91b00000`07cbbc66 00000000`0891d378 : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`07105960 fffff800`0306faef : fffffa80`00000000 00000000`0df43fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4e8
fffff880`07105b20 fffff800`030818d3 : ffffffff`ffffffff 00000000`073fe810 00000000`073fe808 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`07105c20 00000000`775214fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`073fe7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775214fa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4ac3
fffff800`030d9767 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4ac3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

Followup: MachineOwner
---------
Corrupt memory, caused by Avast! (avastsvc.exe). Probably related to CPU/Memory configuration set incorrectly or not enough voltage.

( edit )

The other one (third, but middle of the three, they are all from today but at different times) is corrupt. I suggest you:

Open PowerShell or CMD prompt and run sfc /scannow to be sure the crashes didn't corrupt any system files. Then I would also run chkdsk /f /r to check and repair the file system for errors as well.
Edited by GanjaSMK - 3/27/11 at 10:29pm
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: NVIDIA
Overclock.net › Forums › Graphics Cards › NVIDIA › BSOD after 470 install