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 Transferring Files, 0x1A and 0x0A

15 Apr 2012   #1

Windows 7 Professional SP1 64bit
BSOD Transferring Files, 0x1A and 0x0A

Hi All,

I built this new Win7 Pro x64 system a month ago, and have been having multiple BSODs every day. It usually happens when I'm downloading files, or using newsgroups. I'm pretty technically savvy, and here's what I've tried so far:
  • Updating BIOS
  • Different versions of drivers (mfr website vs MS Update)
  • Moving HDDs to different SATA ports
  • Ran MemTest86+ for 18 hours

I can sometimes run for 8 hours without one, other times it happens within half an hour of booting. The BSODs are usually MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL, which makes me hope that it might be a driver issue or something besides the RAM/Motherboard.

Any help would be greatly appreciated!

My System SpecsSystem Spec
17 Apr 2012   #2

Windows 7 Home Premium 64 Bit

Problem Devices:
Universal Serial Bus (USB) Controller	PCI\VEN_1B6F&DEV_7023&SUBSYS_50071458&REV_01\4&18803EC9&0&00E4	The drivers for this device are not installed.
Universal Serial Bus (USB) Controller	PCI\VEN_1B6F&DEV_7023&SUBSYS_50071458&REV_01\4&1B0D22A2&0&00E5	The drivers for this device are not installed.
These are important to have installed, so please fill out your system specs so we may help find them. Use System Info - See Your System Specs to fill out your specs.

Is this the support site for your board: GIGABYTE - Motherboard - Socket 1155 - GA-P67X-UD3-B3 (rev. 1.0) ?

Make sure your Chipset and USB 3.0 drivers are installed from that site.

Security Software (this is just to make sure it is installed and working properly; nothing needs to be done with this information at this time):
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	844	8	200	1380	15/04/2012 7:01 PM	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	864	8	200	1380	15/04/2012 7:01 PM	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	2432	8	200	1380	15/04/2012 7:05 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 2:35 PM
sbiectrl.exe	c:\program files\sandboxie\sbiectrl.exe	2032	8	200	1380	15/04/2012 7:05 PM	653.27 KB (668,944 bytes)	10/04/2012 4:17 AM
sbiesvc.exe	c:\program files\sandboxie\sbiesvc.exe	1108	8	200	1380	15/04/2012 7:01 PM	95.27 KB (97,552 bytes)	10/04/2012 4:17 AM

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Foosh\Windows_NT6_BSOD_jcgriff2\041512-6879-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c9b650
Debug session time: Sun Apr 15 18:59:55.335 2012 (UTC - 6:00)
System Uptime: 0 days 1:34:02.537
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff6800002b6e8, 9ec0000001919867, fffff6a00002b6e8}

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

Followup: MachineOwner

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

    # Any other values for parameter 1 must be individually examined.
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff6800002b6e8
Arg3: 9ec0000001919867
Arg4: fffff6a00002b6e8

Debugging Details:

BUGCHECK_STR:  0x1a_403





LAST_CONTROL_TRANSFER:  from fffff80002a7bc56 to fffff80002ad3c80

fffff880`08dfb668 fffff800`02a7bc56 : 00000000`0000001a 00000000`00000403 fffff680`0002b6e8 9ec00000`01919867 : nt!KeBugCheckEx
fffff880`08dfb670 fffff800`02b05017 : 00000000`00000000 fffff680`0002ba58 fffffa80`07cd7b30 fffffa80`00000002 : nt! ?? ::FNODOBFM::`string'+0x3266c
fffff880`08dfb820 fffff800`02ac04bf : fffffa80`00000000 00000000`0574bfff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`08dfb9e0 fffff800`02ad2f13 : ffffffff`ffffffff 00000000`04bce810 00000000`04bce808 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`08dfbae0 00000000`77a014fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04bce7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a014fa


nt! ?? ::FNODOBFM::`string'+3266c
fffff800`02a7bc56 cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3266c

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3266c

BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3266c

Followup: MachineOwner
Possible causes for the above crash are Memory problems... Drivers...

The crash was related to SABnzbd.exe; uninstall the software to test. If the software is required, re-install the software after uninstalling it. It's possible the software is corrupted.

  • If you are overclocking any hardware, please stop.

  • Run the boot version of Memtest86+ 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.

  • 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. In Windows 7:
    • Click the Start Menu
    • Type verifier in Search programs and files (do not hit enter)
    • Right click verifier and click Run as administrator
    • Put a tick in Create custom settings (for code developers) and click next
    • Put a tick in Select individual settings from a full list and click next
    • Set up the individual settings as in the image and click next
      Attachment 207625
    • Put a tick in Select driver names from a list
    • Put a tick next to all non-Microsoft drivers.
    • Click Finish.
    • Restart your computer.

    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.

    When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
    verifier /reset
    -> Restart your computer.
My System SpecsSystem Spec

 BSOD Transferring Files, 0x1A and 0x0A

Thread Tools

Similar help and support threads
Thread Forum
BSOD happened when just transferring some files
Hi there, any contribution would be appreciated. It's been two weeks, BSOD happened about twice per week when just transferring some files. Thank you.
BSOD Help and Support
Multiple BSOD 0x0a, 0x1a, 0x4e, 0x50, 0x3b (IRQL, SYS_SERV_EXC, etc)
Hi, I have a Dell Optiplex 9020 Lab with about 30 computers in there. The computers are running Windows 7 64 bit. There is one computer that has about 5 different types of bluescreens happening over the last few months. I attached a SF Diag Tool Zip. Any help on what could be the problem? I...
BSOD Help and Support
BSODs in BF4 and other games. Ntoskrnl.exe 0x1a, 0x0a, 0x3b, ntfs.sys
Hello, I get random BSODs, especially when playing games, like Battlefield 4 and Alien: Isolation. When it doesn't blue screen, the games often stop working with an error message and quit to Windows. I tried using Bluescreen viewer to find out which driver was causing it, but the errors are varied...
BSOD Help and Support
BSOD - Random 0x0A, 0x1A
Hi, i have been getting BSOD lately and not sure what has caused them normally i can google it and work out the problem but havent been able to fix this so thinking it could be hardware as i cant recall installing anything lately (not saying i havent though) i also received a 0x7E? i think ...
BSOD Help and Support
0x0a & 0x1a BSODs. Frequent and Frustrating to Fix
Greetings gentlemen. Allow me to explain to thee my current dilemma. As the title suggests the most common of Bsod's my PC is suffering are bccode 0a's and 1a's. I have done my research into these stop errors and have learned a fair bit I must say. As for when these crashes happen? Well. 0a's...
BSOD Help and Support

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