Lotsa BSOD's (ntoskrnl.exe)

[Gyrating Gorilla]

edit: deleted

 

[zigzag3143]

Hey all,
I have been getting... quite a few BSOD's (a bit of an understatement..) and I have not been able to solve it.
In total I have 29 .dmps.
Some of the BSOD's I've been having have happened while I was playing games, so I thought it was something wrong with my GPU, so I did a driver sweep of the display drivers, rebooted, installed latest drivers, rebooted, and then BSOD'd later that day (though not while playing games!). Previously before that I did a video card display stress test (Furmark) and the temperature flatlined after a few minutes at 80-83°C but I didn't BSOD at all during that. Also, sometimes after a BSOD when I try turn on the computer BIOS does not beep and nothing is displayed on the screen and I have to turn it off and turn it on again to try get it to work. I don't have any spare components to swap out to test what is wrong.
I'll attach the 5 latest .dmps
I've looked at them using NirSoft's BlueScreenView and most of them point to ntoskrnl.exe(+7cc10 or 7cc40)

Two most recent were Related to nlndis.sys NetLimiter 3 NDIS driver from Locktime Software. I would remove it at least to test. Yours is 2 years old

 

[zigzag3143]

Hi, thanks for responding!
Okay, I've removed it I also removed some cisco VPN driver since I wasn't using it and I had a bluescreen that named that on the BSOD screen.
I'm still getting lots of bluescreens though.
Attached are the last 5.

I was using BlueScreenView's google search function which searches the driver and the error code and I came across a person with a lot of similar error codes in his BSOD's
http://answers.microsoft.com/en-us/...ws-7-x64/6d0f1da3-00f1-43b1-a8d4-adfda784602e
He states his solution was "I found that the XMS 3 memory which normaly runs at 1.5v actually needs to be set to 1.6v for this Intel Mainboard."
I know I've got an AMD motherboard but could this be a solution to my problems?
Cheers.

The most recent dmps point to memory corruption so it may be a memory voltage issue. You should however, test the memory and drivers before adjust the voltage.

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org/#downiso

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

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

 

[bassfisher6522]

The first thing to do is run MemTest86+ to confirm a bad memory module is at fault. As in my case my memory was good, it turned out to be my GPU memory. Luckily I had some backup parts. I replaced my GPU and BSOD's stopped. Something to look at.

 

[zigzag3143]

Okie dokie. I ran memtest. Results:
Slot 1 Card 1: Fail (almost immediately)
Slot 2 Card 1: Pass
Slot 1 Card 2: Fail (almost immediately)
Slot 2 Card 2: Pass



So I guess I need to replace the whole motherboard?

Looks like slot one is bad. Is the computer under warranty?