Bad system config info
Please help, I turned on my computer today and it was in a bios, when I chose save and exit it said: "Your pc ran into a problem..." windows 10 x64 pro
< >
Показані коментарі 19 із 9
BAD SYSTEM CONFIG INFO
I have that win I reboot only, try reset your bios back to default, I am going to do a reinstall on October 17 win the new windows 10 new version comes out.

save and exit it said: boom "reset your bios back to default, "

Windows 10 BAD_SYSTEM_CONFIG_INFO error

http://www.tomshardware.com/faq/id-3127605/fix-windows-bad-system-config-info-error.html

nice tool BlueScreenView scans all your minidump files

BlueScreenView
http://www.nirsoft.net/utils/blue_screen_view.html

Dump File : 090817-11937-01.dmp
Crash Time : 9/8/2017 10:39:57 AM
Bug Check String : BAD_SYSTEM_CONFIG_INFO
Bug Check Code : 0x00000074
Parameter 1 : 00000000`00000002
Parameter 2 : ffff9401`f819e9f0
Parameter 3 : 00000000`00000002
Parameter 4 : ffffffff`c000009a
Caused By Driver : NTFS.sys
Caused By Address : NTFS.sys+f28b8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c560
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090817-11937-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 15063
Dump File Size : 473,436
Dump File Time : 9/8/2017 10:41:23 AM
==================================================
Автор останньої редакції: rotNdude; 9 верес. 2017 о 9:15
Цитата допису OLD*MAN:
Windows 10 BAD_SYSTEM_CONFIG_INFO error

http://www.tomshardware.com/faq/id-3127605/fix-windows-bad-system-config-info-error.html

nice tool BlueScreenView scans all your minidump files

BlueScreenView
http://www.nirsoft.net/utils/blue_screen_view.html

Dump File : 090817-11937-01.dmp
Crash Time : 9/8/2017 10:39:57 AM
Bug Check String : BAD_SYSTEM_CONFIG_INFO
Bug Check Code : 0x00000074
Parameter 1 : 00000000`00000002
Parameter 2 : ffff9401`f819e9f0
Parameter 3 : 00000000`00000002
Parameter 4 : ffffffff`c000009a
Caused By Driver : NTFS.sys
Caused By Address : NTFS.sys+f28b8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c560
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090817-11937-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 15063
Dump File Size : 473,436
Dump File Time : 9/8/2017 10:41:23 AM
==================================================
Not working
Are you continuing to reboot without turning off the PC?
Power off the PC, disconnect the Power Supply main power cable from the rear, then press and hold Power Button on your Case for 10-15 seconds. Then re-connect main power cable and power the system back on again. See if Windows throws up any errors.
BAD SYSTEM CONFIG INFO
Is caused by changing the Bios setting, If you can remember the setting you change just put it back, or reset bios back to default.
Цитата допису Bad_Motha:
Are you continuing to reboot without turning off the PC?
Power off the PC, disconnect the Power Supply main power cable from the rear, then press and hold Power Button on your Case for 10-15 seconds. Then re-connect main power cable and power the system back on again. See if Windows throws up any errors.
How is that gonna work if there is no power in a pc

Цитата допису OLD*MAN:
BAD SYSTEM CONFIG INFO
Is caused by changing the Bios setting, If you can remember the setting you change just put it back, or reset bios back to default.
I didnt do anything in bios
Автор останньої редакції: rotNdude; 9 верес. 2017 о 9:15
You might have dead cmos battery check the bios time and date, how old is your system
The normal life of a CMOS battery is 3 to 5 years. To be honest i've had them last up to 6 years. It is diffcult to say why your battery has died after just two years, it maybe just an inferior battery.
Цитата допису OLD*MAN:
You might have dead cmos battery check the bios time and date, how old is your system
The normal life of a CMOS battery is 3 to 5 years. To be honest i've had them last up to 6 years. It is diffcult to say why your battery has died after just two years, it maybe just an inferior battery.
My system is 2 days old
Bad system config info
All about BAD_SYSTEM_CONFIG_INFO

First off, the BAD_SYSTEM_CONFIG_INFO error is caused by faults in your computer’s registry. With names like Blue Screen of Death and Registry being tossed around, you’re probably pretty worried right about now — let me explain what these things are before we proceed.

The Registry of your computer is, more or less, its table of contents. This table of contents is used to locate everything on your computer, from your operating system to your favorite web browser, to your songs and games. If the registry is damaged, especially the parts leading to the operating system, then you’re going to get this error and your computer is likely going to be rendered unusable for the time being.

A Blue Screen of Death is an error encountered whenever your computer encounters something it can’t process. It shuts itself down to prevent further damage, and in most cases that’s the end of your worries — most people never encounter the BSoD again, and even if they have frequent problems with it, it’s usually fixable.

In this case, however, the damage done is severe. There are three possible problems: faulty memory (RAM), a faulty hard drive, or a program that’s damaged your registry.

To test the former, remove your RAM sticks and leave only one in, testing which stick won’t let your system boot. If none of them are the source of the problem, it’s not a RAM issue — and if you don’t know how to do this, get a technician.

Next, you should try to let Windows use Startup Repair to fix your problem or boot from a Last Known Good Configuration. If neither of these work, then you’re going to have to get your hard drive replaced — because either your hard drive is faulty or a program damaged your registry beyond repair.

You can also try our Registry Reviver and see whether its registry cleaning and optimizing properties can clear up this particular error.

For further assistance, contact your manufacturer or Microsoft.
https://www.reviversoft.com/blog/2013/05/bad-system-config-info/
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x74--bad-system-config-info
don't F with there Registry Reviver

You can use system restore point
https://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/
Автор останньої редакції: rotNdude; 9 верес. 2017 о 9:16
Цитата допису Poop:
Цитата допису Bad_Motha:
Are you continuing to reboot without turning off the PC?
Power off the PC, disconnect the Power Supply main power cable from the rear, then press and hold Power Button on your Case for 10-15 seconds. Then re-connect main power cable and power the system back on again. See if Windows throws up any errors.
How is that gonna work if there is no power in a pc

You don't seem to understand or listen; so please, just take your PC to a repair shop.

You keep opening up tons of threads on these forums, instead of just using one thread regarding your system issues. Since you don't listen to good advice, then I guess we can't help you.
< >
Показані коментарі 19 із 9
На сторінку: 1530 50

Опубліковано: 8 верес. 2017 о 18:02
Дописів: 9