Probably caused by : nvlddmkm.sys
Kaos
Here are the last lot of minidump files. For some reason it started writing kernal memory dump files. I have changed it back to minidump.
I have updated the video card which is now NVIDIA 8.17.12.7533
Thanks heaps
Wana
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
jraid.sys 9/29/2007 1:30:47 AM fffff880`010ab000 fffff880`010c6000 0x0001b000 0x46fde307
ComproHID64.sys 9/30/2007 9:56:11 PM fffff880`041f9000 fffff880`041fb380 0x00002380 0x470053bb
Rt64win7.sys 2/26/2009 5:04:13 AM fffff880`0494b000 fffff880`0497d000 0x00032000 0x49a65b0d
LHidFilt.Sys 6/17/2009 12:49:39 PM fffff880`062ec000 fffff880`062ff000 0x00013000 0x4a391ea3
LMouFilt.Sys 6/17/2009 12:49:43 PM fffff880`0630c000 fffff880`06320000 0x00014000 0x4a391ea7
ccHPx64.sys 6/19/2009 7:28:39 PM fffff880`04400000 fffff880`04493000 0x00093000 0x4a3c1f27
SymIMv.sys 6/22/2009 7:11:56 PM fffff880`02d1d000 fffff880`02d28000 0x0000b000 0x4a400fbc
SRTSP64.SYS 6/22/2009 10:45:21 PM fffff880`09914000 fffff880`09992000 0x0007e000 0x4a4041c1
SRTSPX64.SYS 6/22/2009 10:47:54 PM fffff880`02d83000 fffff880`02d97000 0x00014000 0x4a40425a
SYMEFA64.SYS 6/23/2009 5:52:39 PM fffff880`01160000 fffff880`011c7000 0x00067000 0x4a414ea7
SYMEVENT64x86.SYS 6/24/2009 4:19:12 PM fffff880`03f25000 fffff880`03f5b000 0x00036000 0x4a428a40
SYMTDI.SYS 7/6/2009 8:28:48 PM fffff880`03ed9000 fffff880`03f25000 0x0004c000 0x4a5296c0
SYMFW.SYS 7/6/2009 8:29:22 PM fffff880`03f6b000 fffff880`03f8d000 0x00022000 0x4a5296e2
SYMNDISV.SYS 7/6/2009 8:33:26 PM fffff880`03f5b000 fffff880`03f6b000 0x00010000 0x4a5297d6
- - The most common drivers are listed on this page: Driver Reference Driver Reference- 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.