I need help repairing Windows server 2012 r2 from the installation disk.

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
I need help repairing Windows server 2012 r2 from the installation disk but I can't figure out how. When I try to boot up into Safe mode but I get the kmode exception_not handled error. The only thing I could find on the error is to boot into safe mode which isn't exactly helpful. I am not familiar with the process of repairing Windows from the install disk in 8.1/2012. There isn't a repair option that I've found. I tried the steps here Your PC needs to be repaired: Fix for Windows 8, 8.1 but got an error that no OS was found. The disk isn't encrypted so I don't know why that's happening. I've found plenty on a repair install but you have to be in windows to do that and I can't get into Windows in normal mode. I don't know if the 8 forums is active but no one responded there. This is a complicated mess that I don't know how to get out of it except through a clean install and I don't want to do that. The system specs are under system 2 in my system spcs. TIA.
 
Windows Version
2012 R2

My Computers

System One System Two

johngalt

Well-known member
WQ Insider
Member
VIP
Local time
3:44 PM
Posts
732
Location
3rd Rock
Wait, so when you boot off the server 2012 R2 disc, you don't have a "Repair" option at the bottom left?

Odd.

See Repairing a Windows Installation 2012 R2 for reference.

Just as with a multitude of Windows installers, going back to at least Windows 7, when it presents you with the option to install, at the bottom left there should be a 'link' to repair.

However, you need to boot from the installer disc itself, not try to boot into Safe mode on the server.
 

My Computer

System One

  • Operating System
    Windows 10 Pro X64
    Computer type
    PC/Desktop
    Manufacturer/Model
    The Beast Model A (homebrew)
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * Corsair Vengeance 32 GB 3600 MHz
    Graphics Card(s)
    eVGA GeForce GTX 970 SSC ACX 2.0 (04G-P4-3979-KB)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2 * Lenovo LT2323pwA Widescreeen @ 1920*1080
    Hard Drives
    3x Sabrent Rocket PCIe Gen4 NVMe M.2 1 TB SSD (SB-ROCKET-NVMe4-1TB)
    SanDisk Ultra SDSSDHII-960G-G25 960 GB SATA III SSD
    2 * Seagate Barracuda 7200.12 ST31000528AS 1TB 7200 RPM --> RAID1
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler + Air (3 * 140mm fans from case)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3 Wireless Laser Mouse(shared)
    Internet Speed
    AT&T Lightspeed Gigabit duplex
    Browser
    Nightly|Chrome|Canary|Edge+ (Chromium) (in all 4 flavors)
    Antivirus
    Windows Defender + MB 4

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
Thanks for your reply. Yes I was booting into the disk (to be exact a bootable USB). I do have the repair but the only options are to continue/exit, troubleshoot (which brings up the command prompt), and turn off your pc. I don't have an automated repair option like on 7 or an OS to select like your link says. I do see in the instructions to try an sfc. I can't try that now though. I'll try tomorrow afternoon and let you know.
 

My Computers

System One System Two

philc43

BSOD Analyst
MVP
Member
VIP
Local time
8:44 PM
Posts
150
Location
Cambridge, UK
That would be helpful to run SFC. If it does not complete please provide the CBS.log file; either zip it or share it from OneDrive or Dropbox.
 

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

johngalt

Well-known member
WQ Insider
Member
VIP
Local time
3:44 PM
Posts
732
Location
3rd Rock
^^^^ This.
 

My Computer

System One

  • Operating System
    Windows 10 Pro X64
    Computer type
    PC/Desktop
    Manufacturer/Model
    The Beast Model A (homebrew)
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * Corsair Vengeance 32 GB 3600 MHz
    Graphics Card(s)
    eVGA GeForce GTX 970 SSC ACX 2.0 (04G-P4-3979-KB)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2 * Lenovo LT2323pwA Widescreeen @ 1920*1080
    Hard Drives
    3x Sabrent Rocket PCIe Gen4 NVMe M.2 1 TB SSD (SB-ROCKET-NVMe4-1TB)
    SanDisk Ultra SDSSDHII-960G-G25 960 GB SATA III SSD
    2 * Seagate Barracuda 7200.12 ST31000528AS 1TB 7200 RPM --> RAID1
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler + Air (3 * 140mm fans from case)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3 Wireless Laser Mouse(shared)
    Internet Speed
    AT&T Lightspeed Gigabit duplex
    Browser
    Nightly|Chrome|Canary|Edge+ (Chromium) (in all 4 flavors)
    Antivirus
    Windows Defender + MB 4

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
I'm unable to login in normal mode due to the time being off. I could easily take care of that if I could boot into safe more but then there is that BSOD.
 
Last edited:

My Computers

System One System Two

philc43

BSOD Analyst
MVP
Member
VIP
Local time
8:44 PM
Posts
150
Location
Cambridge, UK
I'm unable to login in normal mode due to the time being off. I could easily take care of that if I could boot into safe more but then there is that BOSD.
I thought you were going to boot via the Installation usb drive and then select repair option to access the command prompt. This should allow you to run SFC.
 

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
I am but I can't get into Windows directly to get the logs if the repair doesn't work. I suppose I could do so through Linux but since it keeps messing up the time I think that I am going to stop going into Linux if I can get this fixed. I could also put the hdd in an enclosure or into my desktop but that would require removing it and the screwless drive mounting in my server is strange and a pain. Basically it won't so easy to get those logs.

Any idea why the time is wrong? It's set about 22 hours into the future. I've tried changing it on the bios and from the command prompt accessed under troubleshooting. Neither sticks when I boot into Windows normally. The system isn't even a year and a half old which is way too young for the cmos battery to go out. Never the less I changed the cmos battery but that didn't fix it. I never suspected that because it isn't defaulting to a date/year in the past on boot up. I've had this happen before but changing the time in the bios resolved the issue. Not this time. It's been frustrating.
 

My Computers

System One System Two

philc43

BSOD Analyst
MVP
Member
VIP
Local time
8:44 PM
Posts
150
Location
Cambridge, UK
You can use Command Prompt to access the file and copy it to a USB drive. It will be found in %SystemRoot%\Logs\CBS\CBS.log
 

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
I tried the sfc and it did "beginning verification phase of system scan." After a few seconds It reached 100% and the said "Windows resource protection could not perform the requested operation." I think that there is a second phase right? I thought that there my be an issue with having multiple hard drives and OSs so I removed the power from the other 2 drives. It still didn't work. When getting the file I noticed that the Windows driver letter is f. Could that be why it isn't working? I got the cbs log file and I'm attaching today's portion as requested.
 

Attachments

  • CBS.zip
    19.3 KB · Views: 12
Last edited:

My Computers

System One System Two

philc43

BSOD Analyst
MVP
Member
VIP
Local time
8:44 PM
Posts
150
Location
Cambridge, UK
What command did you use? When using SFC in this mode you need to tell it which drive to test and where to get the files from.

See this tutorial option1 -> Run SFC Command in Windows 10
It should work the same in your OS.
 

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
I've tried SFC once and the first time it said that it fixed some corrupted files but it still won't boot into safe mode. I wanted to check the syntax of the command. I don't have anything listed as a windows partition or system reserved so based on the volume sizes I guessed on what to put in my command. List volume has volume 0 with the c label. It is a 2048 MB Fat32 partition. I figured that this is the recovery and put that down for offbootdir because nothing else fits. Volume 1 with a drive letter of e is the windows drive since it is shown as the 929 GB partition and my main drive is 1 tb. I put that in offwindir. Volume 2 is a 29 gb ntfs partition and it shows as a removable type. I know that's my installation USB. Volume 3 is a 101 MB fat volume without a drive letter. So I put sfc /scannow /offbootdir=c:\ /offwindir=e:\windows. Is that correct?

i decided to try it again and the second time it ran it returned no integrity violations after running for about 20 minutes. However I still get a bsod when trying to boot into safemode.
 

My Computers

System One System Two

philc43

BSOD Analyst
MVP
Member
VIP
Local time
8:44 PM
Posts
150
Location
Cambridge, UK
If you are getting a blue screen when booting into safe mode - this generally indicates a hardware problem. Try replacing RAM with another module for testing. Try running the DELL hardware/diagnostic tests

The time difference you get in normal mode suggests you may be using a different time zone / country code for your system settings. Have you checked that these are all correct?
 

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
I can't login. Is there a way to check that without logging in? The tzutil command isn't built into the recovery console. If there is a hardware issue why do I have no problems booting into normal mode? I don't have a compatible stick of memory to check.

I don't think that the time zone/country code is wrong in Windows. If it's wrong in Linux could that change Windows even though they have separate bootloaders?
 
Last edited:

My Computers

System One System Two

philc43

BSOD Analyst
MVP
Member
VIP
Local time
8:44 PM
Posts
150
Location
Cambridge, UK
If you can access the Bios can you try updating the Bios. There may be an update. Check on the Dell website.

As for the BSOD, there may be crash dump files we can examine. They will be found in c:\windows\minidump - copy them via command prompt and then zip them and post.
 

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
There's no minidump folder or memory.dmp file. When it bluescreens it's sits on 0% and doesn't progress. I wonder if that's because the folder is missing. Do I need to create it? It isn't on my 8.1 desktop either.

What makes you think that a bios update will help? I don't like to do those.
 

My Computers

System One System Two

philc43

BSOD Analyst
MVP
Member
VIP
Local time
8:44 PM
Posts
150
Location
Cambridge, UK
You will not need to create the minidump folder - it will be created when a crash dump file is saved. The fact that there are none there shows that the BSOD is occurring very early in the boot process.

Sometimes BIOS updates can help fix issues that appear to be hardware related. I was asking you to check if there were any updates. I do not know what version of the BIOS you have on your server. There was an urgent BIOS update released on 8 Jun 2021 for the T140:

There may be other important updates for the T140 that you need to consider.
 

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
I was able to update the bios, which I can confirm from the splash screen, but the time problem still exists as does the BSOD when booting into safe-mode. The error collection is sitting at 0%. Any other suggestions?
 

My Computers

System One System Two

zbook

Active Member
Member
VIP
Local time
2:44 PM
Posts
275
Please indicate what happens when
a) the computer is shut down and started.
b) the computer is restarted
c) the computer is restarted into safe mode

Run the V2 log collector and upload results into this thread:
(see BSOD posting instructions)
 

My Computer

System One

  • Operating System
    Windows 10

townsbg

~~тσωηsвg~~
VIP
Local time
2:44 PM
Posts
18
Location
US of A
Thread starter
Please indicate what happens when
a) the computer is shut down and started.
b) the computer is restarted
c) the computer is restarted into safe mode

Run the V2 log collector and upload results into this thread:
(see BSOD posting instructions)

a) Boots successfully into regular mode.
b) Boots successfully into regular mode.
c) Blue screens with error kmode exception_not handled

As stated I am unable to login from normal mode due to security software I have installed. It is rejecting my login since the date/time is incorrect. Because of that I can't run your log collector. I either need to fix the time issue and have it stick or boot into safe mode from which I can uninstall the software.
 
Last edited:

My Computers

System One System Two

Top