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

My computer has been crashing for a long time.


  • Please log in to reply
3 replies to this topic

#1 AprilFear13

AprilFear13

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:36 AM

Posted 07 October 2017 - 05:27 AM

The crashes appear to be caused by something with wininit.exe.

 

Here is my crash dump from osronline.com :

 

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.23564.amd64fre.win7sp1_ldr.160930-0600
Machine Name:
Kernel base = 0xfffff800`03605000 PsLoadedModuleList = 0xfffff800`03847730
Debug session time: Sun Mar 19 00:49:24.534 2017 (UTC - 4:00)
System Uptime: 0 days 0:14:20.736
*******************************************************************************
* *
* 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: fffffa8006943b10, Terminating object
Arg3: fffffa8006943df0, Process image file name
Arg4: fffff8000397fa10, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

PROCESS_OBJECT: fffffa8006943b10

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: wininit.exe

EXCEPTION_CODE: (Win32) 0x48999f0 (76126704) -

BUGCHECK_STR: 0xF4_fffffa80048999f0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`074c80b8 fffff800`03a09732 : 00000000`000000f4 00000000`00000003 fffffa80`06943b10 fffffa80`06943df0 : nt!KeBugCheckEx
fffff880`074c80c0 fffff800`039c6f7b : 00000000`00000001 fffffa80`048999f0 fffffa80`06943b10 00000000`00ac0900 : nt!PspCatchCriticalBreak+0x92
fffff880`074c8100 fffff800`03930234 : 00000000`00000001 ffffffff`ffffffff fffffa80`06943b10 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x273e6
fffff880`074c8150 fffff800`036736d3 : ffffffff`ffffffff fffffa80`048999f0 fffffa80`06943b10 00000000`00ac09f0 : nt!NtTerminateProcess+0x284
fffff880`074c81c0 fffff800`0366fc90 : fffff800`036f5849 fffff880`074c8b38 fffff880`074c8890 fffff880`074c8be0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`074c8358 fffff800`036f5849 : fffff880`074c8b38 fffff880`074c8890 fffff880`074c8be0 00000000`00ac2230 : nt!KiServiceLinkage
fffff880`074c8360 fffff800`03673ac2 : fffff880`074c8b38 00000000`0000e7ec fffff880`074c8be0 00000000`00ac1d08 : nt! ?? ::FNODOBFM::`string'+0x40f54
fffff880`074c8a00 fffff800`0367263a : 00000000`00000001 00000000`00ac0fa8 00000000`77202801 00000000`0000e7ec : nt!KiExceptionDispatch+0xc2
fffff880`074c8be0 00000000`770f815d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00ac0fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770f815d


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_fffffa80048999f0_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_fffffa80048999f0_IMAGE_wininit.exe

Followup: MachineOwner



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:36 AM

Posted 07 October 2017 - 09:28 AM

We need more information about your system than what you've provided. Hence, please follow these BSOD posting instructions and attach the requested files by replying to this topic. You may skip the part of step three where it instructs you to create a new topic, since you already have a topic here. There's no need to create another topic. :wink:

Thank you.

Regards,
bwv848


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 AprilFear13

AprilFear13
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:36 AM

Posted 08 October 2017 - 12:25 AM

http://speccy.piriform.com/results/bc60OZVPAgr0LScSgN8Lxjb

 

Here you go.

Sorry I didn't follow instructions the first time. I'm a little new on this site.

Attached Files



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:36 AM

Posted 09 October 2017 - 09:05 AM

Let's go through these...
 
:step1: Test RAM with MemTest86

  • Run MemTest86 for EIGHT passes - guide is here.

:step2: Test HDD with SeaTools

  • Run SeaTools - test ALL drives with the LONG GENERIC TEST - guide is here.

:step3: Check Disk - ONLY if SeaTools passes

WARNING: It is recommended that you backup ALL your files. If CHKDSK finds and repairs a corrupted sector, you may lose your data.

  • Click Start, enter cmd.exe in the Search box, right-click on cmd.exe, and then click Run as administrator.
  • Type the following command and hit ENTER:
chkdsk /R
  • You should see this message:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
  • Type Y and hit Enter on your keyboard.
  • Restart your computer and CHKDSK will run.

Once CHKDSK is complete, we need the log:

  • Click Start, enter powershell.exe in the Search box, right-click on powershell.exe, and then click Run as administrator.
  • Copy this command:
Get-WinEvent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file $Env:UserProfile\Desktop\CHKDSKResults.txt
  • Right-click in Powershell to paste the command.
  • You will find CHKDSKResults.txt on your Desktop. Copy/paste that log in your next reply.

:step4: System File Checker

  • Click Start, enter cmd.exe in the Search box, right-click on cmd.exe, and then click Run as administrator.
  • Type the following command and hit ENTER:
sfc /SCANNOW
  • After the scan is finished, you will see one of three things:
Windows Resource Protection did not find any integrity violations.
Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log.
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log.
  • If you see either of the two latter messages, please immediately enter the following command:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
  • Then, attach sfcdetails.txt, which is found on your Desktop, in your next reply.

BSODs that occur during boot are trickier to diagnose, and usually the dumps are pretty sparse in info. In your case, I am suspecting a hardware fault.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users