random BSOD at start up - ntoskrnl.exe+75bc0

Question

random BSOD at start up - ntoskrnl.exe+75bc0

Anonymous

Hello,

I hope someone can give me some guidance about this issue, because I can't find the cause of this problem, and I've tried everything but formatting, and I don't like this solution.

those BSODs only occur on the windows 7 start up and sometimes doing the repair installation fix the problem for a couple days, and then I got the same BSOD again. Other times I have to do a complete chkdsk repair and sfc /scannow. If I try to reboot on safe mode it get stuck at classpnp.sys driver and then the same BSOD appears. I will post the complete information bellow. thanks in advance!

EDIT: here is the link for .dmp files as requested :

https://onedrive.live.com/?cid=f7592357d45c6469&id=F7592357D45C6469%21197

**UPDATE (FIX):**turns out the problem was my HDD. I had bad sectors growing up on the disk. I used the HD tune pro to confirm this. After I replaced it, the cumputer is good as new.

==================================================

Dump File : 043014-19546-01.dmp

Crash Time : 30/04/2014 19:11:45

Bug Check String : BAD_SYSTEM_CONFIG_INFO

Bug Check Code : 0x00000074

Parameter 1 : 00000000`00000002

Parameter 2 : fffff880`043f79e0

Parameter 3 : 00000000`00000002

Parameter 4 : ffffffff`c000014d

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+75bc0

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)

Processor : x64

Crash Address : ntoskrnl.exe+75bc0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\043014-19546-01.dmp

Processors Count : 4

Major Version : 15

Minor Version : 7601

Dump File Size : 273.088

Dump File Time : 30/04/2014 19:22:02

==================================================

Dump File : 042814-28735-01.dmp

Crash Time : 28/04/2014 20:16:54

Bug Check String : BAD_SYSTEM_CONFIG_INFO

Bug Check Code : 0x00000074

Parameter 1 : 00000000`00000002

Parameter 2 : fffff880`06b379e0

Parameter 3 : 00000000`00000002

Parameter 4 : ffffffff`c000014d

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+75bc0

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)

Processor : x64

Crash Address : ntoskrnl.exe+75bc0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\042814-28735-01.dmp

Processors Count : 4

Major Version : 15

Minor Version : 7601

Dump File Size : 268.920

Dump File Time : 28/04/2014 23:08:29

==================================================

Dump File : 042314-20529-01.dmp

Crash Time : 23/04/2014 19:02:34

Bug Check String : BAD_SYSTEM_CONFIG_INFO

Bug Check Code : 0x00000074

Parameter 1 : 00000000`00000002

Parameter 2 : fffff880`02b089e0

Parameter 3 : 00000000`00000002

Parameter 4 : ffffffff`c000014d

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+75bc0

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)

Processor : x64

Crash Address : ntoskrnl.exe+75bc0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\042314-20529-01.dmp

Processors Count : 4

Major Version : 15

Minor Version : 7601

Dump File Size : 272.160

Dump File Time : 23/04/2014 19:42:16

==================================================

Dump File : 041814-22417-01.dmp

Crash Time : 18/04/2014 10:47:36

Bug Check String : BAD_SYSTEM_CONFIG_INFO

Bug Check Code : 0x00000074

Parameter 1 : 00000000`00000002

Parameter 2 : fffff880`06b5e9e0

Parameter 3 : 00000000`00000002

Parameter 4 : ffffffff`c000014d

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+75bc0

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)

Processor : x64

Crash Address : ntoskrnl.exe+75bc0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\041814-22417-01.dmp

Processors Count : 4

Major Version : 15

Minor Version : 7601

Dump File Size : 273.088

Dump File Time : 18/04/2014 11:43:51

==================================================

Dump File : 040314-38797-01.dmp

Crash Time : 03/04/2014 19:24:48

Bug Check String : BAD_SYSTEM_CONFIG_INFO

Bug Check Code : 0x00000074

Parameter 1 : 00000000`00000002

Parameter 2 : fffff880`0694c9e0

Parameter 3 : 00000000`00000002

Parameter 4 : ffffffff`c000014d

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+75bc0

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)

Processor : x64

Crash Address : ntoskrnl.exe+75bc0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\040314-38797-01.dmp

Processors Count : 4

Major Version : 15

Minor Version : 7601

Dump File Size : 268.920

Dump File Time : 03/04/2014 19:31:29

==================================================

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

4 additional answers

Answer 1

Thanks for the dumps!

All of the attached DMP files are of the BAD_SYSTEM_CONFIG_INFO (0x74) bug check.

The BAD_SYSTEM_CONFIG_INFO bug check occurs if the SYSTEM hive is corrupt. However, this corruption is usually unlikely, because the boot loader, known as NT Loader (NTLDR) in versions of Windows prior to Vista, checks a hive for corruption when it loads the hive.

This bug check can also occur if some critical registry keys and values are missing. Thee keys and values might be missing if a user manually edited the registry.

--------------

Unfortunately, and I always hate to say this, this is a bug check that the only usual workaround is to do a clean install of Windows as there is no way to 'repair' a registry that is so corrupted that it leads to this bug check. The only other thing aside from a clean install that works (but usually never does) is attempting to load a Last Known Good Configuration via the Boot Options.

Regards,

Patrick

Answer 2

My pleasure, and just about anything can cause this from malware, file system corruption over time, etc.

If and when you are comfortable and feel your issue has been solved, I'd recommend marking any posts of mine that answered your question as answered so this thread no longer shows up as requiring an answer.

Regards,

Patrick

Answer 3

Anonymous

I see. well...since I will have to do a clean Install, I might as well upgrade it to Windows 8.

What really grinds my gears is not being able to know what have caused this bug.

Thank you for your clarification.

0 comments

Answer 4

Anonymous

Thanks for the quick reply Patrick!

I've added the .dmp file on the original post. Let me know if I did it correctly.

Thank you again for spend your time on this! I really apreciatted that.

0 comments

Answer 5

Hi,

In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

If you don't know where .DMP files are located, here's how to get to them:

1. Navigate to the %systemroot%\Minidump folder.

2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

If you are going to use Onedrive but don't know how to upload to it, please visit the following:

Upload photos and files to Onedrive.

Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick

Share via

random BSOD at start up - ntoskrnl.exe+75bc0

4 additional answers