Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after new Mo-Bo

08 Sep 2010   #1
Krumlov

Windows 7 Home Premium x64
 
 
BSOD after new Mo-Bo

I just got a new mother board to add to my pre-built machine. It is a BioStar TA790GXBE.
I added it to my AMD Phenom II Quad core and my Win7 x64 machine. Running 8GB ram with a GeForce 9800 GT video card.

My machine has been freezing every 5 minutes or has been giving me BSOD's. I just got another one as I type. I have not been able to run through the whole BSOD application which will scan my system, but I have managed to .rar my Minidump and "Performance Report" so that you guys can check them out.

I am almost sure that the BSOD's have to deal with drivers, but which ones I am not sure of. I am also not sure of how to update a driver when the computer won't stay functional for even 5 minutes.

Thank you all for your help!
-Harrison


My System SpecsSystem Spec
.
08 Sep 2010   #2
Capt.Jack Sparrow

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Hello and Welcome !

Seems like the Dump are pointing to one of the Network driver so i would recommend to uninstall the Driver and reinstall it and see if that fixes the issue. Then uninstall Sophos Anti-Virus completely and you could install Microsoft Security Essentials. The crash has happened while you where using Safe Connect it's network access control so uninstall that software as well since the Stacks are pointing to Network drivers.

Uninstall sptd.sys driver use this link DuplexSecure - FAQ it's notorious for BSOD.

Code:
RTKVHD64.sys Thu Dec 10 15:08:13 2009 
Rt64win7.sys Thu Feb 26 14:34:13 2009
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff800333d7fc0, 8, fffff800333d7fc0, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ec0 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff800333d7fc0, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff800333d7fc0, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f90e0
 fffff800333d7fc0 

FAULTING_IP: 
+1e7952f00a1dfdc
fffff800`333d7fc0 ??              ???

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800697e5e0 -- (.trap 0xfffff8800697e5e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000180181f48 rbx=0000000000000000 rcx=fffffa800945ca10
rdx=0000000000000289 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800333d7fc0 rsp=fffff8800697e778 rbp=fffff8800697eca0
 r8=0000000000000001  r9=0000000000000001 r10=0000000000000001
r11=fffff800032c1b60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff800`333d7fc0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800031408f2 to fffff800030c1740

STACK_TEXT:  
fffff880`0697e478 fffff800`031408f2 : 00000000`00000050 fffff800`333d7fc0 00000000`00000008 fffff880`0697e5e0 : nt!KeBugCheckEx
fffff880`0697e480 fffff800`030bf82e : 00000000`00000008 00000000`00000002 fffffa80`09914b00 fffffa80`07b18010 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`0697e5e0 fffff800`333d7fc0 : fffff800`0336a4d4 fffff880`0697eca0 fffff800`00000010 fffff880`00000000 : nt!KiPageFault+0x16e
fffff880`0697e778 fffff800`0336a4d4 : fffff880`0697eca0 fffff800`00000010 fffff880`00000000 fffff880`00000000 : 0xfffff800`333d7fc0
fffff880`0697e780 fffff800`0336a80b : fffffa80`098ecb30 00000001`80181f48 fffffa80`09479b30 00000000`002ec530 : nt!MmCopyVirtualMemory+0x234
fffff880`0697eb30 fffff800`030c0993 : fffffa80`0945ca10 00000000`016ff078 fffff880`0697ebc8 00000000`00340652 : nt!NtReadVirtualMemory+0xff
fffff880`0697ebb0 00000000`76df014a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`016ff058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76df014a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+40ec0
fffff800`031408f2 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+40ec0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40ec0

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40ec0

Followup: MachineOwner
---------
Hope this helps,
Captain
My System SpecsSystem Spec
08 Sep 2010   #3
Krumlov

Windows 7 Home Premium x64
 
 

Freezing is still happening, but more BSOD's than I can keep up with.

Here is new minidump. First 2 are duplicates of last minidump.
My System SpecsSystem Spec
.

08 Sep 2010   #4
Capt.Jack Sparrow

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Hello,

Did you try what i suggested ?

- Captain
My System SpecsSystem Spec
08 Sep 2010   #5
Capt.Jack Sparrow

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Hello,

This time it has pointing to nvlddmkm.sys i.e nVidia so follow this link and cleanup the Drivers and reinstall it nVidia Driver Cleanup Guide !! « Captain Debugger

Enable Driver Verifier Using Driver Verifier to identify issues with Drivers

Hope this helps,
Captain
My System SpecsSystem Spec
08 Sep 2010   #6
Krumlov

Windows 7 Home Premium x64
 
 

Driver verifier is telling me again and again that its my nVidia drivers that are throwing the BSOD. I will check that now.

And yes I reinstalled my network drivers as well as removed stpd.sys
My System SpecsSystem Spec
08 Sep 2010   #7
Capt.Jack Sparrow

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Quote:

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
My System SpecsSystem Spec
08 Sep 2010   #8
Krumlov

Windows 7 Home Premium x64
 
 

Right now my problem comes from the fact that the computer can't go 5 minutes without freezing up. No BSOD's are happening because I just clean installed Win7. Clear disk, etc. But it keeps freezing up on a fresh computer which is bugging me. My thought is that the "auto-drivers" are messed up, so I need to replace the ones that are necessary for the computer to run.
My System SpecsSystem Spec
08 Sep 2010   #9
Capt.Jack Sparrow

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Quote   Quote: Originally Posted by Krumlov View Post
Right now my problem comes from the fact that the computer can't go 5 minutes without freezing up. No BSOD's are happening because I just clean installed Win7. Clear disk, etc. But it keeps freezing up on a fresh computer which is bugging me. My thought is that the "auto-drivers" are messed up, so I need to replace the ones that are necessary for the computer to run.
Did you ran the stress test ?
My System SpecsSystem Spec
08 Sep 2010   #10
Krumlov

Windows 7 Home Premium x64
 
 

The stress test is too hold for my system. I need a x64 version to use.
My System SpecsSystem Spec
Reply

 BSOD after new Mo-Bo




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 03:39.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App