Random BSOD's that happened today

lovewin7yea · 12 Dec 2010

Well first off i didnt install anything new cept a game and a new copy of Nero 10 i just purchased. Not sure whats going on, but if someone can read these and tell me whats happened that be great

Specs
Windows 7 Ultimate 64 bit
AMD Athlon II x2 260
MSI 870-G45
4GB DDR3 1033
200GB Seagate Barracuda 7200

First off, my hard drive is not the newest, so im thinking that could be a problem, im going to upgrade to a cavier black 2TB so, if thats whats causing it, ill update ASAP

i havent gotten a BSOD in a couple months so im not sure why it just started outta the "blue" no pun intended.

thanks in advance for any help

edit: Also noticed my Nvidia Geforce GT240 has been lagging up on games lately, so im also wondering if that could be it, my drivers are updated all around my system.

yowanvista · 12 Dec 2010

The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to run driver verifier to pinpoint the faulting driver...

- 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.

CarlTR6 · 12 Dec 2010

In additions to Yowan's excellent advice, update or rename these two drivers. Out of date drivers can and do cause BSOD's. The one in bold font is really obsolete.

L1C62x64.sys Wed Apr 01 01:09:17 2009 - Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20). OEM - none at http://www.atheros.com/pt/index.html. Update this driver from you computer manufacturer's website.

pcouffin.sys Tue Dec 05 09:39:30 2006 - low level access layer for CD devices (A part of many different CD/DVD burning programs) VSO Download DVD Burning Software, convert AVI to DVD, video converter, DVD copy to DVD slideshow photo
or
rename to pcouffin.BAK and see what CD/DVD program it breaks.

lovewin7yea · 12 Dec 2010

thanks guys, im going to BSOD my comp now, its a brand new board and ive updated all of my drivers through MSI and the pcouffin is convertxtoDVD and they dont have an updated driver as i use it to create my family DVDs

lovewin7yea · 12 Dec 2010

yea not sure why i did that cause now my computer BSOD in a loop now and i cant even get into my damn windows. how the hell i turn it off now? i have to go into safe mode to talk to you guys.

lovewin7yea · 12 Dec 2010

yes this advice was so excellent it has now fully rendered my windows inoperable cause it was working just fine until i did this little idea.

yowanvista · 12 Dec 2010

lovewin7yea said:

yes this advice was so excellent it has now fully rendered my windows inoperable cause it was working just fine until i did this little idea.

Driver verifier is meant to cause more BSODs which will directly point to the faulting driver(s), boot into safe mode with networking and upload the new dumps

lovewin7yea · 12 Dec 2010

alright. gimme a second

yowanvista · 12 Dec 2010

lovewin7yea said:

thanks man, i went from one little blue screen to a blue screen loop now every time i get logged into windows. please tell me how to reverse this cause this was no help at all. its only made it worse.

See the above suggestion and upload the dumps :)

lovewin7yea · 12 Dec 2010

ok here it is

there are 5 dmps in there