Solved BSOD instantly on entering windows

[Arc]

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Uninstall MBAM and install a fresh downloaded copy, must be the free version.

We are seeing his issues are Ntfs, but it might be the disc controller too. I searched ...

lmvm nvstor
start    end        module name
88b57000 88b7c000   nvstor     (deferred)             
    Image path: \SystemRoot\system32\drivers\nvstor.sys
  [COLOR=Red]  Image name: nvstor.sys
    Timestamp:        Sat Mar 20 02:21:52 2010 (4BA3E3E8)[/COLOR]
    CheckSum:         0002B646
    ImageSize:        00025000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So it might be an idea ....
A search revealed that you are using nForce as the chipset driver, and that includes nvstor.sys as the storage controller driver. You need to try to update nForce, as it contains not only the storage controller, but also network controller and a lot of other vital drivers.

Go to Drivers - Download NVIDIA Drivers, search for nForce, as per your motherboard's chipset specifications.

 

[Wowdude]

Thanks Arc!

After a quick search, the nVidia drivers dropdown list doesn't have the nForce series 430 that is required for the M2N-MX motherboard, but after a quick search on their site I found them. I will try updating the chipset drivers and also uninstalling and re-installing malwarebytes and get back to you.

Thanks,

Wowdude

 

[Wowdude]

I have just noticed however that the chipset drivers are from 2007. Shouldn't the computer (as it was running fine for a good 5 months with internet connection) have updated these from the original ones used off the accompanied install disc for the mobo?

 

[Wowdude]

After shutting off MBAM in the startup menu, rebooting and reintalling, and installing the nForce driver pack (from the nVidia website), I rebooted the computer and let it attempt to load into the desktop. The computer blue screened almost instantly after reaching the desktop. Hmmm....

 

[Arc]

Wowdude, it is really difficult to get the drivers for M2N MX motherboards, as those are somehow outdated I had one MX SE+ earlier. It is somehow apparent that the old chipset drivers, those dates back to 2007 may not support windows7 very properly coz windows 7 came into existence in 2009.

Anyway, can you upload the latest crash dump? Koolkat77 is busy atm, and so I am posting here, and it will be overview by koolkat77 later again, dont worry.

 

[Wowdude]

Sure thing Arc. And I managed to get a 2009 windows vista/7 driver from nVidia but it hasn't solved the problem. I don't know whether it may be the driver or not. The file you asked for is attached. Sorry it's still got the old crash dumps in too.

Thanks

Wowdude

 

[Wowdude]

Hmm, it seems I was a bit too quick with the zipping of the file. Here's the completed file.

Wowdude

 

[Arc]

In my best assumption, the root of the problem is the motherboard, the BIOS.

BIOS Version/Date    American Megatrends Inc. 0404, [B][COLOR=Red]24/11/2006[/COLOR][/B]

It is very outdated. And, unfortunately windows 7 is not listed there in the list of supported OS :
ASUS - Motherboards- ASUS M2N-MX

But, even strange information are available here

Machine ID Information [From Smbios 2.4, DMIVersion 0, Size=2169]
BiosMajorRelease = 8
BiosMinorRelease = 12
BiosVendor = American Megatrends Inc.
BiosVersion = 0404   
[COLOR=Red][B]BiosReleaseDate = 11/24/2006[/B][/COLOR]
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
[B][COLOR=Red]SystemFamily = To Be Filled By O.E.M.[/COLOR][/B]
SystemVersion = System Version
[COLOR=Red][B]SystemSKU = To Be Filled By O.E.M.[/B][/COLOR]
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = M2N-MX
BaseBoardVersion = Rev 1.xx

I am guessing you are using genuine windows, seeing you have MSE installed. But, how can you get an OEM license for a motherboard that is 3 years old than the operating system? And if you buy the OEM license for it, why? Those are some wrong steps IMO.

 

[Wowdude]

Hey Arc,

I think I know why the OEM looks so strange. The original OEM liscence, registered to the motherboard, is Windows Vista. I upgraded my operating system about 4 years ago using a student bought version of Windows 7 downloaded through digital river and used to upgrade vista to windows 7. When I donated the computer to my in-laws, I reinstalled vista and then loaded 7 over the top. But the computer was running fine for 4-5 months before it blue screened once.

Very curious. But at least you have a bit of background now =)

 

[Arc]

So now it provides a base, for sure. But you may need to find any possible update of the bios,from the Asus website I have linked in my earlier post.

Also,

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

► Stress test the CPU.
Hardware - Stress Test With Prime95

 

[Wowdude]

Ah. Well I assumed that because the mobo can run vista, it could run windows 7, as they can sometimes share the same drivers. I've already run memtest86+ overnight to 8 passes without problems. The latest BIOS update I can find for vista OS is 2008. I will attempt the other 2 stress tests now.

Thanks Arc,

Wowdude

 

[Wowdude]

Heya Arc,

I've already ran the memtest86+ for 8 passes a few days ago. The GPU stress test doesn't load properly in safe mode and the CPU worked perfectly for 2 hours under stress.

After spending 4 hours trying to update the BIOS i've given up. I don't have a floppy drive to boot from, when I burn the files to a DVD the EZ-Flash utility claims the .ROM file is not on there (even though it's named exactly the same as what it's asking for) and it can't find AFUDOS on my flash drive. Also the ASUS BIOS update utility that comes with the drivers disk only installs when it's connected to the internet and no tin safe mode.

This is serously beginning to annoy me now...

Wowdude

 

[Vir Gnarus]

All the crashdumps have something to do with registry key activity, with the occasional NTFS error. Either something is fouling up - or has fouled up - the registry, or there's some sort of storage problem like a corrupt file system, bad hard drive, or just a storage controller problem with your old motherboard.

I've ran into this thread late so bear with me. If you haven't already, do a CHKDSK /R (fix probs automatically & check bad sectors). Follow that up with running Seatools, all checks except long & advanced.

Sometimes malware like rootkits will operate through registry activity. I recommend running a scan using both the free internet security scan offered by Kaspersky as well as their TDSSKiller. Make sure to only scan; do not permit them to fix/clean/remove infections. If they find anything, report to us in our Security Forum.

One question I'd like to ask: have these symptoms been occurring on only one installation of Windows?

 

[Wowdude]

Ok, thanks Vir Gnarus. Running the disk check /repair utility now, then will have a go with Seatools and using the Kaspersky software. In answer to your question, when I was using the computer, before I formatted and reinstalled the OS, it worked perfectly and never had a problem like this (apart from a HDD failure). After reinstalling the OS (Vista OEM) and upgrading ti Windows 7 i installed all the software they required and the computer worked perfectly for about 5 months. Upon booting the computer one afternoon, it loaded to the desktop and blue-screened, when it had been working that morning. Now that I think I do remember the (now) owner saying that they had some phoney email to their new email address with a link that they clicked. Spyware/malware could have downloaded then I suppose and ruined the registry for the next boot.

Wowdude

 

[Wowdude]

Heya Vir Gnarus,

Unfortunately, as I can only boot into safe mode, without an internet connection, the security internet scan didn't even load. The chkdsk /r didn't come across any errors. The TDSS killer found some suspicous items. I couldn't run the in-windows seatools but I had a Seatools DOS on a CD from something I was using last year. Below are screeshots from the TDSS killer and the Seatools for DOS (sorry about the picture quality, it's form my phone).

 

[Vir Gnarus]

The suspicious items are because they are drivers that aren't signed to prevent forgery. Either they're illegitimate copies of legitimate drivers or they just were never signed to begin with, which is bad business practice. Most of them look like HP printer drivers, with the PML driver also being HP and printer-related, so I wouldn't hold it against them to do something slipshod like that by releasing unsigned drivers. The BS_DEF driver showed up in Google as being related to the ASUS BIOS flash utility driver used to flash BIOS updates. I've seen this bugger cause problems before, but I'm not sure if you just installed this utility to update your BIOS to fix the instability problem or if it's been sitting there this whole time creating them. I'd advise removing it, but I don't think you can do so from safe mode.

As for Seatools, it looks like only the Short DST scan was completed. If there's any other available tests (besides Advanced), please run through those as well.

If you can't seem to get into normal Windows, try Diagnostic Startup. Type msconfig in Start Menu then select Diagnostic Startup and then restart system. If things seem to stabilize now, you can use this opportunity to clean up programs, drivers, and start up that security scan to find potential issues.

 

[Wowdude]

I did try installing the ASUS update to flash the BIOS, but it wouldn't install properly in safe mode. I have tried the diagnostic startup approach and the computer still BSOD's soon after arriving to the desktop. I will try a the longer (short, long and accoustic) test on the SeaTools disk I have.

Thanks

Wowdude

 

[Vir Gnarus]

Hmm, can you provide your most recent crashdumps?

 

[Wowdude]

Sure thing. Crash dumps are attached. After conducting the long test from Seatools, the HDD passed the short and long test with no errors. Do you think a new user account on the OS may help? Or maybe partition the HDD and install the OS on the other half?

Wowdude

 

[Vir Gnarus]

Forgot to attach the dump files. It happens.