Identify the driver for me!

[Dnomes]

While this title insinuates that I only have one problem, I actually have two. Driver Verifier has found a faulty driver and I want you to help me find it.
The other problem is,"0x0000001e". It happens only when I fullscreen any flash video, it either freezes or BSoD's on me. This is the bad part, I cannot get a dump, because the blue screen itself freezes. What should I do with that part?

Edit: I might think that the driver verifier and the fullscreen part is connected, but one thing It ain't, that's my hardware. I have tested the fullscreen problem in safe mode, so I am helpless as it is.

 

[yowanvista]

I suspect your Logitech Gamepanel drivers are the cause. I suggest installing an updated copy of the drivers, or removing it altogether.

Unable to load image \SystemRoot\system32\drivers\LGVirHid.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for LGVirHid.sys
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys

 

[Dnomes]

What could be the cause to problem 2?

 

[yowanvista]

All 3 dumps blame the Logitech driver

 

[Dnomes]

Read "The other problem is,"0x0000001e". It happens only when I fullscreen any flash video, it either freezes or BSoD's on me. This is the bad part, I cannot get a dump, because the blue screen itself freezes. What should I do with that part?"

Thank you for your assistance so far though

 

[Dnomes]

First problem is solved, now this is the only one

 

[yowanvista]

Read "The other problem is,"0x0000001e". It happens only when I fullscreen any flash video, it either freezes or BSoD's on me. This is the bad part, I cannot get a dump, because the blue screen itself freezes. What should I do with that part?"

Thank you for your assistance so far though

Boot into safe mode with networking and upload the other dumps

 

[Dnomes]

I don't quite understand what you mean? How can I find the dumps when they didn't finish. Last night i tried testing it. Got my blue screen and let it stay, The next morning it was still frozen at "Creating dump: 50" or what it says. It didn't make progress at all.

 

[yowanvista]

Without the dump files we can't determine the cause of the BSOD
I'll suggest testing your RAM http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run the SFC tool http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Troubleshooting specific Stop messages

 

[Dnomes]

Everything went well... What should I do

I tried full screening again, and this time the dump almost finished, should I keep retry doing it, or will it damage my system?

 

[Dnomes]

I tried to BSoD myself again and got the dump file! But the problem is that I no longer can put it in a ZIP or RAR archive. How do I do it XD

Nevermind. Now I am excited

 

[yowanvista]

Run the SFC tool http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

BugCheck 1E, {ffffffffc0000005, fffff880063d5df0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )

 

[Dnomes]

I have done it, and it shows no error.

Should I format my computer?

 

[CarlTR6]

Test your RAM with Memtest86. Follow the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Let Memtest run for at least 7 passes. This will take 6-8 hours. Run it from a cold boot after your computer has been off for an hour or two. Errors, if any, will show on your screen in red. If you see errors, you can stop the test. Post back with your results.

 

[Dnomes]

Will run the test one more time, I'll post the results tomorrow.

 

[CarlTR6]

Very good.

 

[Dnomes]

14 passes, zero errors.

Any other suggestions?

 

[Dnomes]

I just formatted my PC, and the problem still occours...

 

[zigzag3143]

I just formatted my PC, and the problem still occours...

If you installed the OS again on a formatted drive and the problem re-occured it has to be hardware.

read here

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Thanks


Ken

 

[Dnomes]

I used "WhoCrashed", and it blamed the ATI driver! So I googled about BSoD's with that driver, and turns out that there are people experiencing it too. So I tried to use my disc with the old driver (But unfortunately not compatible with Windows 7), read that it fixed the problem for many other. So could it be ATI's fault? I also removed all the display driver and left myself with only the VGA one, I could actually watch a full screen video.