[gismeu]

just realized my error, have copied them to the desktop, now continuing with your

instructions

[Advertisements]

next question, how do I  'zip'  them?

 

Thanks, Richard

[gismeu]

next question, how do I  'zip'  them?

 

Thanks, Richard

[Essexboy]

Right click one of the files and select Send to....Compressed (zipped) folder
Then drag and drop the second one into the zip folder

[gismeu]

Here they are,

 

thanks, Richard

Attached Files

•  091914-47408-01.zip   190.99KB   121 downloads

[Essexboy]

Sorry about the delay, it appears that who crashed no longer works in windows 10

Could you download whocrashed from here to your desktop http://www.resplendence.com/downloads

Install the programme and then run
On the page that opens click analyse

Then copy and paste the results please

[gismeu]

Hope that is what you need:

 

System Information (local)

Computer name: GIAMEU
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: 2847CZU, LENOVO
CPU: GenuineIntel Intel® Core™2 Duo CPU T6670 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2005778432 bytes total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 1/7/2016 1:52:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-48968-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x8323)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4380008, 0xFFFFFA8005897C90)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 1/7/2016 1:52:08 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisCmNotifyCloseAddressFamily+0x2D9)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4380008, 0xFFFFFA8005897C90)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 9/20/2014 12:55:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091914-47408-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8001777060, 0xFFFFF80000B9C4D8, 0xFFFFFA80024E5010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

 

[Essexboy]

OK they are old ones which would suggest that a mindump is not being generated for the latest BSOD's

OK we need to open an elevated command prompt :

This can be achieved by clicking on the Start menu, then selecting All Programs, and then Accessories.
You will now see a shortcut labeled Command Prompt. Right-click on it and select Run as administrator.
In the black box that opens type in (or copy and paste) the following command and press enter :

sfc /scannow

Once it has completed then reboot and let me know how the computer is behaving

[gismeu]

Last sentence was     'Windows Resource Protection did not find any integrity violations.'

 

will reboot now

[Essexboy]

Thanks

[gismeu]

sorry to say, still get a BSOD   

 

Thanks, Richard

[gismeu]

,

Edited by gismeu, 02 May 2016 - 10:50 AM.

[Essexboy]

Does it reference a file/driver on the blue screen ?
 
If the computer reboots then follow the steps on this page http://www.howtogeek...tomatic-reboot/

[gismeu]

I can do what you recommend, but there is never any text to see, plus the blue screen stays forever!

To get rid of it,  I press  ctrl+alt+Del and then turn it off or restart it in safe mode!

 

So please tell me if you still want me to turn off the automatic reboot option?

 

Thanks, Richard

[Essexboy]

If there is no text then it will be a pointless exercise

Download Speedfan and install it. Once it's installed, run the program and post here the information it shows. The information I want you to post is the stuff that is circled in the example picture I have attached.
If you are running on a vista machine, please go to where you installed the program and run the program as administrator.


(this is a screenshot from a vista machine)

[gismeu]

Hi Essexboy,

 

got Speedfan, but when trying to run it, the message says,  "Error <SPEEDFAN Driver Not Installed>  Is SPEEDFAN service started?

 

So will uninstall it, and then try again

 

Richard