Red Vertical lines on monitor

abbas5001

Hi guys,


I was playing Football Manager 2 nights ago and suddenly the computer crashed and i got the Blue Screen of Death before the computer restarted and iput it into Safe Mode. The computer had about 4 blocks of vertical red lines but when i restarted back into normal mode they went away. This happened again the same night while playing Football Manager.


I did a virus scan with Avast which found 10 or so 'infected' files but after looking around the net i think these were just false positives.


Again the PC has crashed earlier today while playing Football Manager but with the Blue Screen of Death this time. Again the red lines appeared as i took it into safe mode first and then went away after i put it into normal mode. I checked Problems and Solutions in Windows and it said was due to a video adapter error or something and the solution was to download the new video driver and i installed it.


However, it was has crashed again while playing Football Manager. This time it just froze and there was noBlue Screen of Death. I put it into safe mode and rebooted back into normal mode, but unlike before the red vertical lines stay. I also used system restore to take the computer back to the settings of 2 days ago but again the red lines are there.


I checked some advice online which said to go into Safe mode and uninstall the video adapter and then go back into normal mode, set the resolution and download the driver. I uninstalled the video driver in safe mode but the problem was still there when i went back into normal mode and the windows software was automatically installing the new adapater as soon as windows started anyway.


any ideas?
thanks

John_Gray

Since it seems to be entirely Football Manager related, could you uninstall and reinstall it without losing all your data?

Taffybiker

You don't mention your hardware types. Does your graphics card meet the recommended specs for the game?

Raksha

Have you tried a different monitor cable/checked the connections?

JasX

Things I'd be tempted to check

-did you make a note of what the BSOD actually said (and related do you have your machine to set to leave the blue screen up so you can read it rather than automatically/instantly reboot?)

-reinstall your graphics driver (and perhaps directX too/get the latest version)

-reinstall football manager

-do a check for corrupt operating system files (on xp the command was "sfc /scannow" from DOS prompt, you'll need your install disk or the location of your CAB file)

-reinstall your OS/restore to factory settings

doesn't sound like a monitor/cable fault

abbas5001

Hi guys,

Got an update.

Anyway, next morning the red lines are gone which is a surprise. However, was watching something on 4OD last night and again the same thing happened - got this scotch pattern of red but no BSOD. Shut down manually using power button.

Went to bed, put the PC on this morning and no red lines again. However, after using the PC for about half an hour, i tried to open a notepad file and the monitor just went into standy (blue 'on' light turned to orange and would not change). Again restarted manually by switching off from power button and the computer started up but instead of going to the windows screen i just got this complete light blue screen for ages then the BSOD again.

I changed the settings so the computer doesn't auto restart so i managed to get down the details:

***STOP: 0x00000116 (0x8A653238. 0x90EF4A50, 0x00000000, 0x00000002)

*** NVLDDMK.SYS - Address 90EF4A50 base at 90E0A000, Datestamp 4bb7df30

I'm getting a monitor from a friend tonight to try that out but more and more i'm thinking this is a video card error. Also, i got Vista to check for system file corruption and got this message:

"Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log"

I have accessed the CBS file but can't make any sense of it?

John_Gray

Stop 116 pointing at NVLDDMK.SYS seems highly indicative of an nVidia graphics card driver error. Can you download the latest version of the correct driver for the correct nVidia card model for your operating system from the nVidia website?

If not, you'll have to tell us the operating system and the exact model of the graphics card...

abbas5001

I've checked Device Manager and the nvidia card has the exclamation mark logo next to it and under device status it presents the regular message if something is wrong: Windows has stopped this device because it has reported problems. (Code 43).

The following are my specs:

OS: Windows Vista Home Premium
Graphics card : NVIDIA Geforce 8800 GT
CPU: Intel Core 2 Quad 2.4GHz
RAM: 3GB

I have the most recent version of the driver for the graphics card according to the nvidia site. Although i have the English USA version installed rather than the English UK one but this shouldn't be making any obvious difference with regards to the above problem?

JasX

this might seem a bit random but I'll mention it,

I was plagued with Nvidia driver BSODs for about 3 months a couple of years back and no end of driver updates and rebuilds seemed to fix it.... turned out in the end to be a glitching RAM stick as when I eventually got round to running memtest86 having run out of ideas on what else to test it threw up 3000 errors in 15 mins.

ripped out the bad stick, memtest then ran showing zero errors and the BSOD problem disappeared too... might also be worth a check if other steps don't work

http://en.wikipedia.org/wiki/Memtest86

http://www.memtest86.com/

JasX

abbas5001 wrote: »

I've checked Device Manager and the nvidia card has the exclamation mark logo next to it and under device status it presents the regular message if something is wrong: Windows has stopped this device because it has reported problems. (Code 43).

cross post. hmm definitely points more towards the graphics card

Richie-from-the-Boro

Look here

Read the para that starts with : Fix - Go to windows/system32/drivers and rename nvlddmkm.sys to nvlddmkm.sys.old.

It explains why you have to do it manually !