Windows 7 freezes randomly, ends up in stop Error-BSOD/force-resets

docsanchez · 14 Oct 2013

Hello!
This is my first Post so I'm trying not to forget anything.
I have attached the zip folder from the SF_diagnostics tool, in the folder you should find 2 of my latest mindumps - my big hope is that someone will look at the zipfile and tell me exactly what my problem is :)

Crash description:

Usually my windows just starts to slowly freeze, this often starts by google Chrome not responding - then my desktop will also begin to be unresponsive. Sometimes it recovers but most of the time nothing responds (except skype when in a call - this seems to last forever) and I am forced to do a hard reset - UNLESS the computer goes into bluescreen mode by itself, which happened twice in the last week, but I was forced to reset the computer much more often.

A curious thing is after this happens, my windows won't boot up, instead it will give me a "disk read error - press ctrl+alt+delete to restart" error, which I have to solve by unplugging the power, waiting a bit and then booting up again.

Now the thing is, I have replaced most of my PC's hardware a few months ago so most of it is pretty new (the Mobo, the CPU and the RAM) and the only "old" parts from my previous computer are the PSU, the DVD drive and the Hard Disk Drive (which was fairly new even before I replaced my computer parts) - and my old computer, even though I have done a fresh clean win7 install after replacing all the parts, crashed and froze in a very similar manner - how is that even possible?

I have tried using firefox instead of chrome, no effect. I also removed my graphics card and I am currently using the onboard chip, but it is still giving me those freezes.

I am really starting to despair as replacing the hardware did not solve my problem at all.

Please help me, I am really out of ideas and I fear consulting a technician that will just charge a lot of money and not even end up fixing the problem.

Best regards,

doc

koolkat77 · 15 Oct 2013

Remove:

Code:

Start Menu\Programs\DAEMON Tools Lite    Public:Start Menu\Programs\DAEMON Tools Lite    Public

Tip

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows 7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

Remove:

Code:

Start Menu\Programs\Avira    Public:Start Menu\Programs\Avira    Public
Start Menu\Programs\Avira\Avira Desktop    Public:Start Menu\Programs\Avira\Avira Desktop    Public

Information

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Microsoft Security Essentials
- uninstall the antivirus software from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of the antivirus software using one of these free tools: Antivirus Uninstallers
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Then please run these tests and report back the results
------------------------
1. SFC /scannow to check windows for corruption - SFC /SCANNOW - System File Checker
2. Disk check for errors on the hard drive - Run Disk Check in Windows 7
3. Troubleshoot apps by a clean boot - Performing a Clean Startup
4. Memtest86+ paying attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Code:

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


Loading Dump File [C:\Users\USER\Downloads\docsanchez\SF_15-10-2013\101413-15381-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e98670
Debug session time: Mon Oct 14 23:25:10.592 2013 (UTC + 6:00)
System Uptime: 0 days 4:46:35.888
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff8a0013b57b0, ffffffffc000000e, 14a0bf8c0, fffff88009a486b0}

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

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
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
KERNEL_STACK_INPAGE_ERROR.
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.
Arguments:
Arg1: fffff8a0013b57b0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000014a0bf8c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88009a486b0, 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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007a5d3b0 -- (.trap 0xfffff88007a5d3b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88009a40428 rbx=0000000000000000 rcx=fffff88009a486b0
rdx=fffff88009a403a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030a8bb4 rsp=fffff88007a5d540 rbp=0000000000006ea8
 r8=00000000ffffffff  r9=fffff88009a401c0 r10=0000000000000001
r11=fffff88007a5d4c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!RtlFindMessage+0xa4:
fffff800`030a8bb4 0fb701          movzx   eax,word ptr [rcx] ds:fffff880`09a486b0=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d3d742 to fffff80002ccac00

STACK_TEXT:  
fffff880`07a5d098 fffff800`02d3d742 : 00000000`0000007a fffff8a0`013b57b0 ffffffff`c000000e 00000001`4a0bf8c0 : nt!KeBugCheckEx
fffff880`07a5d0a0 fffff800`02cf191f : fffffa80`08b7dc70 fffff880`07a5d210 fffff800`02f05540 fffffa80`08b7dc70 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`07a5d180 fffff800`02cd81b9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`07a5d570 : nt!MiIssueHardFault+0x28b
fffff880`07a5d250 fffff800`02cc8d2e : 00000000`00000000 fffff880`09a486b0 fffff880`09a40000 00000000`0000007d : nt!MmAccessFault+0x1399
fffff880`07a5d3b0 fffff800`030a8bb4 : fffff880`0001cff8 00000000`00006a9d 00000000`00006ea8 00000000`00200040 : nt!KiPageFault+0x16e
fffff880`07a5d540 fffff880`0127cd12 : 00000000`00006a9d 00000000`00000000 00000000`00000000 fffff880`0126e630 : nt!RtlFindMessage+0xa4
fffff880`07a5d5b0 fffff880`0127ce8e : 00000000`0000dd5e fffff880`07a5d700 fffffa80`00000002 fffffa80`097b90e2 : Ntfs!NtfsRepairLogGetMsg+0x4a2
fffff880`07a5d6b0 fffff880`0127e5e9 : fffff880`07a5d8a0 00000000`0000dd5e fffffa80`097ab2a2 fffff880`07a5d930 : Ntfs!NtfsRepairLogExpandMsgs+0x8e
fffff880`07a5d760 fffff880`0128e6aa : fffff880`07a5d8b8 00000000`00000080 01cec913`14929ac8 00010000`00002e00 : Ntfs!NtfsRepairPrepareEventLogData+0x109
fffff880`07a5d800 fffff880`0128ea50 : fffffa80`07843180 fffffa80`07c86ba0 00000000`00000001 00000000`00000000 : Ntfs!NtfsRepairItem+0x11eb
fffff880`07a5dce0 fffff800`02f68ede : 00000000`00000001 fffff880`09a40bc8 fffffa80`07e71b50 00000000`00000080 : Ntfs!NtfsProcessRepairQueue+0x1c0
fffff880`07a5dd40 fffff800`02cbb906 : fffff880`009e9180 fffffa80`07e71b50 fffffa80`0701c060 00000000`b7172000 : nt!PspSystemThreadStartup+0x5a
fffff880`07a5dd80 00000000`00000000 : fffff880`07a5e000 fffff880`07a58000 fffff880`07a5cdf0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`02d3d742 cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

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

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

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

docsanchez · 16 Oct 2013

Daemon tools removed (I've only installed it recently tho, so it was never on my PC for long), avira removed.

This is what happened when I ran the tests:

1. SFC/Scannow - Ran it a couple of times, would tell me that it still found something, after installing the System Update Readiness Tool everything was fine though.

2. Disc Check ran to be scheduled after a bootup. Nothing happened afterwards, so I assume it's fine, is there a logfile or something?

3. Clean Boot - gave me the same freeze type of error when I was playing binding of Isaac (flash-based Game), recovered after a while though, but the error definitely happened.

4. Memtest gave me 0 errors after running it from Boot for 5 Times. (I turned off the PC in the night cause it was too loud and my RAM is pretty new anyways)

5. Manufactures test gave me this:

What are my next steps? I am getting "disk read error- press ctrl + alt + delete to restart" quite frequently when trying to boot now and ALSO getting an errormessage like this when trying to boot:

Windows has encountered a problem communicating with a device connected to your computer.
This error can be caused by unplugging a removable storage device such as an externas USB drive while the device is in use, or by faulty hardware such as a hard drive or CD-ROM drive that is failing. Make sure any removable storage is properly connected and then restart your computer.

Status:0xc00000e9

Info: An unexpected I/o error occurred

- Usually the way to resolve this is unplugging my computer entirely, leaving it off for ~5 Minutes and then trying to start it again.

So since I did all the suggested steps, what are my next steps? I am really out of ideas. Thanks in advance for the thorough help - added is a new zipfile with the SF file.
e: SF file following shortly, just thought it would be wise to submit this before the PC crashes again :)

Greetings

koolkat77 · 16 Oct 2013

Sounds like a bad hard drive although the mfg diagnostic passed.
This dump confirms the same.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8007954b30, fffffa8007954e10, fffff80002fd1350}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8007954b30, Terminating object
Arg3: fffffa8007954e10, Process image file name
Arg4: fffff80002fd1350, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa8007954b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`021b80e8 fffff800`03058d22 : 00000000`000000f4 00000000`00000003 fffffa80`07954b30 fffffa80`07954e10 : nt!KeBugCheckEx
fffff880`021b80f0 fffff800`0300508b : ffffffff`ffffffff fffffa80`08550b50 fffffa80`07954b30 fffffa80`07954b30 : nt!PspCatchCriticalBreak+0x92
fffff880`021b8130 fffff800`02f85144 : ffffffff`ffffffff 00000000`00000001 fffffa80`07954b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`021b8180 fffff800`02cc9e93 : fffffa80`07954b30 fffff800`c0000005 fffffa80`08550b50 00000000`022a03c0 : nt!NtTerminateProcess+0xf4
fffff880`021b8200 fffff800`02cc6450 : fffff800`02d1581f fffff880`021b8b78 fffff880`021b88d0 fffff880`021b8c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`021b8398 fffff800`02d1581f : fffff880`021b8b78 fffff880`021b88d0 fffff880`021b8c20 000007fe`fe502784 : nt!KiServiceLinkage
fffff880`021b83a0 fffff800`02cca282 : fffff880`021b8b78 00000000`022e0000 fffff880`021b8c20 000007fe`fe511c5c : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`021b8a40 fffff800`02cc8dfa : 00000000`00000001 00000000`022a0978 00000000`022a2f01 00000000`022e0000 : nt!KiExceptionDispatch+0xc2
fffff880`021b8c20 00000000`76da8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`022a0980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76da8e3d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe

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

Bugcheck F4 is a storage related bugcheck.

Use Crystal Disk Info to upload a screenshot of your Hard Drives (s).
- ~~Then test your Hard Drives (s) running a Hard Drive Diag.~~

docsanchez · 16 Oct 2013

That would make sense since it was part of my old computer, maybe my faulty motherboard fried the HDD in some weird way? Well, I don't even know, it's all so random. Anyways, here is the screenshot!

Arc · 16 Oct 2013

If it a stop 0x7A + a stop 0xF4, there is no doubt that it is HDD malfunction. You have only one WD HDD, and we have reasons to believe that it is good.

Next suspect is the storage controller, which is the pciide.sys; the system native IDE driver, that cannot be the guilty by any chance.

Now, open the computer and check some things. Check if the HDD is screwed properly. Re-seat or change the SATA and power cables. Apply the SATA cable in another unused SATA port on the motherboard.

Next attempt ... update the BIOS to Version 3029, dated 2012.07.27. Your present one is version 2101 .

Then let us know the results. If it is the same BSOD even after doing all those successfully, then and only then we can think about the motherboard.

docsanchez · 16 Oct 2013

I did what you said, I updated the bios and checked the HDD in the computer - it seemed like one sata cable that was going into the HDD was a bit loose before, now it is pretty tight - I also plugged the other end into another slot of the mainboard and also unplugged the DVD-Drive. No crashes or freezes so far, I'll keep you updated though. Thanks for the help so far.

Arc · 17 Oct 2013

Good job.
Now let us know how it is running :)

docsanchez · 21 Oct 2013

it seems like the HDD was rly it. I know that the sata cable going to the mainboard was always kinda loose and one of the "fork's" teeth was a bit bent, but as I said I replugged it and it fit much more solidly then before.

Thank you from the bottom of my heart for helping me, I don'T even wanna know what a technician would've done ;D

Best regards

Arc · 22 Oct 2013

You are welcome mate :)

Let us know for any further issue.