Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Random BSOD on startup

- - - - -

Best Answer phillpower2 , 27 October 2015 - 02:35 AM

Apologies for the delay getting back to you   Couple of things of note in Speccy; Hibernation has re enabled, not uncommon when done from power management, after first creating a new... Go to the full post »


  • Please log in to reply

#1
Praenei

Praenei

    Member

  • Member
  • PipPip
  • 11 posts

Hi guys

 

I've been having intermittent BSOD on startup ever since I bought my Gigabyte P35 laptop last February. It has been more of an annoyance than anything more serious as it restarts without any problems but I'm worried that it might be a sign of impending hardware problems which I'd obviously like to get sorted while still under warranty. All of my drivers are up to date (using Slimdrivers utility) & I've just turned on the verifier tool following the instructions listed in http://www.geekstogo.com/forum/topic/345427-driver-power-state-failure/. No BSOD yet but I'll add anything to this post when it reoccurs.

 

I've also attached the minidumps that I've been collecting since I upgraded to Win 10 from Win 8.1.  I should point out that I was also getting these problems with Win8.1.

 

Thanks in advance for any help that can be offered.

 

Praenei

Attached Files


  • 0

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

:welcome:   Praenei,

 

I've been having intermittent BSOD on startup ever since I bought my Gigabyte P35 laptop last February. 

 

 

Honest answer is that you should have returned it and let them sort it out, more difficult to do now unless it is hardware related as you have made changes to the installed software.

 

Your attached dumps are of no use unfortunately as they all show that the crashes happened at 10.00 on 23/10/2015 which as know is not true or possible, if the computer does blue screen while running DV please only attach that dump for us.

 

Tip

To ensure that you receive notification of any reply to your thread please click on the Follow this topic tab, top right corner above your OP.


  • 0

#3
Praenei

Praenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

Wow, thanks for the speedy response Phillpower2.  Yeah I agree with your comment that I should have returned it immediately but in my defense it happens about once a week, doesn't take long to restart & I need the laptop for work.  

 

I'm slightly confused about the minidumps though. If I open the most recent one from the zip file using Windbg I can see the following :-

 

 
Microsoft ® Windows Debugger Version 10.0.10240.9 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\andee_000\Desktop\102315-7406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsof...ownload/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsof...ownload/symbols
Executable search path is: 
No .natvis files found at D:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10240.16515.amd64fre.th1.150916-2039
Machine Name:
Kernel base = 0xfffff800`93e76000 PsLoadedModuleList = 0xfffff800`9419b010
Debug session time: Thu Oct 22 17:30:06.133 2015 (UTC + 1:00)
System Uptime: 0 days 4:49:56.834
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck D1, {fffff8880d912140, ff, d9, fffff8880d912140}
 
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+248 )
 
Followup:     MachineOwner
 
 
 
Each minidump seems to report a different error.  So the second most recent error had 'Probably caused by : hardware ( REGION_PAGED_OUT )' & the one before that was 'Probably caused by : FLTMGR.SYS ( FLTMGR!FltpGetStreamListCtrl+66 '.  There seems to be no consistency.

  • 0

#4
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

Hello Praenei,

 

Aye it is hard when a problem is intermittent as it never seems to happen when being independently tested.

 

I checked the properties of the dump files to get the times and dates in order and I don't appear to have that particular dump in my downloads, the final dump that I have is from Windows 8 Thu Oct 22 12:30:06.133 2015 (UTC - 4:00)  the cause identified (PROCESS_NAME:  System) is too generic to be of any use as is the image name which was ntkrnlmp.exe.

 

The three dumps previous to the above identified svchost.exe, FLTMGR.SYS and again ntkrnlmp.exe. again for Windows 8 and therefore of no use if you are now running Windows 10.

 

While we are waiting to see if DV forces a crash can you do the following for us please;

 

Download then run Speccy (free) and post the resultant url for us, details here,  this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s. 

 

You are welcome btw  :)


  • 0

#5
Praenei

Praenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

Hi again,

 

I think we must be looking at the same file (102315-7406-01.dmp).  The timestamp I see is Thu Oct 22 17:30:06.133 2015 (UTC + 1:00) whereas you're seeing Thu Oct 22 12:30:06.133 2015 (UTC - 4:00) presumably because of timezone differences.  The Win8/10 is a bit more of a mystery.  Perhaps you are running a Win 8 device & that is what it is showing & perhaps that also explains why you see 'PROCESS_NAME:  System' but I see 'Probably caused by : FLTMGR.SYS'.? Only guessing though.

 

I've downloaded speccy & posted by system details here - http://speccy.pirifo...Hz6jDltV0FqwruWI hope it makes sense to someone :)

 

Praenei


  • 0

#6
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

Some pointers from Speccy;

 

Speccy shows you to be in the UK where I am so not sure about time zone differences + I use W10 Pro, no matter anyhow as we will only be using any new dump files that may be generated, meanwhile I would suggest the following changes be made, some temporary while troubleshooting and a couple permanent;

 

Power Profile
Active power scheme: High performance Change this to Balanced. Permanent.
Hibernation: Enabled Change this to Disabled. Permanent.
Turn Off Monitor after: (On AC Power): 10 min Change to never. Temporary.
Turn Off Monitor after: (On Battery Power): 10 min Change to never. Temporary.
Turn Off Hard Disk after: (On AC Power): Never
Turn Off Hard Disk after: (On Battery Power): Never
Suspend after: (On AC Power): Never
Suspend after: (On Battery Power): 25 min Change to never. Temporary.
Screen saver: Disabled
 
Disable all of the following scheduled updates, apart from all important Windows updates and AV protection being automatically installed nothing should be checked for or installed without your permission, this will help with speeding up boot times and to avoid any potentially unwanted software being installed.
 
** Please note that drivers should never be updated unless it is to address a known issue, if a driver is installed needlessly you can end up creating the very issue that the updated driver was intended to correct, rolling back to the previous driver does not always work and waiting for the next driver update can take some time and also not work.
 
Scheduler
24/10/2015 12:17;: GoogleUpdateTaskMachineUA
24/10/2015 12:24;: DropboxUpdateTaskUserS-1-5-21-4290463442-3981218742-3094551730-1001UA
24/10/2015 13:17;: GoogleUpdateTaskMachineCore
25/10/2015 08:24;: DropboxUpdateTaskUserS-1-5-21-4290463442-3981218742-3094551730-1001Core
25/10/2015 08:51;:** SlimCleaner Plus (Scheduled Scan - Andee)
25/10/2015 10:00;: IUM-F1E24CA0-B63E-4F13-A9E3-4ADE3BFF3473
Adobe Acrobat Update Task
DolbySelectorTask
IUM-F1E24CA0-B63E-4F13-A9E3-4ADE3BFF3473-Logon
Optimize Start Menu Cache Files-S-1-5-21-4290463442-3981218742-3094551730-1001
Optimize Start Menu Cache Files-S-1-5-21-4290463442-3981218742-3094551730-500
RtlLanOptimizerVistaStart
**SlimDrivers Startup
 
Scheduled updates like those above can cause network problems with the wireless connection and/or internet if they interfere with Windows updates etc.
 
Can you grab a screenshot of Disk Manager and attach it to your next reply for us;
 

·         Right click This PC > Manage > Disk Management.

·         Click Start Menu and then type Disk Management to search.

·         Click Start Menu and type cmd to open command line and then input compmgmt.msc and then click Enter.

 
To capture and post a screenshot;
 
Click on the ALT key + PRT SCR key..its on the top row..right hand side..now click on start...all programs...accessories...paint....left click in the white area ...press CTRL + V...click on file...click on save...save it to your desktop...name it something related to the screen your capturing... BE SURE TO SAVE IT AS A .JPG ...otherwise it may be to big to upload... then after typing in any response you have... click on browse...desktop...find the screenshot..select it and click on the upload button...then on the lower left...after it says upload successful...click on add reply like you normally would.
 
Screenshot instructions are provided to assist those that may read this topic but are not yet aware of the “how to”.
 
 
 BTW: Avira got a mention in one of your crashes and so may need to be looked at.

  • 0

#7
Praenei

Praenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

I've changed the power profile to match what you stated.  The laptop did actually BSOD as I was booting up before making any of the changes.  I've attached the minidump together with the screenshot of the device mgmt.

 

I'm not sure how to stop the automated updates.  Do you mean from Task Manager / Start-up tab?  Any guidance would be appreciated.  

 

Avira is actually quite a new install as I was using Avast! as my AV until quite recently.  I was getting BSODs with Avast! too & I did follow another site's instructions on diagnosing using Verifier which checked all the checkboxes on the options stage & resulted in it then constantly crashing on bootup.  It highlighted an Avast! DLL as the culprit.   I then uninstalled & replaced it with Avira.  Still broken though :(

 

Thanks again for taking the time to investigate this.

 

Praenei

Attached Thumbnails

  • DiskMgmt.jpg

Attached Files


  • 0

#8
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts
I am hoping that it is the Hibernation setting in the power plan that is causing this so for now we need to wait and see if it happens again with Hibernation disabled.
 

From your latest dump file;

 

 
FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page.  This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 0000000000000620, physical page number
Arg3: 00000087c22e1e00, zero
Arg4: ffffd00021b3c000, zero
 
Debugging Details:
------------------
 
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
 
BUGCHECK_STR:  PAGE_NOT_ZERO
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
PROCESS_NAME:  System

 

 

Again we will need to wait and see if disabling Hibernation helps but fwiw it would appear that there is a known problem with this particular type of crash, see here

 

Disable the scheduled updates in the start up please.

 

Are you aware that Windows 8/8.1 and 10 have an updated version of Windows Defender that offers the same real time protection as Microsoft Security Essentials, you do not need third party AV protection and by not installing any you are reducing the possibility of potential conflicts and freeing up resources on your computer, information courtesy of admin here

 

Disk Manager does not show any problems.

 

You are welcome btw  :)


  • 0

#9
Praenei

Praenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

I've uninstalled SlimCleaner & Avira, rather than disabled, to see if that makes a difference & I can do without them and disabled Dropbox.  I've not done the Google ones yet as I assume they are either to do with Drive or Chrome both of which I use heavily.  So the startup currently looks like the attachment.

 

Lets see what happens.  I'll keep this post updated.

Attached Thumbnails

  • startup.jpg

Edited by Praenei, 25 October 2015 - 04:45 AM.

  • 0

#10
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

Unless you actually use it I would also get rid of Java, see why here


  • 0

Advertisements


#11
Praenei

Praenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

I need Java for stuff I do at work.  Has to stay I'm afraid :(


  • 0

#12
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

All you can do then is ensure that it is always up to date and disable it when not in use, pain in the proverbial I know but always best to be safe.

 

Since uninstalling Avira, have you checked for and installed any/all important updates for Windows 10 and Defender.


  • 0

#13
Praenei

Praenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

Checked for updates yesterday in Win10 & Defender & got everything up to date.

 

However another crash on bootup this morning.  Minidump attached.  Short message today - lots of issues at work :(   Must be Monday morning

 

Praenei

Attached Files


  • 0

#14
Praenei

Praenei

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

Just re-read your last message & missunderstood your commentabout Java.  I have now disabled that at start-up as I never want to update it anyway as the app I use that requires it only works on an old version of Java.  Got carried away & also deactivated some other apps at startup - Ace (*2), CurseClientStartUp, iTunesHelper Java Update Scheduler, Quicktime Task, Receiver Updater, Microsoft OneDrive & Welcome. New screenshot attached.

Attached Thumbnails

  • startup.jpg

  • 0

#15
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

The above crash points towards a hardware problem with the memory, while I am not 100% convinced that it is not a problem with Windows (others are reporting the same crash here) can you for now at least disable Driver Verifier, I have included a link below to Microsoft`s take on the error;

 

To turn Driver Verifier off in the search field type- verifier /reset then re-boot please.

 
This bugcheck indicates that a single bit error was found in this page.  This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 00000000000005fa, physical page number
Arg3: 000000abbffc5da0, zero
Arg4: ffffd0011a5cf000, zero
 
Debugging Details:
------------------
 
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
 
BUGCHECK_STR:  PAGE_NOT_ZERO
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  1
 
STACK_TEXT:  
ffffd001`1a519ce8 fffff802`61ebc859 : 00000000`0000012b ffffffff`c00002c4 00000000`000005fa 000000ab`bffc5da0 : nt!KeBugCheckEx
ffffd001`1a519cf0 fffff802`61e3aea5 : 00000000`00000003 ffffe001`ea200050 ffffe001`ea200050 00000000`00000001 : nt!ST_STORE::StDmPageError+0xe5
ffffd001`1a519d60 fffff802`61d8d09e : ffffe001`ec55f780 ffffafda`d398b64c ffffe001`edc7b040 fffff802`61d8e86c : nt! ?? ::FNODOBFM::`string'+0x62fa5
ffffd001`1a519e40 fffff802`61d8cea5 : 00000000`00000002 ffffe001`ed236f90 ffffe001`ea200050 00000000`00000002 : nt!ST_STORE::StDmSinglePageTransfer+0xb6
ffffd001`1a519ea0 fffff802`61d8cbdd : ffffe001`ffffffff ffffe001`000005da 00000000`00000aea ffffe001`ec55f780 : nt!ST_STORE::StDmpSinglePageRetrieve+0x1e1
ffffd001`1a519f40 fffff802`61d8c29d : ffffd001`1a51a130 ffffe001`ec55f780 ffffd000`0001fef8 ffffe001`ed24e3c0 : nt!ST_STORE::StDmPageRetrieve+0xc1
ffffd001`1a51a000 fffff802`61d8c1d1 : ffffe001`ea200000 ffffe001`ec55f780 ffffe001`ea200000 fffff802`61d8c1b8 : nt!SMKM_STORE::SmStDirectReadIssue+0x91
ffffd001`1a51a070 fffff802`61cf8925 : ffffe001`ec55f780 ffffd001`1a51a130 ffffe001`ea2011d4 fffff802`61d618c0 : nt!SMKM_STORE::SmStDirectReadCallout+0x19
ffffd001`1a51a0a0 fffff802`61d8c0e3 : 00000000`00000003 fffff802`61fbe300 ffffe001`edc7b000 ffffe001`ea200000 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd001`1a51a0f0 fffff802`61d8aba8 : ffffe001`ec55f780 00000000`00000801 ffffe001`ea200000 00000000`00000002 : nt!SMKM_STORE::SmStDirectRead+0xb7
ffffd001`1a51a1c0 fffff802`61d8a84f : ffffe001`ec55f780 ffffe001`ec55f780 ffffe001`ea200000 fffff802`61fbe300 : nt!SMKM_STORE::SmStWorkItemQueue+0x1c8
ffffd001`1a51a220 fffff802`61d889f1 : 00000000`0000000c ffffe001`f06f4110 00000000`00000001 ffffe001`f06f4060 : nt!SMKM_STORE_MGR::SmIoCtxQueueWork+0xc7
ffffd001`1a51a2b0 fffff802`61d88885 : ffffe001`f06f4010 ffffd001`1a51a370 ffffd001`00000001 fffff6e0`00000000 : nt!SMKM_STORE_MGR::SmPageRead+0x165
ffffd001`1a51a330 fffff802`61cadf81 : ffffd001`203f77ab fffff781`00000000 00000000`00003e48 fffff802`61c9a1f2 : nt!SmPageRead+0x75
ffffd001`1a51a370 fffff802`61cac1e8 : 00000000`00000002 fffff802`61fbdbf8 ffffe001`f06f4010 00000000`00000000 : nt!MiIssueHardFaultIo+0x129
ffffd001`1a51a3f0 fffff802`61c9b93d : 00000000`c0033333 fffff802`61fbdbf8 ffffc000`dc71ee68 7fffe001`e6773500 : nt!MiIssueHardFault+0x168
ffffd001`1a51a490 fffff802`61dd23bd : ffffe001`ed24e0d8 ffffc000`d9fe7210 00000000`00000000 ffffe001`e1118508 : nt!MmAccessFault+0x39d
ffffd001`1a51a5e0 fffff802`61d53935 : fffff801`548bbee7 ffffc000`dbe84bb0 ffffd001`1a51aa40 ffffe001`e6772180 : nt!KiPageFault+0x13d
ffffd001`1a51a778 fffff801`548bbee7 : ffffc000`dbe84bb0 ffffd001`1a51aa40 ffffe001`e6772180 ffffe001`00000000 : nt!RtlSplay+0x25
ffffd001`1a51a780 fffff801`5480c665 : ffffc000`dbe84bb0 ffffd001`1a51aa40 00000000`00000000 ffffe001`e11173c8 : NTFS!NtfsFullDeleteLcb+0x47
ffffd001`1a51a7b0 fffff801`548bc16b : ffffe001`ee50b368 ffffe001`e6772180 ffffc000`dbe847a0 ffffc000`dbe84bb0 : NTFS!NtfsTeardownFromLcb+0x145
ffffd001`1a51a850 fffff801`5480d170 : ffffe001`ee50b368 ffffd001`1a51a952 ffffc000`dbe84bb0 ffffe001`ee50b368 : NTFS!NtfsTeardownStructures+0xdb
ffffd001`1a51a8d0 fffff801`548be191 : ffffd001`1a51aa78 ffffd001`00000000 ffffd001`1a51aa40 ffffe001`ee50b368 : NTFS!NtfsDecrementCloseCounts+0xd0
ffffd001`1a51a910 fffff801`548bb612 : ffffe001`ee50b368 ffffc000`dbe848e0 ffffc000`dbe847a0 ffffe001`e6772180 : NTFS!NtfsCommonClose+0x401
ffffd001`1a51a9e0 fffff802`61cf4dd9 : fffff802`62054340 ffffe001`ed24e040 fffff802`62054200 fffff801`57515110 : NTFS!NtfsFspCloseInternal+0x1a6
ffffd001`1a51ab70 fffff802`61d61558 : 00000010`00000000 00000000`00000080 fffff802`62054340 ffffe001`ed24e040 : nt!ExpWorkerThread+0xe9
ffffd001`1a51ac00 fffff802`61dce3c6 : ffffd001`18cc2180 ffffe001`ed24e040 ffffe001`ee2fb2c0 007d0036`00450041 : nt!PspSystemThreadStartup+0x58
ffffd001`1a51ac60 00000000`00000000 : ffffd001`1a51b000 ffffd001`1a515000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
SYMBOL_NAME:  REGION_PAGED_OUT
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: hardware
 
IMAGE_NAME:  hardware
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  X64_PAGE_NOT_ZERO_VRF_REGION_PAGED_OUT
 
BUCKET_ID:  X64_PAGE_NOT_ZERO_VRF_REGION_PAGED_OUT
 
Followup: MachineOwner
 
Also busy myself now for a few hours but will check back later, when you are able to, can you post an updated Speccy url for us so we can take a fresh look at your hardware and settings.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP