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

Hp computer keeps rebooting


  • Please log in to reply
22 replies to this topic

#1 user234

user234

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:27 PM

Posted 12 December 2016 - 02:06 AM

​Computer keeps rebooting everyday. We have replaced the hard drive, and installed all new memory, Updated the video driver and turn off fast boot option. Scan the pc for malware and viruses and it comes up clean. Any help would be appreciated. Thank You for all your help.

 

 

Attached File  perfmonreport.zip   182.88KB   1 downloadsAttached File  SysnativeFileCollectionApp.zip   932.51KB   1 downloads



BC AdBot (Login to Remove)

 


#2 baines77

baines77

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Washington, D.C.
  • Local time:07:27 PM

Posted 12 December 2016 - 04:28 PM

I'd suspect a bum power supply and/or if you have it plugged into a surge protector (and you should), try removing it from there and plugging it directly into the wall to see if that alleviates the symptoms.  



#3 user234

user234
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:27 PM

Posted 12 December 2016 - 07:11 PM

Thank You Baines777 for your reply. Yes the computer is plug into a battery backup and has the software installed to shut down the computer in a case of a power failure. I was looking at that this morning but the software shows it only had 1 event in the last 4 weeks. I will unplug it from the battery backup for a few days and see if that helps. The reboots only happens once a day but it is every day and not at the same time. It does seem like it 23 hours between shut down. I tried to track it down through the bug check but did not have any luck. Thank You again for your help!



#4 baines77

baines77

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Washington, D.C.
  • Local time:07:27 PM

Posted 12 December 2016 - 07:32 PM

Yeah APC's getting weird can do that too but I'd see that randomly and not every 23-ish hours. Does the unit have an LED display or anyway to test the batteries? Has it been updated lately (software/firmware)? Also, Check your task scheduler (library) and see If there are any tasks scheduled to reboot.

#5 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:08:27 PM

Posted 13 December 2016 - 10:25 AM

7 memory dumps from this month in the uploaded Sysnative report - likely they're BSOD's that aren't being seen by the user/owner.

 

Your UEFI/BIOS (version 5.13) dates from 2007.  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).
This BIOS is very far out of date - and I am concerned about it being compatible w/W10.  Unfortunately the only way to test this is to revert back to the previous OS to see if the problems go away then.

 

Only 5 Windows Update hotfixes installed.  Most build 14393 (1607) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
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.

You only have 767 MB of available Physical Memory (RAM).
Please get more memory if the system is able to handle it.
While waiting to upgrade the memory, please:
- only use one program at a time
- go through your startup items and stop those that aren't essential from loading with Windows

The dumps are suggestive of compatibility issues (because of the presence of hal.dll in the stack text) and they all blame nvstor32.sys (which dates from 2009)

I strongly suspect that this system isn't compatible w/W10 and that you won't be able to find significant updates for this driver from nVidia.

 

A question that's often asked is "Why did it work up until now?"

Most often this is because an incompatibility isn't necessarily exposed when an operating system is released.

But as the operating system is updated, the changes during the updates will sometimes expose incompatibilities later on.

So, I suspect that a Windows Update did something that wasn't compatible with the nvstor32.sys driver (or one of the other components related to it), and that caused the BSOD's to be generated under certain circumstances (and we don't kinow what those circumstances are).

 

In short, I'd suggest going back to the OS that the system came with - or purchasing a new system that's W10 compatible.

 

This does not mean that we're giving up on this system - and we'll continue to try and provide assistance for it.

 

Please notice the drivers below that date from before the release of Windows 10 (July of 2015).

You should try and update them to versions that are compatible w/W10

In the event that they aren't compatible, then they should be uninstalled (but drivers like the nvstor32.sys driver shouldn't be uninstalled - as they are a part of the chipset, and you can't compute without them).

 

The GEARAspiWDM.sys driver is usually a part of iTunes, and is usually stable with the version dated from 2012 (as yours is).

It's safe to leave in place.

The MpKsl50f4fa82.sys is a dynamically generated driver for Microsoft Secruity Essentials.

Still, it's out of date and that program should probably be uninstalled (and then enable Windows Defender)
But I'm not a security expert, so I'm not sure how they are related.

 

In short, the nvstor32.sys driver should be updated (if you can find one at the nVidia website).

Even if it's not a W10 compatible version - it's possible that it was changed enough that it won't crash as badly as the current driver (and the only way to tell is to try it).

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Dec 12 00:42:06.443 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121116-27250-01.dmp]
Windows 10 Kernel Version 14393 MP (2 procs) Free x86 compatible
Built by: 14393.479.x86fre.rs1_release.161110-2025
System Uptime:1 days 0:15:23.719
*** WARNING: Unable to verify timestamp for nvstor32.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor32.sys
Probably caused by :nvstor32.sys ( nvstor32+dc65 )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 00000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 00000501, The DPC time count (in ticks).
Arg3: 00000500, The DPC time allotment (in ticks).
Arg4: 00000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_DPC_nvstor32!unknown_function
  BIOS Version                   5.13
  BIOS Release Date             10/29/2007
  Manufacturer                  HP-Pavilion
  Baseboard Manufacturer        ASUSTek Computer INC.
  Product Name                  GX614AA-ABA a6330f
  Baseboard Product             NARRA2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 11 00:25:25.334 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121016-26984-01.dmp]
Windows 10 Kernel Version 14393 MP (2 procs) Free x86 compatible
Built by: 14393.479.x86fre.rs1_release.161110-2025
System Uptime:1 days 0:15:23.734
*** WARNING: Unable to verify timestamp for nvstor32.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor32.sys
Probably caused by :nvstor32.sys ( nvstor32+dc65 )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 00000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 00000501, The DPC time count (in ticks).
Arg3: 00000500, The DPC time allotment (in ticks).
Arg4: 00000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_DPC_nvstor32!unknown_function
  BIOS Version                   5.13
  BIOS Release Date             10/29/2007
  Manufacturer                  HP-Pavilion
  Baseboard Manufacturer        ASUSTek Computer INC.
  Product Name                  GX614AA-ABA a6330f
  Baseboard Product             NARRA2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec  9 22:42:36.743 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120916-52296-01.dmp]
Windows 10 Kernel Version 14393 MP (2 procs) Free x86 compatible
Built by: 14393.447.x86fre.rs1_release_inmarket.161102-0100
System Uptime:1 days 0:16:26.734
*** WARNING: Unable to verify timestamp for nvstor32.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor32.sys
Probably caused by :nvstor32.sys ( nvstor32+dc65 )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 00000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 00000501, The DPC time count (in ticks).
Arg3: 00000500, The DPC time allotment (in ticks).
Arg4: 00000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID: 0x133_DPC_nvstor32!unknown_function
  BIOS Version                   5.13
  BIOS Release Date             10/29/2007
  Manufacturer                  HP-Pavilion
  Baseboard Manufacturer        ASUSTek Computer INC.
  Product Name                  GX614AA-ABA a6330f
  Baseboard Product             NARRA2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



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:

**************************Mon Dec 12 00:42:06.443 2016 (UTC - 5:00)**************************
mdmxsdk.sys                  Mon Jun 19 17:26:59 2006 (449716A3)
RTKVHDA.sys                  Thu Oct 25 02:25:38 2007 (472036E2)
HSX_DP.sys                   Fri Feb 13 15:56:27 2009 (4995DE7B)
HSX_CNXT.sys                 Fri Feb 13 15:57:25 2009 (4995DEB5)
HSXHWBS2.sys                 Fri Feb 13 15:58:27 2009 (4995DEF3)
XAudio32.sys                 Wed Apr 29 14:20:55 2009 (49F89A87)
nvstor32.sys                 Mon Jun 22 18:19:03 2009 (4A400357)
nvmf6232.sys                 Wed Apr 20 18:49:15 2011 (4DAF62EB)
GEARAspiWDM.sys              Thu May  3 15:55:59 2012 (4FA2E2CF)
point32.sys                  Wed Jan  9 06:15:09 2013 (50ED513D)
MpKsl50f4fa82.sys            Tue May 19 21:33:53 2015 (555BE481)
NuidFltr.sys                 Tue Oct 27 14:14:37 2015 (562FBF0D)
dc3d.sys                     Fri Nov  6 14:13:31 2015 (563CFBDB)
nvvad32v.sys                 Tue Apr 12 04:46:37 2016 (570CB5ED)
NvStreamKms.sys              Fri Jun  3 07:28:20 2016 (575169D4)
WirelessKeyboardFilter.sys   Sat Jun 25 03:14:19 2016 (576E2F4B)
nvhda32v.sys                 Thu Sep 29 09:24:46 2016 (57ED161E)
nvlddmkm.sys                 Thu Nov 24 14:04:25 2016 (583739B9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec  7 17:36:54.021 2016 (UTC - 5:00)**************************
afcdp.sys                    Wed Jul 20 10:46:28 2011 (4E26EA44)
snapman.sys                  Wed Jan 16 08:44:45 2013 (50F6AECD)
vidsflt.sys                  Thu Feb 14 02:05:15 2013 (511C8CAB)
fltsrv.sys                   Fri Mar  1 08:54:14 2013 (5130B306)
tib.sys                      Wed Mar 20 04:59:41 2013 (51497A7D)
MpKslDrv.sys                 Tue May 19 21:33:53 2015 (555BE481)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec  3 18:14:52.048 2016 (UTC - 5:00)**************************
NvStreamKms.sys              Sat Jul 25 05:22:13 2015 (55B35545)
nvvad32v.sys                 Mon Aug 10 03:51:30 2015 (55C85802)
nvhda32v.sys                 Tue May 10 04:58:49 2016 (5731A2C9)
nvlddmkm.sys                 Fri Sep 16 18:20:14 2016 (57DC701E)

http://www.carrona.org/drivers/driver.php?id=mdmxsdk.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHDA.sys
http://www.carrona.org/drivers/driver.php?id=HSX_DP.sys
http://www.carrona.org/drivers/driver.php?id=HSX_CNXT.sys
http://www.carrona.org/drivers/driver.php?id=HSXHWBS2.sys
http://www.carrona.org/drivers/driver.php?id=XAudio32.sys
http://www.carrona.org/drivers/driver.php?id=nvstor32.sys
http://www.carrona.org/drivers/driver.php?id=nvmf6232.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=point32.sys
MpKsl50f4fa82.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=NuidFltr.sys
http://www.carrona.org/drivers/driver.php?id=dc3d.sys
http://www.carrona.org/drivers/driver.php?id=nvvad32v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
WirelessKeyboardFilter.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvhda32v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=afcdp.sys
http://www.carrona.org/drivers/driver.php?id=snapman.sys
http://www.carrona.org/drivers/driver.php?id=vidsflt.sys
http://www.carrona.org/drivers/driver.php?id=fltsrv.sys
http://www.carrona.org/drivers/driver.php?id=tib.sys
MpKslDrv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvvad32v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda32v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 


Edited by usasma, 13 December 2016 - 10:26 AM.

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.

#6 user234

user234
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:27 PM

Posted 13 December 2016 - 01:04 PM

Thank You usasma for all your hard work. I will see what updates I can find. Probably end up replacing the video card as I doubt I can find a driver that will work. I wish now I would have told my friend just to buy a new computer. Thanks again for your help.



#7 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:08:27 PM

Posted 15 December 2016 - 05:57 AM

Unfortunately, this is a storage controller driver that's causing the problem.  As such, even replacing the video card may not fix the problem.

The storage controller resides on the motherboard, and is a part of the nForce chipset (which is no longer updated and isn't compatbile w/W10)

 

If the problem continues, the best solution would be to go back to the original OS while waiting to purchase a new system.


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.

#8 user234

user234
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:27 PM

Posted 15 December 2016 - 09:14 AM

​Yes we have decide to put in a new motherboard and processor & memory to solve the problem. Thank You for all your help.



#9 JohnC_21

JohnC_21

  • Members
  • 24,668 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:27 PM

Posted 15 December 2016 - 10:05 AM

usasma can verify this but if you replace the motherboard, CPU, and memory, your Windows 10 license may no longer be valid and you would need to purchase a new license. If the motherboard and processor are identical to what is currently in the computer it may work.

 

What is the model number of the HP. If it came pre-installed with Windows 8 you could clean install 8.1 and see if the BSOD returns before purchasing any new hardware.


Edited by JohnC_21, 15 December 2016 - 10:05 AM.


#10 baines77

baines77

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Washington, D.C.
  • Local time:07:27 PM

Posted 15 December 2016 - 10:11 AM

The upgrades to WIN10 create an ID of sorts (gone is the key) that is stored in the UEFI/firmware.  If you replace your hardware, Windows won't activate.  You would have to load whatever the native OS that came with the system was with the key you have when you purchased it.  Aside from that, you're spending hundreds in new hardware and possibly a new OS.  Either revert back to 8 or whatever was on it or buy a new WIN10 box.  



#11 user234

user234
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:27 PM

Posted 15 December 2016 - 10:44 AM

So you are saying if I replaced the motherboard and processor and use the same hard drive which has windows 10 already on it that it won't stay activated, Can't use the same motherboard because that the problem. It came with vista. we brought window 7 pro. So can I put windows 7 pro back on and upgrade to windows 10 pro? We may find out as I have just brought the parts this morning.


Edited by user234, 15 December 2016 - 10:50 AM.


#12 baines77

baines77

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Washington, D.C.
  • Local time:07:27 PM

Posted 15 December 2016 - 10:50 AM

Correct, the 'key,' if you will, is held in the BIOS/Firmware on the MoBo.  If you replace it, you're taking the upgraded ID to WIN10 with it.  There are tools out there that can scan/read/pull that key, but that may only help on reloads on the existing hardware.  Swapping hardware may still result in issues activating Windows with that key since the hardware has changed.  



#13 user234

user234
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:27 PM

Posted 15 December 2016 - 11:33 AM

Thank you for your help. I did not even think about window 10 activation being a problem. I just order windows 10 so that should be all I need.



#14 JohnC_21

JohnC_21

  • Members
  • 24,668 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:27 PM

Posted 15 December 2016 - 11:42 AM

If this motherboard is HP branded with the same Nvidia controller chipset you will probably continue to receive BSODs when using Windows 10. 



#15 user234

user234
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:27 PM

Posted 15 December 2016 - 12:12 PM

No this is not an HP motherboard and it does not have Nvida on it. It is Asus board with AMD 760 G chipset. People who have brought this board says it runs windows 10 without any problems. Plus I put protection on it, since this is not my computer. They don't play games, so the onboard video should be fine for them. Had a time finding a motherboard that would fit the case, but I did find one.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users