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 and driver blackouts

03 Mar 2012   #1

Windows 7 Home Premium x64
BSOD and driver blackouts

on Wednesday, I did a major upgrade to my PC. Now I am getting occasional BSOD's. Another strange thing that is happening is that the drivers (display, network, etc.) will seemingly stop working, then come back online in 30 seconds or so, but windows shows no notification of them not working. Any assistance diagnosing these issues would be appreciated.

I have run a 5-pass, high quality memory test and found no errors.

Specs before upgrade:
Asus P5LP-LE Limestone
Intel Pentium D 820
250GB Caviar HDD
Conexant Falcon II NTSC Tuner
Ralink Turbo WiFi

Specs now:
Gigabye 870A-USB3
AMD Phenom II X6 1035T
8GB DDR3 RAM (PNY optima)
250GB Caviar HDD
Conexant Falcon II NTSC Tuner
Ralink Turbo WiFi

I have another 4GB of the same type RAM shipping right now, along with a SATA3 DVD drive.

My System SpecsSystem Spec

03 Mar 2012   #2

Windows 7 Home Premium 64 Bit

Possible out of date drivers:
PS2	fffff880`0407f000	fffff880`04088000	Thu Sep 07 16:49:03 2006 (4500a1df)	0000d72b		PS2.sys
AtiPcie	fffff880`0146d000	fffff880`01475000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys
PxHlpa64	fffff880`010ca000	fffff880`010d5e00	Tue Jun 23 17:16:35 2009 (4a416253)	000111b7		PxHlpa64.sys

  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\halomademeapc\Windows_NT6_BSOD_jcgriff2\030312-46332-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache* Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03001000 PsLoadedModuleList = 0xfffff800`0323ee70 Debug session time: Sat Mar 3 17:44:20.582 2012 (UTC - 7:00) System Uptime: 0 days 0:03:44.564 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa80054ee5c0, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+338c6 ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa80054ee5c0 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: Steam.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800030e4efe to fffff800030715c0 STACK_TEXT: fffff880`084fb8c8 fffff800`030e4efe : 00000000`0000001a 00000000`00041790 fffffa80`054ee5c0 00000000`0000ffff : nt!KeBugCheckEx fffff880`084fb8d0 fffff800`03044ba7 : ffffffff`00000000 00000000`0327ffff fffffa80`00000000 fffffa80`0a71ab60 : nt! ?? ::FNODOBFM::`string'+0x338c6 fffff880`084fba90 fffff800`03353a8b : fffff8a0`026a8060 00000000`00000001 00000000`00000000 fffffa80`0a71ab60 : nt!MmCleanProcessAddressSpace+0x62f fffff880`084fbae0 fffff800`0332b35b : 00000000`00000000 00000000`00000001 00000000`7efdb000 00000000`00000000 : nt!PspExitThread+0x92f fffff880`084fbba0 fffff800`03070813 : fffffa80`0a642b30 fffff880`00000000 00000000`7efdb000 fffffa80`0a71ab60 : nt!NtTerminateProcess+0x25b fffff880`084fbc20 00000000`76fef97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fef97a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+338c6 fffff800`030e4efe cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+338c6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+338c6 BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+338c6 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\halomademeapc\Windows_NT6_BSOD_jcgriff2\030312-33134-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache* Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`0300e000 PsLoadedModuleList = 0xfffff800`0324be70 Debug session time: Sat Mar 3 17:39:42.529 2012 (UTC - 7:00) System Uptime: 0 days 1:19:27.871 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8a0052256f0, 0, fffff88001260260, 0} Could not read faulting driver name Probably caused by : Ntfs.sys ( Ntfs!memmove+250 ) 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: fffff8a0052256f0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff88001260260, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b60e0 fffff8a0052256f0 FAULTING_IP: Ntfs!memmove+250 fffff880`01260260 488b440af8 mov rax,qword ptr [rdx+rcx-8] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88008ba9cf0 -- (.trap 0xfffff88008ba9cf0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000048 rbx=0000000000000000 rcx=fffff9801fa96000 rdx=ffffff1fe578f6f8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88001260260 rsp=fffff88008ba9e88 rbp=fffff88008baa140 r8=0000000000000048 r9=0000000000000002 r10=fffff8a0052256b0 r11=fffff9801fa95fb8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy Ntfs!memmove+0x250: fffff880`01260260 488b440af8 mov rax,qword ptr [rdx+rcx-8] ds:fffff8a0`052256f0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800030fedf4 to fffff8000307e5c0 STACK_TEXT: fffff880`08ba9b88 fffff800`030fedf4 : 00000000`00000050 fffff8a0`052256f0 00000000`00000000 fffff880`08ba9cf0 : nt!KeBugCheckEx fffff880`08ba9b90 fffff800`0307c6ae : 00000000`00000000 00000000`d06f2bec 00000000`00000000 fffff8a0`00228670 : nt! ?? ::FNODOBFM::`string'+0x426f7 fffff880`08ba9cf0 fffff880`01260260 : fffff880`01306124 00000000`00000000 fffff880`08baa130 00000000`00001028 : nt!KiPageFault+0x16e fffff880`08ba9e88 fffff880`01306124 : 00000000`00000000 fffff880`08baa130 00000000`00001028 00000000`00000000 : Ntfs!memmove+0x250 fffff880`08ba9e90 fffff880`0130e5a5 : fffff8a0`00000048 fffff8a0`0021a700 fffff880`08baa900 fffff980`00000fb8 : Ntfs!LfsWriteLogRecordIntoLogPage+0x5e4 fffff880`08ba9f30 fffff880`01308b26 : fffff8a0`03661a90 fffffa80`00000002 00000000`d06f29d9 fffff880`08baa180 : Ntfs!LfsWrite+0x145 fffff880`08ba9ff0 fffff880`013188e9 : fffff880`08baa770 fffffa80`07cbeac0 00000000`042dd000 fffff8a0`001bf140 : Ntfs!NtfsWriteLog+0x466 fffff880`08baa240 fffff880`0131a250 : fffff880`08baa770 fffff880`08baa701 00000000`46706000 00000000`01bd8000 : Ntfs!NtOfsPutData+0x229 fffff880`08baa370 fffff880`01319d37 : fffff880`08baa770 01ccf752`dc126a00 fffff880`08baa770 00000000`00000000 : Ntfs!NtfsWriteFcbUsnRecordToJournal+0xa8 fffff880`08baa430 fffff880`01306b32 : 00000000`00000001 fffff8a0`0364e680 fffff8a0`001bf140 fffff8a0`03661a90 : Ntfs!NtfsWriteUsnJournalChanges+0x187 fffff880`08baa4b0 fffff880`012cbdc2 : 00000000`00000000 00000000`00000000 fffff880`08baa770 fffff880`08baa770 : Ntfs!NtfsCheckpointCurrentTransaction+0x72 fffff880`08baa4e0 fffff880`012cb980 : fffff880`08baa770 fffff8a0`03661e10 fffff8a0`03661a90 fffff8a0`03661e00 : Ntfs!NtfsModifySecurity+0x292 fffff880`08baa620 fffff880`012e6a69 : fffff880`08baa770 fffffa80`0f36cc10 fffff8a0`03661a90 fffffa80`08060180 : Ntfs!NtfsCommonSetSecurityInfo+0x150 fffff880`08baa6d0 fffff880`012e6fe1 : fffff880`08baa770 fffffa80`0f36cc10 fffffa80`0f36cc10 00000000`00000000 : Ntfs!NtfsFsdDispatchSwitch+0x169 fffff880`08baa750 fffff880`0101f23f : fffff880`08baa9f0 fffff880`0101ebe9 fffff880`08baa900 fffff880`0101f215 : Ntfs!NtfsFsdDispatch+0x2d fffff880`08baa940 fffff880`0101d6df : fffffa80`07c89950 00000000`00000000 fffffa80`07c89900 fffffa80`0f36cc10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`08baa9d0 fffff800`033620e4 : fffffa80`0d6a39c0 00000000`00000000 00000000`00000000 fffffa80`0f36cc10 : fltmgr!FltpDispatch+0xcf fffff880`08baaa30 fffff800`0331941a : 00000000`00000000 00000000`03841e94 fffff880`08baab58 fffff8a0`215c0200 : nt!IopGetSetSecurityObject+0x174 fffff880`08baaaf0 fffff800`033197a8 : fffffa80`06e90000 00000000`00000004 00000000`00000001 fffffa80`0a880f01 : nt!ObSetSecurityObjectByPointer+0x5a fffff880`08baab50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtSetSecurityObject+0x108 STACK_COMMAND: kb FOLLOWUP_IP: Ntfs!memmove+250 fffff880`01260260 488b440af8 mov rax,qword ptr [rdx+rcx-8] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: Ntfs!memmove+250 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d79996d FAILURE_BUCKET_ID: X64_0x50_Ntfs!memmove+250 BUCKET_ID: X64_0x50_Ntfs!memmove+250 Followup: MachineOwner ---------
  1. Possible causes are Memory problems... Drivers...
  2. Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.
  • If you are overclocking any hardware, please stop.

  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

  • Sometimes Memtest86+ needs to be run a few times (seven passes each) to find errors. Run the boot version of Memtest86+ again, paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

  • Install all Windows updates. You have not yet installed Service Pack 1.

  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

Also, when I see driver issues like this, I usually ask if the person has used an automated registry cleaner. Have you by chance done so?
My System SpecsSystem Spec
03 Mar 2012   #3

Windows 7 Home Premium x64

I have not run a registry cleaner, but I typically use CCleaner for that. I've been having difficulty getting SP1 to install, so I'm downloading the full ISO that includes SP1 and will be doing a repair install of that first. I'll post back after that's done.

oh and I already ran a 5-pass extended memory test with the tool built in to windows.
My System SpecsSystem Spec

03 Mar 2012   #4

Windows 7 Home Premium 64 Bit

Alright, that may resolve the driver issues as well, so let us know if you still need help after the repair install.

I also recommend not using the registry cleaning part of CCleaner. While CCleaner is safer than most, I have had the occasional registry clean by CCleaner render a system completely useless. Many of us on these forums believe that automated registry cleaning should be avoided as it breaks the system eventually and does not offer any performance gain in most systems. In the systems that it does help, there are safer methods for fixing the registry than blindly relying on an automated tool to do tweaks to the registry. If you need help with registry errors, you can post within this forum or within and receive help from people who are familiar with the registry.
My System SpecsSystem Spec
04 Mar 2012   #5

Windows 7 Home Premium x64

I think that my copy of the SP1 ISO was corrupted, so the installation crashed and ruined my existing install. I had to reinstall Windows 7, and this time the first thing I did was install SP1. I'll let Windows Update get all of the drivers this time to see if that helps. I'm just not looking forwards to re-downloading my Steam library for the second time this week.
My System SpecsSystem Spec
04 Mar 2012   #6

Windows 7 Home Premium x64

okay, this time when I booted up, Windows Explorer would stop working every time I tried to pull it up. I've installed Ubuntu 11.10 to use as a backup when Windows doesn't work, that way I can still get assignments and stuff done while this is going on. I did, however, successfully, get it to SP1 with drivers and most updates.
My System SpecsSystem Spec
04 Mar 2012   #7

Windows 7 Home Premium 64 Bit

Steam has a backup feature to put your library on an external drive. That is what I do with my games.

As to your explorer crashes, try Troubleshooting Explorer.exe Crashing Issues

For step 1. in that thread, another similar method is Troubleshoot Application Conflicts by Performing a Clean Startup

For step 3. there is now a Windows 7 version: Fix a corrupted user profile.

Step 5. may also be useful given that you have already tried a clean install...
My System SpecsSystem Spec
04 Mar 2012   #8

Windows 7 Home Premium x64

I copied the program files folder for steam from Windows.old and it worked fine that way. After restarting windows explorer and everything started acting normal again. I was doing fine, just humming along, then I got a BSOD while streaming TF2.
and then while typing this I had another one of those driver blackouts. I'll try that clean startup thing soon.
My System SpecsSystem Spec
08 Mar 2012   #9

Windows 7 Home Premium x64

I haven't had any more of those "driver blackouts", but I have been getting bluescreens in the following scenarios. This does not happen every time I try the action, but the ones listed have corresponded with a BSOD on at least one instance.
Starting Burnout Paradise
Plugging in Headphones to the front jack
Resuming from sleep mode
Rendering in 3ds max 2011 with Mental Ray

there have also been bsod's that don't appear to correspond by a user action and occur "out of the blue" (pun not intended).

The BSOD's have been primarily

(I may have mistyped one)

I will re-run the analysis tool and post back with the results when I get the chance.
My System SpecsSystem Spec
08 Mar 2012   #10

Windows 7 Home Premium 64 Bit

When you have crashes that have different error types as you do, and they all point to a memory problem, it is most likely a hardware concern. Have you had a chance to run the memory tests yet?
My System SpecsSystem Spec

 BSOD and driver blackouts

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 09:23 AM.
Twitter Facebook Google+

Windows 7 Forums

Seven Forums Android App Seven Forums IOS App

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33