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

Registry Error BSOD (Windows 10)


  • Please log in to reply
5 replies to this topic

#1 EffectiveBones484

EffectiveBones484

  • Members
  • 87 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Howling Abyss
  • Local time:02:49 AM

Posted 09 March 2016 - 12:48 PM

I have been encountering frequent blue screens on one of my computers, usually displaying the message REGISTRY_ERROR. I created a topic in the Am I Infected? subforum but was redirected here. The bluescreen seems to only come up if the computer has been idle for more than 5 minutes, and always with the REGISTRY_ERROR code. Here is the information requested:

 

OS: Windows 10 Home

64 bit (I think)

Windows 8 was the original OS, but upgraded to 10 when it came out

Windows 8 came pre-installed, I upgraded to 10 myself.

The system is about three or four years old, I don't know exactly

I have never reinstalled the OS, Windows 10 has been installed since I upgraded it.

 

CPU: AMD A8-5500

Video Card: Integrated on the CPU

Motherboard: No idea

Power supply: No idea

 

System manufacturer: HP

Model Number: Pavilion p7-1534

 

Desktop

 

Zipped files are attached.

Attached Files



BC AdBot (Login to Remove)

 


#2 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 981 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:04:49 AM

Posted 09 March 2016 - 02:34 PM

Hi. . .
 
6 of the 7 dumps had a bugcheck = 0x51 - severe registry error
 
The other dump had a bugcheck = 0x109 - kernel corruption

 

The cause of the 0x51 BSOD could have been the same basic underlying cause of the 0x109 BSOD. A failing HDD could definitely be responsible for the 0x109 BSOD as well.
 
Run chkdsk /r  from an Admin CMD prompt screen (then reboot system. chkdsk will execute upon start-up) 
 
Run sfc /scannow  from an Admin CMD prompt screen
 
The only thing that I can think of that may have caused this rarely seen bugcheck  (0x51) is a problem with the HDD.
 
Run HDD diagnostics -- SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html
 
How long ago did the BSODs start? According to the system files (+ dumps), the first BSOD occurred on 2 March 2016. Nothing before that date? Any type of system problems before the first BSOD?

 

Windows was installed on 11 December 2015 (or initial boot up if the system is new).

 

Regards. . .
 
jcgriff2
 
 
 
 




Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030916-29984-01.dmp]

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Debug session time: Wed Mar  9 12:01:42.925 2016 (UTC - 5:00)

System Uptime: 0 days 14:37:16.732

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+cfaa )

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x51

PROCESS_NAME:  ngen.exe

FAILURE_BUCKET_ID:  0x51_nt!_??_::NNGAKEGL::_string_

Bugcheck code 00000051

Arguments 00000000`00000001 ffffc001`50af2000 00000000`cf42b1b4 00000000`000002d2

BiosVersion = 8.15

BiosReleaseDate = 01/23/2013

SystemManufacturer = Hewlett-Packard

SystemProductName = p7-1534

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030816-14453-01.dmp]

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Debug session time: Tue Mar  8 18:37:47.642 2016 (UTC - 5:00)

System Uptime: 0 days 0:11:04.502

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+cfaa )

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x51

PROCESS_NAME:  ngen.exe

FAILURE_BUCKET_ID:  0x51_nt!_??_::NNGAKEGL::_string_

Bugcheck code 00000051

Arguments 00000000`00000001 ffffc001`116f2000 00000000`cf42b1b4 00000000`000002d2

BiosVersion = 8.15

BiosReleaseDate = 01/23/2013

SystemManufacturer = Hewlett-Packard

SystemProductName = p7-1534

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030816-16687-01.dmp]

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Debug session time: Tue Mar  8 18:24:19.101 2016 (UTC - 5:00)

System Uptime: 0 days 0:13:31.866

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+cfaa )

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x51

PROCESS_NAME:  ngen.exe

FAILURE_BUCKET_ID:  0x51_nt!_??_::NNGAKEGL::_string_

Bugcheck code 00000051

Arguments 00000000`00000001 ffffc000`db70f000 00000000`cf42b1b4 00000000`000002d2

BiosVersion = 8.15

BiosReleaseDate = 01/23/2013

SystemManufacturer = Hewlett-Packard

SystemProductName = p7-1534

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030816-17328-01.dmp]

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Debug session time: Tue Mar  8 18:04:53.269 2016 (UTC - 5:00)

System Uptime: 0 days 0:24:25.033

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+cfaa )

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x51

PROCESS_NAME:  ngen.exe

FAILURE_BUCKET_ID:  0x51_nt!_??_::NNGAKEGL::_string_

Bugcheck code 00000051

Arguments 00000000`00000001 ffffc001`a74fe000 00000000`cf42b1b4 00000000`000002d2

BiosVersion = 8.15

BiosReleaseDate = 01/23/2013

SystemManufacturer = Hewlett-Packard

SystemProductName = p7-1534

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030816-21656-01.dmp]

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Debug session time: Mon Mar  7 21:22:20.869 2016 (UTC - 5:00)

System Uptime: 0 days 0:40:20.634

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+cfaa )

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x51

PROCESS_NAME:  ngen.exe

FAILURE_BUCKET_ID:  0x51_nt!_??_::NNGAKEGL::_string_

Bugcheck code 00000051

Arguments 00000000`00000001 ffffc001`9a108000 00000000`a947ae7b 00000000`000002d2

BiosVersion = 8.15

BiosReleaseDate = 01/23/2013

SystemManufacturer = Hewlett-Packard

SystemProductName = p7-1534

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030716-22109-01.dmp]

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Debug session time: Mon Mar  7 16:05:43.986 2016 (UTC - 5:00)

System Uptime: 4 days 22:08:17.752

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+cfaa )

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x51

PROCESS_NAME:  ngen.exe

FAILURE_BUCKET_ID:  0x51_nt!_??_::NNGAKEGL::_string_

Bugcheck code 00000051

Arguments 00000000`00000001 ffffc000`52d43000 00000000`a947ae7b 00000000`000002d2

BiosVersion = 8.15

BiosReleaseDate = 01/23/2013

SystemManufacturer = Hewlett-Packard

SystemProductName = p7-1534

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030216-30046-01.dmp]

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Debug session time: Wed Mar  2 17:45:02.606 2016 (UTC - 5:00)

System Uptime: 0 days 12:12:21.370

*** WARNING: Unable to verify checksum for win32k.sys

Probably caused by : memory_corruption

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

Bugcheck code 00000109

Arguments a3a01f59`57b1d670 b3b72bdf`aa2f7d19 fffff800`25df5be2 00000000`00000001

BiosVersion = 8.15

BiosReleaseDate = 01/23/2013

SystemManufacturer = Hewlett-Packard

SystemProductName = p7-1534

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 


Edited by jcgriff2, 09 March 2016 - 02:45 PM.

Microsoft MVP 2009-2015

#3 EffectiveBones484

EffectiveBones484
  • Topic Starter

  • Members
  • 87 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Howling Abyss
  • Local time:02:49 AM

Posted 09 March 2016 - 03:37 PM

I tried running CHKDSK, but it has been stuck at 11% for almost an hour now. Should I just restart and move to the next step?

To answer your question, we had no system problems before the first blue screen.



#4 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 981 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:04:49 AM

Posted 09 March 2016 - 04:28 PM

Hi. . .

 

Sounds like chkdsk hit a bad sector or a part of the HDD it can't get past.

 

Kill chkdsk however you can (even if you have to do a hard shutdown) and run SeaTools for DOS immediately.

 

Forget about SFC for now - that can be run later.

 

It seems likely that your hard drive is indeed failing.  I once had a hard drive that failed unexpectedly. I simply re-booted the system; came back 10 minutes later to find out in the end that my HDD failed during the reboot as I was unable to get into Windows.

 

Regards. . .

 

jcgriff2


Edited by jcgriff2, 09 March 2016 - 04:32 PM.

Microsoft MVP 2009-2015

#5 EffectiveBones484

EffectiveBones484
  • Topic Starter

  • Members
  • 87 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Howling Abyss
  • Local time:02:49 AM

Posted 09 March 2016 - 06:32 PM

The only way I can get out of the chkdsk is by hard shutdown, and every time I restart it, it launches right back into chkdsk and gets stuck again. I can't get into the desktop.



#6 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 981 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:04:49 AM

Posted 09 March 2016 - 11:08 PM

Run SeaTools for DOS HDD diagnostic test.

 

It is a DOS-based test; Windows does not load.

 

You boot your system with the SeaTools CD/DVD.

 

You may have to change BIOS to assure that the DVD drive is first - boot order.

 

Regards. . .

 

jcgriff2


Microsoft MVP 2009-2015




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users