Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

8.1 encountered problem needs close :( then difficulty reboot


  • Please log in to reply
7 replies to this topic

#1 Skillful

Skillful

  • Members
  • 92 posts
  • OFFLINE
  •  
  • Local time:04:54 PM

Posted 03 March 2018 - 09:17 PM

First off, permissions. I'm the administrator, right? So I copied the minidump file to desktop, that opened up in the windbg.
but when I moved, not copy, moved, says I need permission for the other dump file? and wont let me open it? How do I fix this permissions?

On to the main problem. Computer has been 'encountered a problem and needs to close :(' we are gathering data 5%, 15%, 30% etc blue screen then reboots. Tells to remove media or press any key, goes to bios, have to turn off and remove usb sometimes to get it to boot again.

I have copied the dump file here



Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.18931.amd64fre.winblue_ltsb.180201-0600
Machine Name:
Kernel base = 0xfffff801`1547e000 PsLoadedModuleList = 0xfffff801`1574b6d0
Debug session time: Sun Mar 4 11:13:09.374 2018 (UTC + 10:00)
System Uptime: 0 days 9:37:14.010
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, {fffff6e8001b5680, ffffffffc00000c0, 1762abbe0, ffffd00036ad0000}

Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+72a )

Followup: MachineOwner

then it said
2: kd> and you can type. pressed enter it said
Implicit thread is now fffe001'13f286c0


we clicked !analyze -v and it did some more
2: 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: fffff6e8001b5680, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc00000c0, error status (normally i/o status code)
Arg3: 00000001762abbe0, current process (virtual address for lock type 3, or PTE)
Arg4: ffffd00036ad0000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 6.3.9600.18931 (winblue_ltsb.180201-0600)

SYSTEM_MANUFACTURER: ASUS

SYSTEM_PRODUCT_NAME: All Series

SYSTEM_SKU: All

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1104

BIOS_DATE: 02/22/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: H81M-K

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

BUGCHECK_P1: fffff6e8001b5680

BUGCHECK_P2: ffffffffc00000c0

BUGCHECK_P3: 1762abbe0

BUGCHECK_P4: ffffd00036ad0000

ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

BUGCHECK_STR: 0x7a_c00000c0

CPU_COUNT: 8

CPU_MHZ: da4

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1A'00000000 (cache) 1A'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: AILLY

ANALYSIS_SESSION_TIME: 03-04-2018 11:57:49.0357

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

LAST_CONTROL_TRANSFER: from fffff801154c6626 to fffff801155d2fa0

STACK_TEXT:
ffffd000`34eff6b8 fffff801`154c6626 : 00000000`0000007a fffff6e8`001b5680 ffffffff`c00000c0 00000001`762abbe0 : nt!KeBugCheckEx
ffffd000`34eff6c0 fffff801`154bb246 : 00000000`00000002 ffffd000`34eff828 fffff801`157cdec0 ffffd000`00000000 : nt!MiWaitForInPageComplete+0x72a
ffffd000`34eff7b0 fffff801`154e379f : 00000000`c0033333 ffffe001`16319642 fffff801`157cdec0 ffffd000`36ad0000 : nt!MiIssueHardFault+0x336
ffffd000`34eff870 fffff801`15567b4e : 00000000`00000001 00000000`00000000 fffff801`1547e000 00000000`00000000 : nt!MmAccessFault+0x95f
ffffd000`34eff9c0 fffff801`155b835f : fffff801`15752de0 00000000`00000000 ffffe001`16479158 ffffe001`00000000 : nt!MiInPageSingleKernelStack+0x296
ffffd000`34effba0 fffff801`155749b8 : fffff801`15767180 ffffe001`13e6f040 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0xb3
ffffd000`34effc00 fffff801`155db2d6 : fffff801`15767180 ffffe001`13f286c0 fffff801`157cea00 00000004`ed374efe : nt!PspSystemThreadStartup+0x178
ffffd000`34effc60 00000000`00000000 : ffffd000`34f00000 ffffd000`34efa000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: 3033062ed9b1b68c332576eeeecce57621371b73

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8bb81ca9ea0074664d05ad5bc4e6d59431fce94f

THREAD_SHA1_HASH_MOD: cb5f414824c2521bcc505eaa03e92fa10922dad8

FOLLOWUP_IP:
nt!MiWaitForInPageComplete+72a
fffff801`154c6626 cc int 3

FAULT_INSTR_CODE: cccccccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiWaitForInPageComplete+72a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5a734bdd

IMAGE_VERSION: 6.3.9600.18931

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 72a

FAILURE_BUCKET_ID: 0x7a_c00000c0_nt!MiWaitForInPageComplete

BUCKET_ID: 0x7a_c00000c0_nt!MiWaitForInPageComplete

PRIMARY_PROBLEM_CLASS: 0x7a_c00000c0_nt!MiWaitForInPageComplete

TARGET_TIME: 2018-03-04T01:13:09.000Z

OSBUILD: 9600

OSSERVICEPACK: 18931

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

OSEDITION: Windows 8.1 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-02-02 03:18:21

BUILDDATESTAMP_STR: 180201-0600

BUILDLAB_STR: winblue_ltsb

BUILDOSVER_STR: 6.3.9600.18931

DISKSEC_ORG_ID:

DISKSEC_MODEL: |

DISKSEC_MANUFACTURING_ID: XNGA039154 K

DISKSEC_ISSUE_DESC_STR:

DISKSEC_TOTAL_SIZE: 589

DISKSEC_REASON: 1

DISKSEC_PUBLIC_TOTAL_SECTION_SIZE: 454

DISKSEC_PUBLIC_OFFSET: 12c

DISKSEC_PUBLIC_DATA_SIZE: 400

DISKSEC_PRIVATE_TOTAL_SECTION_SIZE: 9

DISKSEC_PRIVATE_OFFSET: 580

DISKSEC_PRIVATE_DATA_SIZE: 1

ANALYSIS_SESSION_ELAPSED_TIME: 416

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7a_c00000c0_nt!miwaitforinpagecomplete

FAILURE_ID_HASH: {7d19656d-a91b-a228-4ebb-5edd525642eb}

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

Edited by Skillful, 03 March 2018 - 09:24 PM.


BC AdBot (Login to Remove)

 


#2 Skillful

Skillful
  • Topic Starter

  • Members
  • 92 posts
  • OFFLINE
  •  
  • Local time:04:54 PM

Posted 04 March 2018 - 12:45 AM

I'm also getting
"A disk read error occurred
Press ctrl alt del to restart"

So I did that and it booted. I left it at logon screen and came back within about 2hrs it had the same disk read error. This time it keeps going to that error.

Edited by Skillful, 04 March 2018 - 01:25 AM.


#3 Skillful

Skillful
  • Topic Starter

  • Members
  • 92 posts
  • OFFLINE
  •  
  • Local time:04:54 PM

Posted 04 March 2018 - 01:20 AM

Another update: Since this time I can't get it to boot to windows at all, even turning it off didn't fix it... I turned it off, dc power, swapped to different sata port, different sata cable, and different power cable. Now , it boots to windows. I also got radeon something something needs to close, that could be a separate issue as I did rollback a driver recently. But I got the blue screen stuff before I even updated the amd driver. Unsure if this is fixed now or not. But the permission issues still need to know how to fix that?

#4 dmccoyks

dmccoyks

  • BSOD Kernel Dump Expert
  • 752 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:54 AM

Posted 23 March 2018 - 02:38 PM

Is it working with Windows now or are you still getting BSOD's? Have you ran any hardware diagnostic utilities on the hard drive and memory? Does it work properly in Safe mode?



#5 techiegeek12

techiegeek12

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:01:54 AM

Posted 01 April 2018 - 10:58 PM

Open Command Prompt with administrator privileges (as shown previously)
Type sfc /scannow
 
update drivers run memory test 


#6 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 6,875 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:07:54 AM

Posted 02 April 2018 - 04:25 PM

 

I'm also getting
"A disk read error occurred

 

I don't like that part !  This may well have been due to the SATA cable or port, which you have changed but I would still download Seagate's 'Tools for Windows - if your computer is booting reasonably normally - and the Seagate 'Tools for DOS' if it isn't. You will need to burn these to either a disc or a USB stick to use them as they both download as ISO files. Both versions come with two basic tools - a 'Short' test and a 'Long' one. Run the short test first and, if the HDD passes that, run the long one. This will let you know if you have any problems with the HDD itself.

 

Chris Cosgrove



#7 Skillful

Skillful
  • Topic Starter

  • Members
  • 92 posts
  • OFFLINE
  •  
  • Local time:04:54 PM

Posted 29 April 2018 - 05:47 PM

Hey everyone,

Ended up turning it off, used different sata port, and different power cable to that sata port, and problem has gone away so far.

This was done back in early March. I'm guessing sata ports/power cable can sometimes either get loose or stop working?

I've always had those permissions issues though in the first post. I can start a new thread if necessary for that. I installed win8 myself , so figured I'd be administrator by default?

Edited by Skillful, 29 April 2018 - 05:52 PM.


#8 dmccoyks

dmccoyks

  • BSOD Kernel Dump Expert
  • 752 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:54 AM

Posted 30 April 2018 - 11:22 AM

Are you having issues with file permissions on all directories or only certain ones? We can try resetting your permissions using commands or you can download the following easy to use utility. I recommend backing them up first.

 

http://www.thewindowsclub.com/reset-ntfs-file-permission-windows 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users