BSoD need direction

Wana

New Member
#1
Hey
I have had a heap of BSoD since I bought this pc. I have run out of things to update including the BIOS, drivers etc.
Here is the dump file for the latest one.

I am using Windows 7 so i don't kow why it referenced DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


Any information would be much appreciated
Thanks
 


Last edited:

Saltgrass

Excellent Member
Microsoft Community Contributor
#2
From your post, it appears you might want to check for a video driver update. You can check the date and version in the Windows\System32\drivers folder.

Probably caused by : nvlddmkm.sys
 


Last edited:

Wana

New Member
#3
Hey thanks saltgrass, I was able to upgrade the driver but now I have this one.

Any ideas?
 


Last edited:

Saltgrass

Excellent Member
Microsoft Community Contributor
#4
It might be better if you attach your dump file and some of the other things they ask for in the sticky. Maybe one of the experts can help.
 


kaos

Senior Member
#5
hi , if you upload the minidump i will upload the driver dates for you :)
 


Wana

New Member
#6
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
 


Attachments

zigzag3143

Honorable Member
Microsoft MVP
#7
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
These were probably caused by memory corruption caused by an un-named driver. Please run these two tests




Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

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.
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#8
You have a jraid.sys file from 2007, on my system it is 2010.

It is not the only one, but I do not know if they are related, or might be causing a problem.

ComproHID64.sys
TSDDD.dll no information shown
 


zigzag3143

Honorable Member
Microsoft MVP
#9
Thanks to saltgrass as an afterthought here are the driver you need to update. I would also remove symantec it is a known BSOD cause.

Code:
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
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
 


nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#10
ComproHID64.sys is for a TV Card. You can get updated drivers from Compro Technology, Inc.
 


Wana

New Member
#11
Thanks heaps for all the replys guys
Funny thing is i removed that compro tv card over 12 months ago so I deleted the file :)
I mouse over the jraid.sys file and it has 2010 yet it displays 2007 hmm

got another BSoD yesterday so i have attached the bmp file. View attachment 070711-23088-01.dmp

To top it off I ran memtest88+ last night first 2 passes were 0 errors kept it running and when I woke up the computer had rebooted and went to sleepmode. Why would it do that?
 


Last edited:

kaos

Senior Member
#12
Re run the test :)
possible
error, you need 7 passes at least, i ran mine all nite and it was still running in the morning at 16 passes +
 


#13
Woot!
I got 9 passes with Memtest86+ and no errors. I guess that is the good news.
The bad news is the BSoB after the mem check.
View attachment 071011-25708-01.dmp

Wana
 


nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#14
The faulting driver is LMouFilt.Sys can you update your logitech setpoint software.
 


#15
Ok lets see how that one goes just found the update for LMouFilt.Sys
 


nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#16
Get back to us, if you have any problems after updating the driver. :)
 


Elmer

Extraordinary Member
#18
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes:
Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.

You did a good job of updating the drivers Zigzag mentioned. Unfortunately you still have Norton on there.

Norton is known to be a cause of BSOD's on Windows 7 systems. I suggest that you uninstall Norton using the Norton Removal Tool in Safe Mode. Download Blue Screen friendly Microsoft Security Essentials as its replacement. Make sure Windows firewall is enabled!

I've also spotted this outdated driver:

000.fcl Fri Sep 26 14:11:22 2008 CyberLink FCL Driver
 


#19
YEA!! another BSOD.
I had uninstalled Norton hoping it will cure the world but its back to the drawing board.

Here is the latest dump file View attachment 082011-32760-01.dmp
Thanks again for all your help
Wana
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.