BSOD Random but csrss.exe every time

[Dooahhdoo]

Hi,

Its a new build only two months old all new hardware. Asrock z68 extreme4 board, i7 2600K processor, 16GB Corsair RAM, BeQuiet 750W PSU, GTX 580 graphics, win7 enterprise 64bit. Initially I thought the crashes were heat related but monitoring the board shows cool temps. I am not overclocking either.

Any help appreciated.
Thanks.

View attachment 186585

 

[zigzag3143]

Hi,

Its a new build only two months old all new hardware. Asrock z68 extreme4 board, i7 2600K processor, 16GB Corsair RAM, BeQuiet 750W PSU, GTX 580 graphics, win7 enterprise 64bit. Initially I thought the crashes were heat related but monitoring the board shows cool temps. I am not overclocking either.

Any help appreciated.
Thanks.

View attachment 186585

You have one driver verified crash pointing to csrss.exe and one Related to FNETURPX.SYS FNETURPX from Analog Devices Inc. from FNet Co., Ltd.. I am betting its that and it is from 2008. I would remove it at least to test.

If you have any doubt you can run a system file check to verify the OS files (csrss)

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.



Other old drivers

LVUSBS64.sys    2/3/2007 1:05:16 PM        fffff880`07ff3000    fffff880`07fff980    0x0000c980    0x45c4cedc                        
CamDrL64.sys    2/3/2007 1:17:27 PM        fffff880`088bb000    fffff880`089a2a00    0x000e7a00    0x45c4d1b7                        
FNETURPX.SYS    10/3/2008 9:27:02 PM    FNETURPX.SYS+1670    fffff880`01bf1000    fffff880`01bfa000    0x00009000    0x48e6d476                      vnaap.sys    12/29/2008 7:10:44 AM        fffff880`055c0000    fffff880`055e60c0    0x000260c0    0x4958be44

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[Dooahhdoo]

Hi,
Thanks for the very quick response. The fneturpx.sys is a driver for turbo usb supplied with the board. That was removed a few days ago but have still had BSODs after this.
I will let you know the results of the driver updates and sfc /scannow.

Thanks

 

[zigzag3143]

Hi,
Thanks for the very quick response. The fneturpx.sys is a driver for turbo usb supplied with the board. That was removed a few days ago but have still had BSODs after this.
I will let you know the results of the driver updates and sfc /scannow.

Thanks

There is a report at the end and we could use the cbs.log file uploaded for analysis

 

[Dooahhdoo]

Hi,
Ran SFC /scannow three times, no errors found. The driver versions that were old were from a logitech quickcam 4000 which has now been removed from the system as well as the Turbo USB utility.
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>

Please find attached the cbs.log of sfc.
Thanks.

View attachment 186597

 

[zigzag3143]

Hi,
Ran SFC /scannow three times, no errors found. The driver versions that were old were from a logitech quickcam 4000 which has now been removed from the system as well as the Turbo USB utility.
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>

Please find attached the cbs.log of sfc.
Thanks.

View attachment 186597

IF SFC didnt find any violations there is something else wrong.