Random reboot

HornetMaX · 29 Jun 2011

Hi all,
back home after 3 months, started the PC, everything fine.
Updated my video drivers (OK) and made all the pending windows updates and .. troubles.

First, the PC started to reboot in the middle of the updates. Selcting only 1-2 updates at a time i managed to complete all of them.

However, now the PC reboots randomly.
It doesn't seem power/temperature related (it doesn't happen while gaming, it seems to happen when idle or with light apps like web browsing). I checked thew ram (memtest86+) and it seems OK.

Notice that almost all the times, it just reboots, no BSOD.

I've attached the screenshot of the event viewer, with the events relative to a single unexpected reboot highlighted in blue.

Any help appreciated !!

Thanks,

MaX.

MvdB · 29 Jun 2011

Hello HornetMax, welcome!
Could you please post full details as explained in this tutorial:
https://www.sevenforums.com/crashes-d...tructions.html

HornetMaX · 29 Jun 2011

Hi, here are the details.

Thx.

MvdB · 29 Jun 2011

Your dump file points to a driver: LV302V64.sys

It should only be found in the directory:
\SystemRoot\system32\DRIVERS\LV302V64.SYS

If you find it elsewhere (also) then there is a chance that it's a malware infection. In that case do a complete system scan with your (up to date...) Antivirus and use a anti malware tool. Plenty of info on that in this forum.

If only found in the correct (above) directory, try renaming it to LV302V64.SYS.OLD

and reboot.

HornetMaX · 29 Jun 2011

Thanks for the help. The file is located only at:

- C:\Windows\System32\drivers
- C:\Windows\System32\DriverStore\FileRepository\lpepi64v.inf_amd64_neutral_f339c42a4d192519

I did a full scan with Avira antivirus and Malwarebytes Anti Malware (both updated) first thing after coming home, nothing found.

Should I rename both files in .old ?

MaX.

MvdB · 29 Jun 2011

HornetMaX said:

Thanks for the help. The file is located only at:

- C:\Windows\System32\drivers
- C:\Windows\System32\DriverStore\FileRepository\lpepi64v.inf_amd64_neutral_f339c42a4d192519

I did a full scan with Avira antivirus and Malwarebytes Anti Malware (both updated) first thing after coming home, nothing found.

Should I rename both files in .old ?

MaX.

yes.

HornetMaX · 29 Jun 2011

Freaky.

I can rename the one in the C:\Windows\System32\drivers directory, but not the one in the C:\Windows\System32\DriverStore\... directory.
I'm prompted for admin rights (i have) but when I click I get a pop-up with the message:

You need permission to perform this action.

You require permission from SYSTEM to make changes to this file.

Only buttons available are "Try again" (useless) and "Cancel".

MaX.

MvdB · 29 Jun 2011

HornetMaX said:

Freaky.

I can rename the one in the C:\Windows\System32\drivers directory, but not the one in the C:\Windows\System32\DriverStore\... directory.
I'm prompted for admin rights (i have) but when I click I get a pop-up with the message:

You need permission to perform this action.

You require permission from SYSTEM to make changes to this file.

Only buttons available are "Try again" (useless) and "Cancel".

MaX.

Might not be a problem. Driverstore should only be a backup off, and by Windows. It's files should not be used except for restoring corrupted files.

If renaming to .old did work for the first one, as it should, reboot and keep fingers crossed...

HornetMaX · 29 Jun 2011

MvdB said:

If renaming to .old did work for the first one, as it should, reboot and keep fingers crossed...

For extra safety, at the price of a minor discomfort, I'm keeping my balls crossed too

I'll let you know. Out of curiosity, how did you narrow it down to that driver ?

MaX.

MvdB · 29 Jun 2011

HornetMaX said:

MvdB said:

If renaming to .old did work for the first one, as it should, reboot and keep fingers crossed...

For extra safety, at the price of a minor discomfort, I'm keeping my balls crossed too

I'll let you know. Out of curiosity, how did you narrow it down to that driver ?

MaX.

The info in dumpfiles can be read and analysed by using Windows debugging tools.
There are some non MS tools on the market but the standard MS stuff works best in my humble opinion...

But... let's first see if your problem is really solved...