«

GigaStudio's FileSpy.sys didn't agree with my PC

For a few weeks now my home machine has been rebooting itself mid-operation, or just plain hanging. After reboots, dump files were sent to Windows Crash Analysis, but the website they redirected me to only explained the error as a problem with an unidentified driver. I tried all of the usual things, but all of my devices seemed to be operating well.


The event log had several errors like:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/5/2005
Time: 7:45:34 AM
User: N/A
Computer: MYCOMPUTER
Description:
Error code 1000007f, parameter1 00000008, parameter2 80042000,
parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 38 2c 20 000008,
0038: 38 30 30 34 32 30 30 30 80042000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

Have you gotten a blue screen of death, or had a crash or hang where the system error code was 1000007f? Did it mention a driver called filespy.sys? Are you running Tascam’s GigaStudio? Believe it or not, Gigastudio seems to have been at the root of my home machine’s recent instability. I’ve never used the software (it came as a free add-on with my external soundcard), so I uninstalled it about a week ago. Bingo, no more crashes.

The really weird thing is I’ve had GigaStudio installed for a few months, and never even thought to look at it as the possible culprit. It turns out that GigaStudio includes a file monitoring feature (implemented by the aforementioned driver filespy.sys), which seems to have caused Windows to freak out.


I’ve done some web searching and it seems like I’m not the only one who has been bitten by this.

As always, YMMV. I’m not a professional driver debugger or computer maintenance engineer, just sharing my experience in hope that someone else who runs into this may find it helpful.


This posting is provided “AS IS” with no warranties, and confers no rights.