Hello Marco, and welcome to Seven Forums.
Are you able to set everything under "System failure", "Write debugging information", and "Dump file"? This is what is key to be set instead.
Once that is set, see if you are able to do the instructions below to post your BSOD thread with.
Blue Screen of Death (BSOD) Posting Instructions
I can change all the settings in the part below. So yes, but everything in the above part I can not change.
It looks like the following picture:
http://ptpimg.me/8f39m9.jpg
It's in Dutch, but I hope that is not a problem.
Options are the same as written in this tutorial.
I'm now of to the instructions of my BSOD..........
I followed the instructions and the following ZIP file was created.
I uploaded it and hope you can see the zip file.
I am not sure if it is correct to post the ZIP file here, or in another post specially for BSOD, but please tell me.
FYI: the first message was that the program was not able to find any dump file.
The image link is broken. Try posting it using the method below instead.
Screenshots and Files - Upload and Post in Seven Forums
In addition, post a screenshot of the boot tab in msconfig to see if it shows the same.
You'll need to create a new thread for the BSOD issue instead since it's off topic from this tutorial.
Windows 7 Help Forums - FAQ: Board FAQ
Sorry about the picture. Hereby the first picture:
And in addition to your request another picture from my msconfig, first tab. I''m not sure if this is the tab you want to see:
I will create another post for my BSOD porblem, but first I want to post here to get clear why I am not able to make a dump file.
It should be the "Computer opstarten" tab in msconfig instead.
If it's empty as well, then type bcdedit in an elevated command prompt, and post the results to see what it says. :)
Sorry for the wrong picture ;-)
Here is the correct one and indeed it is empty:
So I tried to execute bcdedit in the "elevated command prompt", but this doesn't work with me. I tried the 3 different options to get into the elevated command prompt. All the times my command opens in C:\Users\(user name) instead of C:\Windows\System32. When I go manually with dos commando's to the windows\system32 directory and execute bcdedit.exe I get the message that the archive with configuration options can not be opened.
info of my command prompt:
It's saying this below for your boot file. See if doing a startup repair may be able to repair this for now.
Please go ahead and post a screenshot of your Disk management to see if anything may be wrong there as well.Code:Can not boot configuration data does not open the archive. The system can not find the file specified.
Disk Management - Post a Screen Capture Image
Last edited by Brink; 07 Jun 2014 at 15:00. Reason: typo
It did take some time because I have a Win7 OEM so I had to create a system repair disc first.
After creating the disc I started my PC on the newly created disc and used the startup repair.
It came up with the message "startup repair could not detect a problem".
I tried again to get into the elevated command prompt without succes. But did not see the "lnk" that could be downloaded. I used the lnk on my desktop screen and yes the command prompt started up at the windows/system32 directory. But after giving the command bcdedit or even bcdedit.exe the following message came up; bcdedit is not recognized as an internal or external command, program or batch.
As you requested a picture of my disk management.
And FYI I have problems ther too ;-)
When a new external HD is connected I have to go into the disk management to point manually a specific drive letter. It is not down automaticly. When this is done, the next time the drive letter is recognized, but when another new external HD is connected I have to do the manual work again.
I don't see anything wrong in Disk Management for your Windows drive.
You're CD-rom-station 0 should not be RAW though. Could be an issue with the DVD in it.
For now, see if doing either a system restore using a restore point dated before this issue, or a sfc /scannow command may be able to let you get a dump file after a BSOD.
Afterwards, go ahead and pursue the BSOD issue in a new thread to see what may turn up about it.
Thank you!
I'will try the sfc /scannow option.
After that I will open a new post in the BSOD forum and hope for a solution.
Quote
