BSOD on vista home premium!

Status
Not open for further replies.

e_p_a_k

Posts: 26   +0
i don't know when this started exactly, but lately whenever i restart my laptop for whatever reason, it would boot up, go into the logon screen, then when i logon, it would crash into a BSOD, restart, and then run perfectly fine the second time. event log reads:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-07-09T02:03:19.000Z" />
<EventRecordID>52376</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Ejohn</Computer>
<Security />
</System>
- <EventData>
<Data Name="param1">0x00000050 (0x8309d000, 0x00000000, 0x862710a6, 0x00000000)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
</EventData>
</Event>

i'm a complete noob at this. anybody know what might be wrong??
 
Please attach your minidumps so we can take a closer look at what is going on.

How to find minidumps in XP with ">" meaning to click on; I don't know if it has changed in Vista:

My Computer > C Drive > Windows Folder > Search for Minidump Folder > the files inside this folder are what we need (not the folder itself). Attach these files to your next reply like you would a Word document to an email.
 
here's the stuff i got from the minidump folder, as well as the additional info that vista said would "help describe the problem". i archived all the files and put them up on rapidshare. any help would be very much appreciated.

LINK TO RAPIDSHARE: http://rapidshare.com/files/42082425/BSOD_info.zip.html

much obliged!=)

files included in zip:
BSOD.txt
Nimi071007-01.dmp
WER-11618909.sysdata.xml
WERC216.tmp.version.txt
 
This is a known problem with Folder Lock. The best solution is to uninstall Folder Lock.

BugCheck 50, {83095000, 0, 862710a6, 0}
Probably caused by : windrvNT.sys ( windrvNT+40a6 ) <-- Folder Lock file.
8626d000 86273440 windrvNT windrvNT.sys Mon May 10 16:42:04 2004 (409F405C)
 
argh. that sucks. haha! i happen to like folder lock. no known bug fixes? no new updates to the program that address this?
 
new software (the company that made folder lock) support told me to try installing folder lock on a different directory instead of just the usual C:/program files/folder lock. do you think this'll actually help?
 
Status
Not open for further replies.
Back