Solved BSOD shortly after powering on

[Jordyi]

Hi there.

My brother's computer has been BSODing for weeks now with no real improvement. I'm fairly certain it's hardware related, but can't tell for sure. Going to do trial and error stuff like replacing pieces but need your help. I've tried running the diagnostic tool to create the dump files but the application just won't start and crashes upon running it.

I forget the way of collecting this information the other way, or perhaps could somebody help me with the program issue? I'm getting the EventType: clr20r3 error message upon startup which after google searches just relates to developers and not user fixes.

 

[Dsprague]

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[x BlueRobot]

Could you please check this directory?

C:\Windows\Minidump

You may substitute the C:\ for the partition in which you installed Windows on.

Or, just use this:

%systemroot%\Minidump

 

[Jordyi]

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Not much help considering said program won't run.

Could you please check this directory?

C:\Windows\Minidump

You may substitute the C:\ for the partition in which you installed Windows on.

Or, just use this:

%systemroot%\Minidump

Alright. I'll check that folder.

Just got a BSOD related to ntfs.sys. I'm right in thinking this may be caused by the hard-drive?

 

[x BlueRobot]

ntfs.sys is related to the driver used by hard-drives formatted with NTFS file systems, however, does not mean necessarily that the hard-drive is at fault.

 

[Jordyi]

It's currently doing a windows file system consistency check on startup so I'm just letting it do it's thing. If there's a dump file in there, should I zip it up and post it? Or try and get this program to work?

 

[x BlueRobot]

Zip up all the dump files (if any) and then post the files in your next post. You will also need to add your MSINFO32 file to the folder also, by following these steps:

1. Start rb:
2. Type: msinfo32
3. File, Save
4. Copy file into the zipped folder

 

[Jordyi]

Here's a folder containing all the dumps along with the Msinfo32 information inside.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 4E[/COLOR], {[COLOR="Blue"]7[/COLOR], d4d32, 4000000000, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+347c5 )

Usual causes:  Device driver, memory

This bugcheck indicates that the Page Frame Number list has become corrupted for some reason. Every page has a PFN, which contains important information. More specifically, a driver has unlocked a page file more times than it was locked. Pages are locked into physical memory are guaranteed not to be written to a page file until the process is stopped.

More Information - VirtualLock function (Windows)

No Service Pack 1?

Windows 7 Kernel Version [COLOR="Red"]7600 MP (4 procs) Free x64[/COLOR]

• Learn how to install Windows 7 Service Pack 1 (SP1)

Service Pack 1 has provided many security and stability updates for Windows 7, which would be highly beneficial for your system.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[Jordyi]

Thank you so much for looking into the dump files so quickly and for the helpful links. I recently reinstalled Windows on his machine hence no SP1, installed that now. Driver issues may also not be the problem due to recently installing windows again (not sure if I'm right about this). In light of the problem possibly being RAM related, I've installed a stick of 4GB RAM from my own computer on the computer and as of yet, the computer has not BSODed, but it's still early days. I'll run Memtest overnight and get back to you with the results. Thanks again, I appreciate it.

 

[x BlueRobot]

Welcome, it seems to more of a RAM issue at the moment.

 

[Jordyi]

Look as though the RAM was the issue. Running Memtest for just half of the first pass it has already encountered 51,000 errors. Will put some new RAM in tomorrow and get back in a while with how it's getting on.

 

[x BlueRobot]

Okay thanks for the update.

 

[Jordyi]

I've installed new RAM, re-installed a fresh copy of windows and it's not crashed since. Seems that was the problem so I'm going to class this as solved. Thanks again for your help.

 

[x BlueRobot]

Welcome, glad I could be of assistance