Sign in with
Sign up | Sign in
Your question

Windows BSOD after microsoft employee clears registry (update: hardware tested and working. 3 months still no fix)

Last response: in Windows 7
Share
August 30, 2013 6:49:26 AM

Here's a long story short:

Before I encountered the issue with office my computer was past, hadNO problems, was clean as a whistle and i was editing 1+ hours of footage and cutting it down to 15 minutes in corel video studio pro X5 at 780p with no problem.

Then I had trouble installing MS office 2013 and called microsoft to help. A female rep helped me and during the process said that she'd have to clear my registry to fix the issue. she cleared it manually and office 2013 installed. In the following weeks, i was busy at work and didn't go on the computer. About 2 weeks after she cleared my registry, I started using the computer again and I started playing some games. After a few BSOD mid game, i let the computer cool off before doing anything else -since it was warm both outside and in my room.

In the days following I would get a BSOD doing anything, from letting the computer to idle to screwing around on MS paint, to plugging my flip phone into the computer to add files to it to rendering videos.

Got on the phone with microsoft and explained the issue. The tech i first spoke to told me that since it was on microsofts part that the issue occured, it would be fixed at their expense. The case was escalated to their 2 after the check disks and scans proved to be normal.

Teir two looked through the logs and said it was a kernel issue and deemed that it was a software issue and that there was a very low chance that it was a hardware issue. Just to be safe, I took my computer to a repair shop and asked them to check over my hard ware to make sure it was ok. the repair shop said that the parts were all in good order and handed me back my computer.

Teir two suggested doing some repair install with a Windows 7 service pack 1 .iso he sent me. After doing so, the blue screens of death continued and he gave me a few days to back up my files, telling me that he wanted to do a clean install of windows and to e-mail him when I was ready. I did so and never received a reply untill yesterday after another rep helped me.

The rep that helped me yesterday said that a custom install would suffice, rather than doing a clean install. after he reinstalled windows, he told me to reinstall and update all the drivers including the one that originally came with my motherboard and told me that he'd call the next day (today after I get home from work).

However after installing them and trying to render a video -the fastest way to test for BSOD- I got another BSOD here's the logs for today's:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 30/08/2013 12:42:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-15256-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5788)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800DD7BE68, 0xFFFFF8800DD7B6D0, 0xFFFFF80002EC56F2)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 30/08/2013 12:42:44 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5788)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800DD7BE68, 0xFFFFF8800DD7B6D0, 0xFFFFF80002EC56F2)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


the only drivers installed are the latest drivers pertaining to my motherboard (lan, sound etc), my graphics cards drivers, and drivers for my mouse, keyboard and monitor.

Can anyone help me here or at least tell me how to do a proper clean install?

Edit: clean install did not work. all drivers are up to date. computer has no viruses. All hardware tested by two different computer technicians and was told that the hardware works perfectly with no issues.
August 30, 2013 7:30:01 AM

imho registry clean cause more problems than it fixes. to do a clean install start with the dvd and nuke the partition, that is, choose to do a manual partitioning, delete the main partition on the C: drive and recreate it. that will force a format and recreation of the filesystem, otherwise any installation will take place over the existing one. the good thing is that since MS created the problem and they're acknowledging it, they'll be happy to guide you through the process.

some advice to avoid any future problems: get hold of a disk imaging software like acronis true image or norton ghost etc. install the os and all your drivers and applications, tweak everything to suit you and once you have everything the way you like it, create a full disk image. once you have a good starting point, at any time in the future where a problem rises you can simply back up only your data then revert to your clean and fully configured system before restoring just your data and hey presto there's your fully configured, fully working system inside of 30 minutes.

acronis true image is my favorite, aside from the classical booting from dvd to restore, it also offers the option of inserting itself into the boot process, so you have the option to revert to a previous state quickly and easily if the system fails to boot. do check it out.

just in case you're wondering, this class of software would restore a fully working installation even in the case of filesystem damage like you're experiencing now, since it would restore the full, physical state of the disk that you imaged (albeit only the used blocks). please consider carefully doing registry cleanups in the future, even the software that is considered the safest has the potential to hose a working system, and more often than not trades one set of problems for another. just use the method above of full system imaging to return to a fully working state instead, it's very quick and completely safe.
m
0
l
September 4, 2013 7:30:56 AM

Well it appears that the clean install was ineffective. As I said the computer was fine before the registry was cleaned and coincidentally i only got BSOD after she cleaned the registry. I checked the hardware and made sure it was all connected and seated correctly and it was. I'll be bringing it to a repair shop this afternoon. it was at 13% completed and has gotten much further in the rendering this time however :/ 
m
0
l
a b $ Windows 7
September 4, 2013 7:55:04 AM

IF you did a clean install and are still having problems then it is starting to sound like a hardware problem -- what are the system specs and what type of PSU is installed (have you recently installed any upgrades that would cause the system to use more power ?) -- sounds like it could be the PSU is starting to degrade and is not keeping a good steady supply of power to run things.
m
0
l
September 4, 2013 10:23:47 AM

JDFan said:
IF you did a clean install and are still having problems then it is starting to sound like a hardware problem -- what are the system specs and what type of PSU is installed (have you recently installed any upgrades that would cause the system to use more power ?) -- sounds like it could be the PSU is starting to degrade and is not keeping a good steady supply of power to run things.


CPU: AMD FX 8350
O/S: windows 7 ultimate 64 bit
SDD: M4 512 GB (main drive)
HDD: WD 3 TB (storage for files/games)
PSU: OCZ ZX Series 850W Fully-Modular 80PLUS Gold High
GPU: Geforce GTX 670 2 way SLI
MOBO: ASRock 990 FX Extreme 4
RAM: G.SKILL Ares Series 32 GB

Only things installed on my SSD are recent Windows updates and drivers, Office 2013, Corel Video Studio Pro X5, Steam and AVG.

My HDD has all my steam games installed.

Computer scan by both AVG and MBAM said that the computer was clean.

Currently my rig is in a local repair shop and I should get it back tomorrow or Friday at the latest.

I did notice however that during a Repair install done last week, that before Service pack 1 is installed, the BSOD said that the error is occurring in the NTFS files. After service pack 1 was installed yesterday -after the clean install- the BSOD indicate that the BSOD is being caused by the kernel.

I'd also want to let you know that I had windows check for errors and memory errors and both came back negative.
m
0
l
September 15, 2013 9:23:58 AM

UPDATE:
After bringing my computer to two different computer technicians, they said that ALL the hard ware is in GOOD WORKING ORDER and the issue is NOT a hardware issue.

Anyone have ANY suggestions on how to fix these BSOD? This has been going on for almost 3 months now. Microsoft closed this case in error and had to re-open it a month ago. One of their techs called me last week and after finding that i was waiting to hear back on the results of hardware tests, told me to e-mail him back. Apparently my case was brought to the attention of the supervisor and I was told that he'd call but that was over 2 weeks ago.

Since Microsoft caused the problem in the first place and now doesn't seem to care -or want to fix it- can any one suggest any ideas? doing a clean install won't work as we've already tried that. Hardware was tested and shows no abnormalities and is in perfect working order. Is there ANYTHING else I can try or am I left to cry with a machine that i built myself that has been screwed up by Microsoft, to the point that it's hard to play games and impossible to edit footage for let's plays on?
m
0
l
a b $ Windows 7
September 16, 2013 7:37:18 AM

Ok, NTFS_FILE_SYSTEM gets thrown whenever the ntfs.sys driver crashes. So something is causing the HDD driver to fail.

Obvious things to try:
Run memtest86+ to validate RAM (most likely cause)
Run a chkdsk to check the HDD (just in case)
Run SFC /SCANNOW in a command prompt (w/ admin privileges) and see if any files are corrupt

If those pass, then its likely software. In which case, I'd recommend using a tool with a registry cleaner (I recommend CCleaner) to see if that can fix the problem. Barring that, you may have to do a clean install.
m
0
l
September 16, 2013 9:36:17 AM

gamerk316 said:
Ok, NTFS_FILE_SYSTEM gets thrown whenever the ntfs.sys driver crashes. So something is causing the HDD driver to fail.

Obvious things to try:
Run memtest86+ to validate RAM (most likely cause)
Run a chkdsk to check the HDD (just in case)
Run SFC /SCANNOW in a command prompt (w/ admin privileges) and see if any files are corrupt

If those pass, then its likely software. In which case, I'd recommend using a tool with a registry cleaner (I recommend CCleaner) to see if that can fix the problem. Barring that, you may have to do a clean install.


Uhh.... microsoft cleaned my registry which actually caused the problem. nearly 3 months ago

I ran the tests you suggested and they all passed. Also, i've already done a clean install and i'm still having issues.

as stated i have 2 hard drives. the HDD is simply for storage. the OS is on my SSD
m
0
l
!