Question Blue screen and buzzing sounds

[shuffler91]

While i was playing Rainbow Six last night the audio suddenly started making loud buzzing sound while it was frozen and then it just crashed and showed up a blue screen telling me that: PC/Device needs to be repaired

The boot configuration data file doesnt contain valid information for an operating system.

File:\Boot\BCD
Error Code: 0xc0000098

I tried using the repair option but that did not work instead i got this message:

Logfile: D\WINDOWS\System32\logfiles\\Srt\SrtTrail.txt

Reinstalled Windows 10 through USB but my monitor was just flashing, until i switched graphics card and put in an older one and it started working. I tried playing something in youtbe and the buzzing sound came again and stoped but it did not crash the PC.

CPU: AMD FX 8350
GPU: MSI GeForce GTX 960 4GB Gaming
RAM: Hyperx 16GB 1866mhz
Mobo: ASUS M5A97 R2.0
SSD: Samsung 850 Evo
HDD: Western Digital 1TB
PSU: XFX Pro Series 750W 80+ Bronze, XFX XPS-750W-SEW

 

[jankerson]

System specs including PSU make and model.

 

[johnbl]

0: kd> !error 0xc0000098
Error code: (NTSTATUS) 0xc0000098 (3221225624) - The volume for a file has been externally altered such that the opened file is no longer valid.

normally, you would not have your windows on drive d:

how many drives to you have in the system?

sometimes the drive letters get re numbered (re assigned) and your reserved volume gets assigned drive c: and your windows install becomes drive d: and the system will not boot.

you then have to boot off of a repair image and run some commands to do the repair.
run
diskpart.exe
list volume
exit

this will show the drive assignments and exit the program.

if the assignments are incorrect you will have to reassign the drive letters.

also, go into bios and check the date and time and see if it is correct. if it is set to defaults, the battery on the motherboard might have failed.

 

[shuffler91]

0: kd> !error 0xc0000098
Error code: (NTSTATUS) 0xc0000098 (3221225624) - The volume for a file has been externally altered such that the opened file is no longer valid.

normally, you would not have your windows on drive d:

how many drives to you have in the system?

sometimes the drive letters get re numbered (re assigned) and your reserved volume gets assigned drive c: and your windows install becomes drive d: and the system will not boot.

you then have to boot off of a repair image and run some commands to do the repair.
run
diskpart.exe
list volume
exit

this will show the drive assignments and exit the program.

if the assignments are incorrect you will have to reassign the drive letters.

also, go into bios and check the date and time and see if it is correct. if it is set to defaults, the battery on the motherboard might have failed.

I got 2. 1 ssd and a hdd. The hdd is split in 2 parts, couldnt get it in 1.

I always thought that windows was installed in c: drive not d:

btw when i open This Pc it shows the windows icon above the c: drive. Does that mean its installed in it ? i uploaded a picture of it.

http://


I went into the bios and the date and time was set right.

How do i know if the assignments are incorrect ?

 

[johnbl]

the reserved partition is small but it should be ok. looks like windows is currently installed on c: drivee

generally a buzzing sound happens when a gpu driver crashes because of a sound conflict.
often it will be a old motherboard sound driver conflicting with a GPU sound driver.

 

[shuffler91]

the reserved partition is small but it should be ok. looks like windows is currently installed on c: drivee

generally a buzzing sound happens when a gpu driver crashes because of a sound conflict.
often it will be a old motherboard sound driver conflicting with a GPU sound driver.

now that we know windows is on the c: drive, what should i do ?

 

[johnbl]

I would guess that a second drive bootable drive was plugged in and you have a intel sata driver. on the intel driver it tends to trigger the drive letters to get reassigned and you get a 50 /50 chance of it getting it correct. if it gets it wrong, i think the windows repair takes a wack at fixing it. it must be a new fix because before you had to manually fix the problem. Anyway, i think the repair detected the windows install on drive d: opened a log file on drive d: then logged what it was doing and then when it changed the drive letter back to c: it was not smart enough to have closed the log file and reopen it on the reassigned drive c: so that the next write to the log failed because the drive letter changed.
that would just be a bug in the repair tool.

in the end, does the machine boot ok? or do you still have a broken machine?

the reserved partition is small but it should be ok. looks like windows is currently installed on c: drivee

generally a buzzing sound happens when a gpu driver crashes because of a sound conflict.
often it will be a old motherboard sound driver conflicting with a GPU sound driver.

now that we know windows is on the c: drive, what should i do ?

 

[shuffler91]

I would guess that a second drive bootable drive was plugged in and you have a intel sata driver. on the intel driver it tends to trigger the drive letters to get reassigned and you get a 50 /50 chance of it getting it correct. if it gets it wrong, i think the windows repair takes a wack at fixing it. it must be a new fix because before you had to manually fix the problem. Anyway, i think the repair detected the windows install on drive d: opened a log file on drive d: then logged what it was doing and then when it changed the drive letter back to c: it was not smart enough to have closed the log file and reopen it on the reassigned drive c: so that the next write to the log failed because the drive letter changed.
that would just be a bug in the repair tool.

in the end, does the machine boot ok? or do you still have a broken machine?

the reserved partition is small but it should be ok. looks like windows is currently installed on c: drivee

generally a buzzing sound happens when a gpu driver crashes because of a sound conflict.
often it will be a old motherboard sound driver conflicting with a GPU sound driver.

now that we know windows is on the c: drive, what should i do ?

Actually, i got a SSD Samsung evo and a HDD Western Digital. Yes i got no problem with that now but sometimes i hear that weird sound when listening to music but no freezing or shutting down.

I noticed in the bios that there's two samsung ssd showing up. Wasent like that before
http://

Btw, doing a factory reset would that solve it ?

 

[johnbl]

I would not do a reset.
the new bios store a windows OS signiture in the bios firmware so it can check to see if the OS have been virus modified. I would leave both entries. I assue the one with the lesser file space is the current one.

I would guess that a second drive bootable drive was plugged in and you have a intel sata driver. on the intel driver it tends to trigger the drive letters to get reassigned and you get a 50 /50 chance of it getting it correct. if it gets it wrong, i think the windows repair takes a wack at fixing it. it must be a new fix because before you had to manually fix the problem. Anyway, i think the repair detected the windows install on drive d: opened a log file on drive d: then logged what it was doing and then when it changed the drive letter back to c: it was not smart enough to have closed the log file and reopen it on the reassigned drive c: so that the next write to the log failed because the drive letter changed.
that would just be a bug in the repair tool.

in the end, does the machine boot ok? or do you still have a broken machine?

the reserved partition is small but it should be ok. looks like windows is currently installed on c: drivee

generally a buzzing sound happens when a gpu driver crashes because of a sound conflict.
often it will be a old motherboard sound driver conflicting with a GPU sound driver.

now that we know windows is on the c: drive, what should i do ?

Actually, i got a SSD Samsung evo and a HDD Western Digital. Yes i got no problem with that now but sometimes i hear that weird sound when listening to music but no freezing or shutting down.

I noticed in the bios that there's two samsung ssd showing up. Wasent like that before
http://

Btw, doing a factory reset would that solve it ?

 

[shuffler91]

I would not do a reset.
the new bios store a windows OS signiture in the bios firmware so it can check to see if the OS have been virus modified. I would leave both entries. I assue the one with the lesser file space is the current one.

I would guess that a second drive bootable drive was plugged in and you have a intel sata driver. on the intel driver it tends to trigger the drive letters to get reassigned and you get a 50 /50 chance of it getting it correct. if it gets it wrong, i think the windows repair takes a wack at fixing it. it must be a new fix because before you had to manually fix the problem. Anyway, i think the repair detected the windows install on drive d: opened a log file on drive d: then logged what it was doing and then when it changed the drive letter back to c: it was not smart enough to have closed the log file and reopen it on the reassigned drive c: so that the next write to the log failed because the drive letter changed.
that would just be a bug in the repair tool.

in the end, does the machine boot ok? or do you still have a broken machine?

the reserved partition is small but it should be ok. looks like windows is currently installed on c: drivee

generally a buzzing sound happens when a gpu driver crashes because of a sound conflict.
often it will be a old motherboard sound driver conflicting with a GPU sound driver.

now that we know windows is on the c: drive, what should i do ?

Actually, i got a SSD Samsung evo and a HDD Western Digital. Yes i got no problem with that now but sometimes i hear that weird sound when listening to music but no freezing or shutting down.

I noticed in the bios that there's two samsung ssd showing up. Wasent like that before
http://

Btw, doing a factory reset would that solve it ?

Ok wont do that.
What about updating the bios ? havent been updated since 2013.

 

[johnbl]

a bios update and motherboard driver updates can help, they go together since some bios changes are made to update spec changes for drivers.
the bios update will also force the bios to rescan your hardware and re assign all of the hardware resources and rebuild the database of settings that it hands off to windows.

I would not do a reset.
the new bios store a windows OS signiture in the bios firmware so it can check to see if the OS have been virus modified. I would leave both entries. I assue the one with the lesser file space is the current one.

I would guess that a second drive bootable drive was plugged in and you have a intel sata driver. on the intel driver it tends to trigger the drive letters to get reassigned and you get a 50 /50 chance of it getting it correct. if it gets it wrong, i think the windows repair takes a wack at fixing it. it must be a new fix because before you had to manually fix the problem. Anyway, i think the repair detected the windows install on drive d: opened a log file on drive d: then logged what it was doing and then when it changed the drive letter back to c: it was not smart enough to have closed the log file and reopen it on the reassigned drive c: so that the next write to the log failed because the drive letter changed.
that would just be a bug in the repair tool.

in the end, does the machine boot ok? or do you still have a broken machine?

the reserved partition is small but it should be ok. looks like windows is currently installed on c: drivee

generally a buzzing sound happens when a gpu driver crashes because of a sound conflict.
often it will be a old motherboard sound driver conflicting with a GPU sound driver.

now that we know windows is on the c: drive, what should i do ?

Actually, i got a SSD Samsung evo and a HDD Western Digital. Yes i got no problem with that now but sometimes i hear that weird sound when listening to music but no freezing or shutting down.

I noticed in the bios that there's two samsung ssd showing up. Wasent like that before
http://

Btw, doing a factory reset would that solve it ?

Ok wont do that.
What about updating the bios ? havent been updated since 2013.

 

[shuffler91]

a bios update and motherboard driver updates can help, they go together since some bios changes are made to update spec changes for drivers.
the bios update will also force the bios to rescan your hardware and re assign all of the hardware resources and rebuild the database of settings that it hands off to windows.

I would not do a reset.
the new bios store a windows OS signiture in the bios firmware so it can check to see if the OS have been virus modified. I would leave both entries. I assue the one with the lesser file space is the current one.

I would guess that a second drive bootable drive was plugged in and you have a intel sata driver. on the intel driver it tends to trigger the drive letters to get reassigned and you get a 50 /50 chance of it getting it correct. if it gets it wrong, i think the windows repair takes a wack at fixing it. it must be a new fix because before you had to manually fix the problem. Anyway, i think the repair detected the windows install on drive d: opened a log file on drive d: then logged what it was doing and then when it changed the drive letter back to c: it was not smart enough to have closed the log file and reopen it on the reassigned drive c: so that the next write to the log failed because the drive letter changed.
that would just be a bug in the repair tool.

in the end, does the machine boot ok? or do you still have a broken machine?

the reserved partition is small but it should be ok. looks like windows is currently installed on c: drivee

generally a buzzing sound happens when a gpu driver crashes because of a sound conflict.
often it will be a old motherboard sound driver conflicting with a GPU sound driver.

now that we know windows is on the c: drive, what should i do ?

Actually, i got a SSD Samsung evo and a HDD Western Digital. Yes i got no problem with that now but sometimes i hear that weird sound when listening to music but no freezing or shutting down.

I noticed in the bios that there's two samsung ssd showing up. Wasent like that before
http://

Btw, doing a factory reset would that solve it ?

Ok wont do that.
What about updating the bios ? havent been updated since 2013.

I think i will try updating the bios. Since the crash happened i noticed that some of my USB ports are not working properly, they dont recognize the USB stick. But when i try it on a different usb port it works.

 

[shuffler91]

Bump