Hi,
I have been experiencing various BSOD crashes lately and have finally decided to look into what's going on. I cannot pinpoint exact symptoms as they have all been different e.g. browsing in Firefox and chrome, watching video in QuickTime,etc.
The BSOD error messages have also varied and I have attached the dump files for analysis. I will run a memory test this evening after I finish working for the day.
Any help would be great
Regards Dave
Dave Hi and welcome
Yep just a few BSOD's eh. well did a quick analysis and it seems most of the chreashes are caused by memory. A couple were caused by the dierectx driver (which still could be a memory issue) that being said I would
download memtestx86 and run it for at least 5 passes. yes its a long time. you need to so that you can tell if it is a memory issue or a heat issue
I would also run a system file check. type cmd in search>right click and run as admin>sfc /scannow
If you are overclocking stop
let us know the results
Ken J+
Code:111309-20779-01.dmp 11/13/2009 12:21:42 PM BAD_POOL_HEADER 0x00000019 00000000`00000020 fffffa80`08615410 fffffa80`08615460 00000000`04050016 hal.dll hal.dll+2bc60 111809-22230-01.dmp 11/18/2009 12:34:12 PM BAD_POOL_HEADER 0x00000019 00000000`00000020 fffffa80`09615dc0 fffffa80`09615e60 00000000`040a0000 ntoskrnl.exe ntoskrnl.exe+71f00 110409-27502-01.dmp 11/4/2009 8:12:46 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffffff`ffffffd8 00000000`00000002 00000000`00000000 fffff800`02cc622b ntoskrnl.exe ntoskrnl.exe+71f00 121109-24070-01.dmp 12/11/2009 10:42:46 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`02c94bf0 ntoskrnl.exe ntoskrnl.exe+71f00 010410-19890-01.dmp 1/4/2010 12:09:36 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71ed0 120809-19718-01.dmp 12/8/2009 8:25:34 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff880`07f65d10 00000000`00000000 00000000`00000000 hal.dll hal.dll+4a56 112909-20560-01.dmp 11/29/2009 8:28:06 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00003452 00000000`06a6a000 fffff700`01110570 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 122409-20607-01.dmp 12/24/2009 10:55:18 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00041284 00000000`2148a001 00000000`0000f129 fffff700`01080000 ntoskrnl.exe ntoskrnl.exe+71f00 120509-20576-01.dmp 12/5/2009 3:55:36 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa7f`9582fc53 00000000`00000001 fffff880`04a38101 00000000`00000007 dxgkrnl.sys dxgkrnl.sys+16e6 010410-20139-01.dmp 1/4/2010 11:47:52 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`00102ba2 fffff880`02a120c0 00000000`00000000 win32k.sys win32k.sys+c2ba2 120409-21106-01.dmp 12/4/2009 1:51:00 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`000f65a9 fffff880`0a971f40 00000000`00000000 win32k.sys win32k.sys+465a9 122009-20545-01.dmp 12/20/2009 6:14:22 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`053daa65 fffff880`0a0f2890 00000000`00000000 dxgmms1.sys dxgmms1.sys+2da65 121409-21793-01.dmp 12/14/2009 5:36:52 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`02d8e8aa fffff880`035e7838 fffff880`035e7090 ntoskrnl.exe ntoskrnl.exe+1768aa 122309-19952-01.dmp 12/23/2009 2:42:30 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`02c9b35f fffff880`03d8d5c8 fffff880`03d8ce20 ntoskrnl.exe ntoskrnl.exe+9735f
Thanks to getting back to me Ken.
The system scan showed no errors and before receiving your reply I ran the memory test for three passes without any errors. I will run the memory test again overnight just to be sure and get back to you with any results.
First, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:
Here's the older drivers:How To Find Updated 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.
Lot's of the errors refer to System Services or System Threads. I'd suggest running Driver Verifier according to these directions once you've updated your drivers above:Code:SSPORT.sys Thu Aug 11 19:07:32 2005 DgiVecp.sys Thu Oct 30 23:38:29 2008 LVUSBS64.sys Sat Jul 26 11:06:36 2008 RTSTOR64.SYS Thu Jun 05 07:21:42 2008
Once this is all done, then please try running Driver Verifier according to these directions:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, 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).
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.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Thanks John
Just a quick update.
I ran 5 passes this morning which located 7 errors. This prompted me to take out all the memory and reseat it in different locations. I ran the memory test for 3 passes with out any errors (I had to get some work done eventually) and will run the test again this evening.
In the meantime I have received the reply above from John.
The first 2 drivers were associated with the Samsung printer which thankfully have just released new drivers that are now installed.
The last driver (RTSTOR64.SYS) was to do with the Realtech USB Card Reader which has also now been updated. Interestingly the new driver does not use the file that you referenced but it is still in the driver folder. I am assuming that it is safe to leave it there.
Finally, the LVUSBS64.SYS driver is associated with some Logitech devices. I am unable to find a way to update this driver. All the Logitech products I have installed do not have software associated and use the generic system drivers (according to the manufacturer's website). Any help with this driver would be much appreciated.
I am still to run the driver verifier and will more than likely do so tomorrow want to hear back about the Logitech driver.
Thanks again for your help
Dave
I have run the memory test again this morning and received 16 errors. I then took it out two of the memory modules and ran the memory test again for six passes without any error.
Then as I was reading how to run the driver verifier (still with only two memory modules inserted) I received a BSOD. I have attached the dump file below and will await correspondence from one of you guys before doing anything else.
The system has memory errors when cold, and none when warmed up?
Try running the memory test overnight and see what happens (after it's warmed up).
I'd suspect that this is the main problem with the system.
Until the memory situation is resolved, there's no sense in working with the memory dump files - as most of them will reflect a memory component in the error.
But, we can view the older drivers from the dump files - so they come in handy for that.
The RTSTOR64.SYS program appears to have been updated as it no longer appears in the dump file.
BUT, the LVUSBS64.sys is still there (so I wonder about what Logitech said). Regardless, please locate the LVUSBS64.sys on your system (most likely in C:\Windows\System32\drivers) and rename it from .sys to .BAK
You can also use this free program to stop drivers from loading: Autoruns for Windows
The SSPORT.SYS driver and the DgiVecp.sys (has something to do with Samsung Port contention - most likely a printer) are still there and must either be updated or removed.
I just realised that I never updated this thread once the problem was resolved. It turns out that a BIOS update was able to fix my problem.
Quote