Multiple BSOD on New Build.

[Jujx]

Tried the overclocking tool that came with my motherboard but have since then reset the settings and am no longer overclocked.

Been getting ntfs BSODs and im not sure how to stop them. Would really appreciate some help.

Windows 7 x64 build 7600.16539.amd64fre.win7_gdr.1000226-1909 version 6.1
AMD Phenom II X6 1090T Black Edition 3.2Ghz CPU
Coolmax 950W 3 Way SLI Certified Modular PSU
LG 22X DVDRW SATA w/Lightscribe OEM
EVGA GeForce GTX 480 SC 1536MB GDDR5 PCIe SLI (should've gone with ATI!!! =[[[)
ASUS Crosshair IV Formula AMD 890FX AM3 M
OCZ 8GB DDR3 PC10666 1333MHZ 8192MB (2 X 4GB)
Cooler Master HAF 932 Full Tower Black Case
Cooler Master V8 CPU Fan 1366/775/940/AM2/AM2+
Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G

Also I used WhoCrash to bring up the logs.

This is what it gave me:

[FONT=Segoe UI, Arial]Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]On Tue 7/20/2010 6:17:32 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002E7C4E1, 0xFFFFF880031683A8, 0xFFFFF88003167C10)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
Dump file: C:\Windows\Minidump\072010-23883-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Tue 7/20/2010 5:47:00 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DBE000, 0xFFFFF8800317D828, 0xFFFFF8800317D080)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
Dump file: C:\Windows\Minidump\072010-22120-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Tue 7/20/2010 5:36:07 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT]
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000856A9, 0xFFFFF880022B1F10, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
Dump file: C:\Windows\Minidump\072010-21278-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Tue 7/20/2010 4:29:23 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT]
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88005B95508, 0xFFFFF88005B94D60, 0xFFFFF80002A910C4)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/FONT]
Dump file: C:\Windows\Minidump\072010-15288-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

Quick note: Built two of these machines the only difference between them are the GPUs. The other machine has two 4870s crossfired. All other hardware exactly the same and it even overclocked to 4.7 with the auto utility. Also same version of windows which I got burned from a friend and no problems with that machine whatsoever.

Let me know if you guys need more info or if I gave a little too much info.

Thanks!
[/FONT]

 

[Capt.Jack Sparrow]

Hello !! Welcome to SF !!

Seems like lot of issues are going on that why you seen different causes. First of all uninstall all the Asus utilities from your System there were few drivers that cause trouble. Reset the BIOS to default settings so we can make sure the Overclocking is not causing any issues.

Uninstall your Marvell-Yukon-Gigabit-Ethernet-Driver and reinstall the Driver since there were few crashes on it.

Run a Hardware Diagnostic to make sure everything is O.K. : Hardware Diagnostic !! « Captain Debugger

Enable Driver Verifier : http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Good Luck,
Captain

 

[Jujx]

did a clean and then tried to install the nvidia drivers and runonce crashed on me then the nvidia driver crash =[

 

[Jujx]

At 8 dumps now 2 of them after I turned on verifier.


[FONT=Segoe UI, Arial]On Tue 7/20/2010 10:05:26 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
Dump file: C:\Windows\Minidump\072010-32822-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Tue 7/20/2010 9:58:50 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002E8F7B6)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Dump file: C:\Windows\Minidump\072010-23041-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Tue 7/20/2010 9:40:17 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x50 (0xFFFFF95FFFCC2000, 0x8, 0xFFFFF95FFFCC2000, 0x5)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
Dump file: C:\Windows\Minidump\072010-23150-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Tue 7/20/2010 9:38:37 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT]
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003F7E478, 0xFFFFF88003F7DCE0, 0xFFFFF880012C350D)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/FONT]
Dump file: C:\Windows\Minidump\072010-23478-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

 

[Jujx]

Nvidia drivers installed correctly. Hardware doesn't seem to be the issue. Waiting on more dumps.

 

[Jujx]

Sorry about that. Heres the minidump. Thanks!

 

[Capt.Jack Sparrow]

Sorry about that. Heres the minidump. Thanks!

Hello,

Seems like VMfilt64.sys is causing the crash which i think it belongs to VIA Audio Driver. If so uninstall it and rebooted the System and reinstall it.

I'm assuming that you have ran the Memory test with MemTest86+ 6 passes atleast.

One more question what Internet Security software are you using ??


Download this http://live.sysinternals.com/sigcheck.exe save it your C Drive.

Start | CMD | Right Click and Run as administrator

Then type in cd\ then Hit enter

 sigcheck -u -e c:\windows\system32 > C:\Sicheck.txt

Hit Enter

It might take a while then it will create a file under C Drive Upload that file it will give us a lit of Drivers that is not verified.

Good Luck,
Captain

 

[Jujx]

I'm not using any internet security software yet. the system is less than a week old and ive been busy trying to weed out the problems. The ram checked out fine before my last wipe and install of windows. Also when I went to uninstall that audio driver I noticed that there are four Nvidia HD audio drivers installed there as well? Could they have come packaged with the video driver when I downloaded and installed from the nvidia site?

 

[Jujx]

heres the sicheck. Thanks again!

 

[Jujx]

Ran great for a while. I used the pc like I usually do a pc. Installed a game I bought a while ago from direct2drive (Unreal tournament 3). navigated through the menus just fine. When I tried to join a server i got the following dump. Check it out. Thanks!

EDIT: Tried the game again and no blue screen this time. minimal lockup when menu screens switch. Could my graphics card be dying?

 

[Jujx]

This dump happened 8 minutes after the last one I posted. Have been running smoothly since then. About 6-7 hours. Could someone take a quick look at this please? Driver verifier still enabled. Thanks!

 

[Jujx]

Latest three minidumps. Need some major help! please!

 

[Jujx]

Can anyone tell me if I formatted my post wrong or didnt include a necessary file? Wondering why everyone else is getting replies on their threads and im not. >.<

 

[Tews]

Looking now...

 

[Tews]

All three .dmp files are the same and blame ntkrnlmp.exe as the cause.. As this is a core system file and not the real cause.

Enable driver verifer by following these instructions..

here's the procedure:

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

You also have a BugCheck 3B, {c0000005, fffff80002e87805, fffff88006d79fa0, 0} which is a memory exception .... Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

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


Loading Dump File [C:\Windows\Minidump\072110-18408-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`03051e50
Debug session time: Wed Jul 21 01:09:29.753 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:22.111
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e87805, fffff88006d79fa0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

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

 

[Jujx]

Does Verifier stay enabled until manually being turned off? if so I enabled and have been running with it since Capt. Sparrow recommended it. I re ran a system health report and BSOD and included it with this reply. Thank you so much for your reply Tews.

BTW: My system has been significantly more stable since removing the software Capt. Recommended.

 

[Jonathan_King]

It appears your Yukon network adapter drivers are the cause. Please uninstall them and install a fresh, updated copy.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 05:09:28.833 2010 (UTC - 4:00)
System Uptime: 0 days 0:40:14.830
BugCheck 1E, {ffffffffc0000005, fffff8800629b8c0, 0, 0}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
Probably caused by : yk62x64.sys ( yk62x64+18dbe )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 02:12:59.073 2010 (UTC - 4:00)
System Uptime: 0 days 0:52:37.431
BugCheck 1000007E, {ffffffffc0000005, fffff8000311f28c, fffff880031689c8, fffff88003168230}
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayCloseWorker+98 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 01:09:29.753 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:22.111
BugCheck 3B, {c0000005, fffff80002e87805, fffff88006d79fa0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[Jujx]

Should I do the memtest before or after the verifier?

 

[Tews]

First remove the driver that Jonathan has suggested, then see what happens... It may be that driver verifier will not be needed... then run memtest..

 

[Jujx]

I removed and reinstalled it from the MOBO setup CD.