BSOD when I install 2nd stick of RAM

[rive0108]

ntoskrnl.exe
is a critical process in the boot-up cycle of your computer, and yours appears to be causing a common system fault

 

[crappydonkey]

ntoskrnl.exe
is a critical process in the boot-up cycle of your computer, and yours appears to be corrupt and is causing a common system fault

Can I just replace ntoskrnl.exe with a copy of the file off of the CD?

 

[rive0108]

If itll work- though I suspect you may have to repair/re-install Vista>

Here is what the fuction of the .exe is:

ntoskrnl.exe
responsible for various system services such as hardware virtualization, process and memory management, etc., thus making it a fundamental part of the system. It contains the Cache Manager, the Executive, the Kernel, the Security Reference Monitor, the Memory Manager, and the Scheduler, among other things

 

[rive0108]

What was the result of sfc/scannow?

 

[crappydonkey]

What was the result of sfc/scannow?

The scan gets to about 18% then stops and says:

Windows Resource Protection could not perform the requested operation.

 

[rive0108]

What was the result of sfc/scannow?

The scan gets to about 18% then stops and says:

Windows Resource Protection could not perform the requested operation.

Well I am not surprised. That should have been your first indication you have severe Windows file integrity/driver corruption issues.

Windows Resource Protection could not perform the requested operation
This issue may occur if a Windows Resource Protection (WRP) file is missing or is corrupted


Backup your DATA files/folders and re-install Vista

 

[crappydonkey]

What was the result of sfc/scannow?

The scan gets to about 18% then stops and says:

Windows Resource Protection could not perform the requested operation.

Well I am not surprised. That should have been your first indication you have severe Windows file integrity/corruption issues.

Windows Resource Protection could not perform the requested operation
This issue may occur if a Windows Resource Protection (WRP) file is missing or is corrupted

So your suggestion is a repair? or is full reinstall required?

 

[rive0108]

The scan gets to about 18% then stops and says:

Windows Resource Protection could not perform the requested operation.

Well I am not surprised. That should have been your first indication you have severe Windows file integrity/corruption issues.

Windows Resource Protection could not perform the requested operation
This issue may occur if a Windows Resource Protection (WRP) file is missing or is corrupted

So your suggestion is a repair? or is full reinstall required?

I suggest you backup your User data while you still can (you may lose the ability to boot up Windows in the near future), and boot into your Vista disk, DELETE all disk partitions, and reinstall into unpartitioned space.

After Installation go to Windows Update, and keep going back untill it states "no more updates available for your System"

Then run sfc/scannow again (its possible you may a corrupted installation disk)

Then I suggest you do this (full defrag/check drive for file issues and bad disk sectors):
http://www.vistax64.com/tutorials/165576-how-make-vista-more-responsive-faster.html?filter

 

[SCSIraidGURU]

Before you do that. Do error checking with one stick of RAM and not both. The problem is most likely caused by memory conflict with your motherboard or hardware. If you install the second stick and you get the problems, I would do more research on your RAM choice.

 

[avgwarhawk]

Before you do that. Do error checking with one stick of RAM and not both. The problem is most likely caused by memory conflict with your motherboard or hardware. If you install the second stick and you get the problems, I would do more research on your RAM choice.

I have suggested he look at the motherboard website for proper installation of additional memory. Perhaps their forums has the answer. I know MSI forums helped me with getting memory set up correctly. Oh well, one can only try.

 

[rive0108]

Before you do that. Do error checking with one stick of RAM and not both. The problem is most likely caused by memory conflict with your motherboard or hardware. If you install the second stick and you get the problems, I would do more research on your RAM choice.

So you think the Windows Resource Protection (WRP) file missing/corruption issue resulting in a failure of the PC to be able to scan System files is because of a bad RAM sticK?:huh:

 

[SCSIraidGURU]

The problem is memory conflict causing either a timing issue with the CPU and bus or other issues with the storage reads/writes.

 

[avgwarhawk]

The problem is memory conflict causing either a timing issue with the CPU and bus or other issues with the storage reads/writes.

My thoughts were BIOS set up on the mobo for memory. What slots are being used? I really think the mobo website should be looked at in this instance before wiping it all clean.

 

[rive0108]

The problem is memory conflict causing either a timing issue with the CPU and bus or other issues with the storage reads/writes.

so...

Just so I understand this, you are saying that it is in fact a hardware issue, and not System file/driver corruption...correct? Even though his system itself in both the BSOD dumpfile and sfc/scannow both indicate otherwise?

 

[SCSIraidGURU]

The problem could be his CPU is 1333 FSB. His RAM is DDR1066. If the motherboard is not setting the RAM to DDR667 to match his CPU, it can cause memory timing to drift and cause the storage bus not to be in sync. It can also be his RAM voltage is not matching up to the board voltage setting. This can cause huge issues. Hard to say. Best thing is get proper matching RAM that is set for his CPU timing.

 

[crappydonkey]

The problem is memory conflict causing either a timing issue with the CPU and bus or other issues with the storage reads/writes.

My thoughts were BIOS set up on the mobo for memory. What slots are being used? I really think the mobo website should be looked at in this instance before wiping it all clean.

I have my sticks in slots #1 and #3 like the manual says. I will try all configurations again with the new memory that I just got yesterday before I do a system wipe.

 

[SCSIraidGURU]

Test RAM with memtest86 one stick at a time. If all ram passes, test pairs.

 

[crappydonkey]

The problem could be his CPU is 1333 FSB. His RAM is DDR1066. If the motherboard is not setting the RAM to DDR667 to match his CPU, it can cause memory timing to drift and cause the storage bus not to be in sync. It can also be his RAM voltage is not matching up to the board voltage setting. This can cause huge issues. Hard to say. Best thing is get proper matching RAM that is set for his CPU timing.

Can you explain a little more about this please?

 

[SCSIraidGURU]

Computers work best if components are matched. The RAM I recommended above is matched to your CPU 1333 FSB bus. Your RAM is DDR2. So 1333/2 is 667. On a highend motherboard, your CPU, RAM, and voltage settings are very tight for stability.

I would recommend getting DDR667 RAM to match your e8400.

 

[SCSIraidGURU]

I learned over 27 years of building computers, it is better to match the RAM to the CPU. I rather match the RAM than have issues with RAM.

I am looking at Intel X5550 Xeons. They are DDR3 1333 FSB CPUs. I can use DDR3 1333 FSB RAM to match to the CPUs.

I have Intel E5430 Xeons. They are DDR2 1333 FSB CPUs. I can use DDR667 FSB RAM to match to the CPUs.