[thedeadpo3t]

Good Day to you.

At seemingly random times (although I'd imagine there's a culprit) a blue screen with vertical white lines appears before me and my laptop restarts.
Unfortunately I have no error code to post, simply because I don't receive one.

Edit: I used to receive an error message which read as follows:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 6153

Additional information about the problem:
BCCode: 50
BCP1: 851B6000
BCP2: 00000000
BCP3: 861EE0A6
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1



However I don't receive it any longer.

[Marvin trill]

Hi,
and good day to u,

this could be either a blue screen or death (although messed up) or ya screens going on ur laptop

So, a few things to try to elimiinate on or the other;
(a) any new software, hard ware, etc.. remove this
(b) run memtest86 (download)
(b)(i) run any diagnostics tools (if they came with ya laptop)
(c) use an external monitor to the laptop. When u get the blue screen, is it apperas on the monitor as normal, then ya screen is going.
(d)update ya graphics card driver, or any other driver.
(e) if u were having the errors before, then go to c:/windows/mini-dumps. Post ya mini dumps.
(f) i cant think of anything else, so hopefully someone else will have some more ideas on this,

but for now, i hope this helps,
Marv

[Rollin' Rog]

I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to %systemroot%\minidump and copy the last few minidump files to that folder.%systemroot% is normally c:\windows. They are numbered by date. You can paste that address in address bar to get there.
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder.
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.

This might point us to a non-system driver causing the error, if one exists for it.

Since almost all bugchecks can be caused by faulty ram, I would recommend you perform memory tests.

Beginners Guides: Diagnosing Bad Memory


Memtest86 - A Stand-alone Memory Diagnostic

[thedeadpo3t]

I've added the last five files of the minidump to this post.

Appreciate the help.

[Marvin trill]

hi,
ive looked at ur files ,and i *think* (im no expert at this, so 2nd opinion welcome ) that the fault is "windrvNT.sys". all ur files give this info

"Could not read faulting driver name
.....
FOLLOWUP_NAME: MachineOwner

MODULE_NAME: windrvNT

IMAGE_NAME: windrvNT.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 409f405c

FAILURE_BUCKET_ID: 0x50_windrvNT+40a6

BUCKET_ID: 0x50_windrvNT+40a6

Followup: MachineOwner"

The module name and image name indicate the faulting driver causing the blue screen.
windrvNT isnt well documented. i belive it belongs to a program called "folder lock". (http://www.file.net/process/windrvnt...drvnt.sys.html)

Have u ever used/had/got folder lock? if u have try uninstalling it, or renaming the windrvnt file, and see if this helps. If not then the file may be something else and more research will be needed.
(there is also an issue with folder lock and spybot)

you could try running (in cmd) chkdsk /r or there is this http://www.techimo.com/forum/showthread.php?t=192165 (i would rename the file first, just in case)

Hope this helps, tc,
-Marv