Windows 7 Forums


Reply
Thread Tools

Lotsa BSOD's (ntoskrnl.exe)

 
 
Gyrating Gorilla Gyrating Gorilla is offline
New Member
Join Date: Oct 2011
Posts: 4
Thanked: 0
 
      10-21-2011
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)
Attached Files
File Type: zip 5 latest dmps.zip (120.4 KB, 15 views)
 
Reply With Quote
 
 
 
 
zigzag3143 zigzag3143 is offline
Wanikiya
zigzag3143's Avatar
Join Date: Sep 2010
Location: NY USA
Posts: 248
Thanked: 77
Send a message via MSN to zigzag3143 Send a message via Yahoo to zigzag3143
 
      10-25-2011
Quote:
Originally Posted by Gyrating Gorilla View Post
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
 
Reply With Quote
 
Gyrating Gorilla Gyrating Gorilla is offline
New Member
Join Date: Oct 2011
Posts: 4
Thanked: 0
 
      10-28-2011
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/w...4-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.
Attached Files
File Type: zip Last 5.zip (114.4 KB, 6 views)
 
Reply With Quote
 
zigzag3143 zigzag3143 is offline
Wanikiya
zigzag3143's Avatar
Join Date: Sep 2010
Location: NY USA
Posts: 248
Thanked: 77
Send a message via MSN to zigzag3143 Send a message via Yahoo to zigzag3143
 
      10-29-2011
Quote:
Originally Posted by Gyrating Gorilla View Post
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/w...4-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


Quote:
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...e-disable.html
 
Reply With Quote
 
bassfisher6522 bassfisher6522 is offline
Established Member
bassfisher6522's Avatar
Join Date: Feb 2010
Location: NC
Posts: 559
Thanked: 87
Send a message via MSN to bassfisher6522 Send a message via Yahoo to bassfisher6522 Send a message via Skype™ to bassfisher6522
 
      10-29-2011
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.
 
Reply With Quote
 
Gyrating Gorilla Gyrating Gorilla is offline
New Member
Join Date: Oct 2011
Posts: 4
Thanked: 0
 
      10-29-2011
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?
 
Reply With Quote
 
zigzag3143 zigzag3143 is offline
Wanikiya
zigzag3143's Avatar
Join Date: Sep 2010
Location: NY USA
Posts: 248
Thanked: 77
Send a message via MSN to zigzag3143 Send a message via Yahoo to zigzag3143
 
      11-01-2011
Quote:
Originally Posted by Gyrating Gorilla View Post
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?
 
Reply With Quote
 
Gyrating Gorilla Gyrating Gorilla is offline
New Member
Join Date: Oct 2011
Posts: 4
Thanked: 0
 
      11-01-2011
Quote:
Originally Posted by zigzag3143 View Post
Looks like slot one is bad. Is the computer under warranty?
Yes I believe so. I think it's still under warrenty for 2 more months.

I've been running my computer only on one stick (2GB) and it had been running fine without any blue screens but I got one earlier today and I'm now concerned. I've attached it to this post.
Thanks for the help you've provided so far!
Attached Files
File Type: zip Last BSOD.zip (22.0 KB, 9 views)
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
BSODs, driver crashes, game crashes and whatnot syrco Crashes, BSODs and Debugging 8 07-27-2011 07:12 PM
New Computer Build Multiple BSODs bboyoxygen Crashes, BSODs and Debugging 0 05-25-2011 03:42 AM
Many Different BSODs Mooster Crashes, BSODs and Debugging 1 05-09-2011 08:29 AM
Win 7 Pro x64 SYSTEM_SERVICE_EXCEPTION (ntoskrnl.exe) vitaljok Crashes, BSODs and Debugging 2 04-17-2011 05:18 PM
BSODs nukin Windows 7 Support 1 01-07-2010 12:19 PM


All times are GMT +1. The time now is 11:53 AM.
W7Forums is an independent website and is not affiliated with Microsoft Corporation.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33