New
#1
Blue screen
On few occasions I hear a sound as if you connect or disconnect a USB device, after that I get the Blue screen and when Windows 7 is back I see this notice (see attachment) What that could be please?
On few occasions I hear a sound as if you connect or disconnect a USB device, after that I get the Blue screen and when Windows 7 is back I see this notice (see attachment) What that could be please?
Thank you axe0
Here is the file attached per your distractions
Looks like a driver from Creative is causing the crashes, update the software/drivers.
Code:v0700vid Creative Live! Cam Chat HD Driver c:\windows\system32\drivers\v0700vid.sys 5: kd> lmvm V0700Vid Browse full module list start end module name fffff880`04600000 fffff880`046602c0 V0700Vid T (no symbols) Loaded symbol image file: V0700Vid.sys Image path: \SystemRoot\system32\DRIVERS\V0700Vid.sys Image name: V0700Vid.sys Browse all global symbols functions data Timestamp: Wed Sep 07 07:30:56 2011 (4E670190) CheckSum: 00066D53 ImageSize: 000602C0 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Thanks, axe0, driver updated, I'd let you know.
It is interesting why all of the sudden that diver is causing a blue screen (I have had it for years) when there were no other changes to the computer.
This is only an example of things that can cause problems, an example where a user would not think of quickly.
In the background various of things happen, each thing that changes can change the behaviour of the system and can affect anything.
For example you change a setting in program A to enable a function, in the background happens the following:
This function assigns itself some memory and writes something to it.
Program B reserved this memory for later use and finds out the memory is not empty, thus program B calls the bugcheck function and so the result is a BSOD.
This BSOD is caused by program A wherein the function was enabled, because it does not check if memory has been reserved or not.
It is also possible that this function from program A would have written data to the memory while program B had already written data to the memory, the bug would again be not checking if memory hasr already been in use. The result is corrupted pool for which driver verifier would be required to ultimately find out that this single function of program A was the cause.
With changes people think of added hardware or installed programs, but not setting changes.
After updating Creative driver I've had another crush today.
Any advice?
Uploaded another log
Thanks.
Last edited by yossibac; 16 Jun 2016 at 05:14.