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

several Restarts, BSODs & Freezes but ONLY at startup?!


  • Please log in to reply
9 replies to this topic

#1 Chumbo

Chumbo

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:07 PM

Posted 05 August 2016 - 05:43 AM

Hi,

It used to be rather erratic and happen only once every couple of days, then I would sometimes have stretches as long as a week or more without any crashes but recently I've been having them systematically at EVERY startup!

 

I start my computer, it will usually boot up into Windows 10 Pro 64bit and then I rarely have to wait more than a few minutes for it to freeze or suddenly restart (more rarely a BSOD). Then starts a cycle of a few more restarts and freezes - always happening almost instantly or after a few minutes - before it eventually stabilizes and can then run reliably for the rest of the day!?

 

This is why I've ruled out temperature problems as it would seem the reverse would happen, i.e. crashing AFTER sufficient time was given to the system to heat up.

 

I have run 2 passes of MemTest without any errors but I've heard that as many as 10 might be needed to reliably exclude RAM problems but seeing how slow it runs the test on my 12Gb of memory, I couldn't be without my PC for that long!?  :(

 

Other useful troubleshooting info: I've recently upgraded to Win 10 in hope of solving my problems - it was already happening under Win 7. It's a 2nd PC I bought off ebay some +- 2 years ago so I don't know how old exactly it is but you'll see the specs in the attached files I guess.

 

Some of the BSOD errors I collected are (from oldest to most recent):

- Clock Watchdog Timeout

- Machine Check Exception

- PA (dxgkrnl.sys)

- Kernel Security Check Failure

 

There were others before that but I'm afraid I didn't jot those down.

 

I should mention also that I've had freezes happen at what looks like to me, pre-OS loading stage. At boot-up, during those BIOS POST messages appearing. I thought that was quite worrying as to me, it would indicate that it most probably is hardware-related because at this stage, the OS is not involved, right? It's less frequent but has happened.
What I find strange though, is that, as I explained above, after a few crashes and freezes, it will work fine for a whole day!? This is why I find this problem very confusing and strange?! On one hand it sound like it would really likely be a hardware problem (because of the crash during BIOS POST), then on the other hand, the fact that several reboots seem to flush the problems away, makes me think it's maybe software related?! 

 

Thanks in advance for any help you can provide! :)

 

Attached Files



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:07 PM

Posted 07 August 2016 - 08:02 PM

Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

I'll try to run an analysis in the morning (early AM east coast of the US - UTC-5), but I'm having troubles:

- wife's away

- extra hours at work

- haven't mowed the lawn in 2 weeks

- I'm sick (flu-ish)

- it's past my bedtime (9pm :0)

- I'm trying to figure out how to fix BSOD's on the Anniversary Update

- I'm trying to get info on the Anniversary Update to add to my BSOD website.

I get up between 4:30 and 5am


Edited by usasma, 07 August 2016 - 08:04 PM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Chumbo

Chumbo
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:07 PM

Posted 08 August 2016 - 04:01 AM

Hi,

Thanks for replying! I'll tell you what, seeing the list of your current troubles, why don't you in fact go mow your lawn, get healthy, etc...because miraculously (to me anyway) the problem seems to be gone for now!?

The only thing I did was to test the RAM (6 x 2Gb) by pulling out all the sticks and reinserting them by pair, and rebooting each time and letting the computer run a bit to see if the problem arose...nothing?! So I then re-inserted all 6 sticks and everything seems to be working ok?!

 

Does that make any sense to you?? Could it have been a speck of dust that got removed while pulling out the RAM sticks? Dunno, very strange....



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:07 PM

Posted 08 August 2016 - 04:20 AM

Yes, RAM problems like that are relatively common.

That's why we suggest hardware diagnostics at the start (when someone describes symptoms similar to yours)

It depends on the technician as to how many passes to run (I normally suggest 3).

 

Unfortunately, all we have is software to test the hardware problems.

For RAM, we have MemTest and it's variants (MemTest86; MemTest86+, etc)

We also have Prime 95.  The Blend test there tests mostly RAM.

But nothing beats trying different RAM - or in your case, trying the individual sticks to see if the problem goes away.

 

It's most likely that a speck of dust was the problem, and that switching the sticks around dislodged it.

I'd suggest running the RAM tests again (just in case) - both MemTest and Prime95's Blend test.

 

Good luck!  Should the problem recur, I'll get an email if you respond to this topic.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 Chumbo

Chumbo
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:07 PM

Posted 08 August 2016 - 04:22 AM

Ok, thanks! Fingers crossed....

Cheers,



#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:07 PM

Posted 08 August 2016 - 04:29 AM

Your UEFI/BIOS (version F13) dates from 2012.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

 

D: drive only has about 7% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

 

MiniTool Partition Wizard driver dates from 2009.  Please uninstall the program from Control Panel...Programs and Features

Your AOC Monitor Driver dates from 2011.  Please uninstall the program from Control Panel...Programs and Features

Beyond that, there's nothing certain in the memory dumps.

 

 

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

**************************Fri Aug  5 04:39:54.598 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\080516-6015-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
System Uptime:0 days 0:01:14.307
Probably caused by :ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
BugCheck 139, {3, ffffd00021d7a780, ffffd00021d7a6d8, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd00021d7a780, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd00021d7a6d8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: 0x139_3_nt!KiFastFailDispatch
CPUID:        "Intel® Core™ i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2665
  BIOS Version                  F13
  BIOS Release Date             01/10/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 30 10:49:36.643 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\073016-46390-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
System Uptime:0 days 0:03:13.355
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, ffffd0009a480180, 7}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd0009a480180, The PRCB address of the hung processor.
Arg4: 0000000000000007, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_8_PROC
CPUID:        "Intel® Core™ i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2665
  BIOS Version                  F13
  BIOS Release Date             01/10/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Fri Aug  5 04:39:54.598 2016 (UTC - 4:00)**************************
pwdrvio.sys                 Mon Jun 15 21:43:45 2009 (4A36F8D1)
mi2c.sys                    Wed Jun 29 07:03:58 2011 (4E0B069E)
bdfwfpf.sys                 Mon Oct 29 08:23:28 2012 (508E7540)
bdfndisf6.sys               Mon Dec 15 09:59:47 2014 (548EF763)
NvStreamKms.sys             Mon Jan 12 12:56:42 2015 (54B40ADA)
gzflt.sys                   Wed Apr 29 07:32:17 2015 (5540C141)
trufos.sys                  Mon May 11 04:26:27 2015 (555067B3)
rt640x64.sys                Wed Oct  7 11:03:55 2015 (5615345B)
intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)
bdvedisk.sys                Mon Nov 23 06:38:07 2015 (5652FA9F)
avc3.sys                    Tue Jan 19 08:52:34 2016 (569E3FA2)
nvlddmkm.sys                Fri Jan 29 04:02:12 2016 (56AB2A94)
hdsp_64.sys                 Fri Jan 29 10:51:04 2016 (56AB8A68)
SbieDrv.sys                 Fri Feb 26 13:18:55 2016 (56D0970F)


http://www.carrona.org/drivers/driver.php?id=pwdrvio.sys
http://www.carrona.org/drivers/driver.php?id=mi2c.sys
http://www.carrona.org/drivers/driver.php?id=bdfwfpf.sys
http://www.carrona.org/drivers/driver.php?id=bdfndisf6.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=gzflt.sys
http://www.carrona.org/drivers/driver.php?id=trufos.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=bdvedisk.sys
http://www.carrona.org/drivers/driver.php?id=avc3.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=hdsp_64.sys
http://www.carrona.org/drivers/driver.php?id=SbieDrv.sys


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 Chumbo

Chumbo
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:07 PM

Posted 08 August 2016 - 05:30 AM

Thanks for that!

- I have an old motherboard so no more recent drivers to install unfortunately.

- I wasn't aware Windows OS needed space on ALL drives (external drives too?), I thought it was only for the C drive! I'll keep that in mind and start clearing up some space then.

- I uninstalled the AOC app but the MiniTool Partition Wizard seems up to date from my end? I'm using the latest version of the software and it's a portabilized version of it so it resides on the D drive and the driver there is from what I can tell of 2015. I couldn't find any trace of the driver on the C drive so I've left this one in place as I imagine it will only be an issue if I run it and I of course very rarely do.

 

As for what came after that in your post, I obviously don't really know what to do with it but as you said, mainly for information purpose so...

Cheers,



#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:07 PM

Posted 09 August 2016 - 07:19 AM

Windows 10 (build 10240) was released on 29 July 2015

The Fall Update (1511/build 10586) was released in November of 2015

The Anniversary Update (1607/build 14393.10) was released on 02 August, 2016

 

The driver for the MiniTool Partition Wizard was date/time stamped 15 June 2009

Most drivers from this date will not work without issues on W10 systems.

Do the software developer and the portable app developer both certify this as being compatible w/W10 (and all it's versions)?

 

My concern here is about compatibility issues - both for the motherboard and for the individual programs.

Unfortunately, the only sure test for compatibility is to revert to the old version of the OS and see if it works there.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#9 Chumbo

Chumbo
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:07 PM

Posted 09 August 2016 - 07:38 AM

I guess you have a more accurate way of dating the driver, I just right-clicked it and looked at the properties, that's where I saw the date of 2015.

Anyway, for now everything seems ok! I've booted several times and never a crash! :-)

Thanks for your support and if ever crashes come back, as you said, I'll post in this thread to notify you.
Cheers!



#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:07 PM

Posted 09 August 2016 - 09:43 AM

There are many, many different ways of dating a driver (and files have many different dates associated with them)..

I simply use the date that the debugger provides (see the dates in the stuff that I posted).

 

I'm glad to hear that it's working well for you.

Good luck!


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users