New
#11
Do you have another video card you can try? Perhaps borrow one from a friend or rob one off another computer.
Do you have another video card you can try? Perhaps borrow one from a friend or rob one off another computer.
However no... all friends on laptops now :)
I then suggest taking the machine into the local PC shop and having them test or replace the video card.
are you sure this is because of that test with lots of errors on GPU memory?
That's my best guess.
You can try updating your card drivers, but if it doesn't work, carry on with the video card change.
Drivers - Download NVIDIA Drivers
ok I have tried one more video card test from this link Download Video Card Stability Test
And after starting the test the monitor started to go black for couple of times and then windows gave me this message: Display driver nvidia windows kernel mode driver, version 197.45 stopped responding and has succesfully recovered.
I think this might be it. Cause in all my bsods there is a problem with kernel mode( dont really know what it does :) )
That means the driver is a Kernel-mode driver and not User-mode. I can't pretend to know the subject well, but I can say that GFX drivers run in Kernel mode, and most other third-party drivers are user-mode.
Still, if the driver update doesn't work, it's time to investigate a hardware video error.
Ok, I am updating it now, and will wait for a day or so to recieve or in better way not receive a bsod :) thanks
Hi, me again... however after 10 days of satisfaction I got a bsod today, playing mafia 2 I played it yesterday and a day before but it was ok. During this period of time I also stressed CPU, GPU and RAM a lot, but everything was working smoothly until today I have already thought that I solved the problem. I am attaching the dump, can anyone look at it please?
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.
This is looking more and more like a bad video card.. Take JKs' advice and consider replacing the card, or take your machine to a shop for repair..
You still have the same outdated drivers from the last .dmp files.. These MUST be updated ...Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {eb46060, 2, 1, 830951e7} Probably caused by : ntkrnlmp.exe ( nt!KiSearchForNewThread+2ed ) Followup: MachineOwner ---------
Code:89eb9000 89eb9680 giveio giveio.sys Wed Apr 03 22:33:25 1996 (316334F5) 8b612000 8b61c000 hcmon hcmon.sys Tue Oct 28 21:27:34 2008 (4907BC06) 8b623000 8b62ec80 vmci vmci.sys Tue Oct 28 20:56:34 2008 (4907B4C2) 91ff8000 91ffc080 VMkbd VMkbd.sys Tue Oct 28 22:36:29 2008 (4907CC2D) 9388d000 9388ff00 VMNET VMNET.SYS Thu May 22 06:33:05 2008 (48354BE1) 9388a000 9388c680 vmnetadapter vmnetadapter.sys Thu May 22 06:33:07 2008 (48354BE3) 8b49f000 8b4a5000 vmnetbridge vmnetbridge.sys Thu May 22 06:33:38 2008 (48354C02) 8b7d0000 8b7d4c80 vmnetuserif vmnetuserif.sys Tue Oct 28 21:40:06 2008 (4907BEF6) 8b62f000 8b631000 VMparport VMparport.sys Tue Oct 28 20:55:46 2008 (4907B492) 8b631000 8b700b00 vmx86 vmx86.sys Tue Oct 28 23:03:30 2008 (4907D282) 8b7d5000 8b7d8d80 vstor2_ws60 vstor2-ws60.sys Thu Oct 02 21:04:30 2008 (48E56F9E)