Random BSOD's at random times often error 0x0000001E

griachae · 08 Sep 2014

essenbe said:

All of the dumps are the same. But I always get references to USB port and tcip. Is there any way you can no use wiFi and install the Lan driver and connect hardwired to your Router? Do you have other machines connected to that router and are they wireless or hardwired?

Hmm that's suspicious. The setup is like this:

There is a lan wire connected directly to the router. That router is from my renter and I dont have access to it.
The lan wire from that router goes into a switch. From that switch one lan wire goes straight into my pc, another one into a WIFI access point, that gives me wifi for my smartphone. So I am connected hardwired to the Router all the time. I will try to find out what my renter has machines he has connected to the router and how.

Are you actually saying that it may be an external problem, that has nothing to do with the soft- or hardware in my computer?

New hardware is on the way anyway

essenbe · 08 Sep 2014

What I am saying is that it appears to me to have something to do with network connectivity. Now, how and what, I can't tell you.

I can imagine you are very happy about new hardware. I know I always am. Hopefully once it gets installed and a clean install is done, hopefully your problems will stop. Just let me know and let me know what you ended up buying. I do wish you luck and hope you have fun.

griachae · 08 Sep 2014

In my opinion the piece all the errors are connected to is the mobo. We will see in a few days if it really is the cause for all this, when my new mobo arrives.

EDIT: I've bought the ASUS Sabertooth mobo you suggested and like i said the 1000W 80+ bronce be quiet PSU and another Gigabyte Radeon 7870 HD. Also a fancy liquid CPU cooler from Corsair called H55.

essenbe · 08 Sep 2014

That's a distinct possibility, but we will soon find out. Please let me know. Pictures are always appreciated.

griachae · 08 Sep 2014

Well because im eager to find the broken soft- or hardware I reinstalled Windows again. After it finished I had to manually install the latest Realtek Gigabit LAN driver(Version 7.088) manually because Windows was not able to do that again.

Then I searched for Windows Updates and 1.3 GB were found to download. At about 50 % of the installtion progress of the updates I got the first BSOD. Let SF Diagnostic Tool collect its files but the thing is the only dump file I've got is the MEMORY.DMP and it's 1 GB. But whatever I'm uploading it to Dropbox, thank god I've been able to compress it to a quarter.

Btw I still use the Nvidia 8800GTS to make sure it's not the Gigabyte Radeon 7870HD that causes the BSOD.

essenbe · 08 Sep 2014

Go Here and check your dump file settings Dump Files - Configure Windows to Create on BSOD Set them for small memory dumps. Whatever it is set to now, look there and zip the file, upload it to a file sharing service, as a public file and give me the link. If it is set to Kernel dump, the file is in c:/Windows /Memorydump.

I'll be away most of the day, unless someone else comes along, I'll look at it this afternoon. Sorry, but unavoidable. My Wife says so.

griachae · 08 Sep 2014

That's what i get from Bugcheck:

Code:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\users\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e5ae90
Debug session time: Mon Sep  8 14:51:38.189 2014 (UTC + 2:00)
System Uptime: 0 days 0:53:09.391
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols

Loading unloaded module list
..........
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff1000631235d, 1, fffff80002c8bc3a, 7}

Probably caused by : Unknown_Image ( nt!KeAccumulateTicks+14a )

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

16.7: kd:x86> !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: fffff1000631235d, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002c8bc3a, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


WRITE_ADDRESS:  fffff1000631235d 

FAULTING_IP: 
nt!KeAccumulateTicks+14a
fffff800`02c8bc3a 41              inc     ecx

MM_INTERNAL_CODE:  7

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000 00000000 00000000 00000000 00000000 0x0


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!KeAccumulateTicks+14a
fffff800`02c8bc3a 41              inc     ecx

SYMBOL_NAME:  nt!KeAccumulateTicks+14a

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  INVALID_KERNEL_CONTEXT

MODULE_NAME: Unknown_Module

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

I think I have something wrong in my Windbg setup but I have no Idea what.

essenbe said:

Go Here and check your dump file settings Dump Files - Configure Windows to Create on BSOD Set them for small memory dumps. Whatever it is set to now, look there and zip the file, upload it to a file sharing service, as a public file and give me the link. If it is set to Kernel dump, the file is in c:/Windows /Memorydump.

I'll be away most of the day, unless someone else comes along, I'll look at it this afternoon. Sorry, but unavoidable. My Wife says so.

Changed it to Minidump again and like I already mentioned I'm uploading the compressed MEMORY.DMP to dropbox right now. Well then have a good day sir!

essenbe · 08 Sep 2014

Thank you Sir, but unfortunately, this will not be a very good day. Doctors are not on my top 10 lists of having fun.

griachae · 08 Sep 2014

Haha so i guess good luck then. Here's the link https://www.dropbox.com/s/mp88ri29xd...RYDMP.zip?dl=0

essenbe · 08 Sep 2014

griachae, when you replaced the motherboard, did you do a clean install? If not, let me know. I think we should do it a little different than normal.