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 when doing nothing (afk)

12 Jul 2014   #1

windows 7 Home 64bit
BSOD when doing nothing (afk)

hi, so a few days ago i got some blue screens when i ran avast, so i decided to uninstall it to see if it was the problem, for a moment everything was fine but now i get blue screens when i don't do anything for a set amount of time ( usually 15 minutes) . So i don't really know what could be the problem, if anyone could help me it would be great .


My System SpecsSystem Spec
12 Jul 2014   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Welcome to the forum.

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

Loading Dump File [C:\Users\admin\Downloads\RATON-PC-12_07_2014_140730,08\071214-488064-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03406000 PsLoadedModuleList = 0xfffff800`03649890
Debug session time: Sat Jul 12 05:59:09.296 2014 (UTC + 6:00)
System Uptime: 0 days 3:29:26.623
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc500a9098, ffffffffc000000e, 50bc8880, fffff8a015213000}

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

Followup: MachineOwner

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

The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arg1: fffff6fc500a9098, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000050bc8880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a015213000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e



PROCESS_NAME:  uTorrent.exe


DEVICE_OBJECT: fffffa8009f496f0

TRAP_FRAME:  fffff88009d8a0a0 -- (.trap 0xfffff88009d8a0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a015213000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff98050e00000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034a6fac rsp=fffff88009d8a230 rbp=fffff88009d8a280
 r8=0000098000000000  r9=000000000dd00020 r10=0000058000000000
r11=0000000029fc0000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff800`034a6fac 488b38          mov     rdi,qword ptr [rax] ds:fffff8a0`15213000=0000000000000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034ee752 to fffff8000347bbc0

fffff880`09d89d88 fffff800`034ee752 : 00000000`0000007a fffff6fc`500a9098 ffffffff`c000000e 00000000`50bc8880 : nt!KeBugCheckEx
fffff880`09d89d90 fffff800`034a291f : fffffa80`0a4ca280 fffff880`09d89f00 fffff800`036b6600 fffffa80`0a4ca280 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`09d89e70 fffff800`034891b9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`034c6b53 : nt!MiIssueHardFault+0x28b
fffff880`09d89f40 fffff800`03479cee : 00000000`00000000 fffff8a0`15213000 fffffa80`03a80d00 00000000`00000000 : nt!MmAccessFault+0x1399
fffff880`09d8a0a0 fffff800`034a6fac : 00000000`00000000 fffff880`09d8a340 00000000`00000001 fffffa80`0d042650 : nt!KiPageFault+0x16e
fffff880`09d8a230 fffff800`034a408e : fffff980`50e00000 00000000`0dd00020 fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0x1dc
fffff880`09d8a420 fffff800`034a4644 : fffffa80`05a7fe00 00000000`0dd00020 fffff880`09d8a560 00000000`001e8000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`09d8a510 fffff880`018616cd : 00000000`00000000 fffff880`09d8a780 fffffa80`06071e40 00000000`00000000 : nt!CcCopyWrite+0x194
fffff880`09d8a5a0 fffff880`01861c93 : fffffa80`06071e40 fffffa80`09f492c0 fffff880`09d8a700 fffff880`09d8a700 : Ntfs!NtfsCommonWrite+0x3399
fffff880`09d8a750 fffff880`017a6bcf : fffffa80`09f496a8 fffffa80`09f492c0 fffffa80`0befb780 00000000`00000001 : Ntfs!NtfsFsdWrite+0x1c3
fffff880`09d8a810 fffff880`017a56df : fffffa80`086d3c90 00000000`00000001 fffffa80`086d3c00 fffffa80`09f492c0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`09d8a8a0 fffff800`03785c3b : 00000000`00000001 fffffa80`0b4167e0 00000000`00000001 fffffa80`09f492c0 : fltmgr!FltpDispatch+0xcf
fffff880`09d8a900 fffff800`03790643 : fffffa80`09f496f0 00000000`00000000 fffffa80`0b4167e0 fffff880`03565180 : nt!IopSynchronousServiceTail+0xfb
fffff880`09d8a970 fffff800`0347ae53 : ffffffff`00000001 00000000`00000000 00000000`00000000 00000000`03f5fd30 : nt!NtWriteFile+0x7e2
fffff880`09d8aa70 00000000`74a52e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0378f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a52e09


nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`034ee752 cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36c1a

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+36c1a

BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+36c1a

Followup: MachineOwner
Run Disk Check on your Hard Drive for file system errors and bad sectors on it:Upload a screenshot of your hard disk using Crystal Disk Info:Make a hard drive test from the hard drive manufacturers website:Test your Hard Drive with SeaTools:Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Memtest should be done overnight.
My System SpecsSystem Spec

 BSOD when doing nothing (afk)

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 00:05.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App