Windows 7 BSOD Problems - All error info and computer specs attached

[jackclangston]

Hey guys,

I have been having off and on BSOD problems for the last couple of weeks. I have absolutely no idea how to diagnose this problem without having to take it to a professional. I was hoping that someone out there in the Windows 7 forum world could help.
Link Removed

 

[GeneralHiningII]

You have 110 updates installed - check Windows Update for more, usually there are about 130 to 140.

More than 95% of the Windows Error Reports from the 9th of February point to acad.exe, which is the AutoCAD software. Please fully uninstall AutoCAD or download and install the latest version (quick link for update most likely found here: Link Removed)

one dump points to Photoshop, another points to Firefox. Uninstall/Update both those programs.

For now, use Microsoft Security Essentials instead of Norton as your Antivirus. Feel free to reinstall Norton once the problem is fixed. Remember to only have one Antivirus installed on your computer.

Update your Ethernet NIC drivers here: Link Removed

There seems to be a problem with your SSD - try:
Updating the firmware: Link Removed
Running: HD Tune website (Run HDTune for about 2 to 3 days on each Storage Drive)
Using these instructions: Link Removed to test all your Storage Drives

I believe usasma has an article relating to SSD problems - try contacting him here: Link Removed

 

[usasma]

SSD issues canned speech is here: Link Removed
But here's a more updated version that I use most times:

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.

This looks (to me) to be:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).

We first look for compatibility and low-level driver problems as they are the most common.
This includes the firmware and controller issues mentioned above. If your SSD is connected to the Marvell controller, please connect it to a different one as there's likely to be no 2012 updates for the Marvell controller.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

RtNdPt60.sys Sun Jul 19 22:27:32 2009 (4A63D614)
Realtek NDIS User mode I/O Driver - Ethernet
Link Removed

Please un-install this one:
AiCharger.sys Wed Oct 20 08:00:33 2010 (4CBED9E1)
Asus Charger Driver [br] Likely BSOD cause
Link Removed

mvxxmm.sys Mon Nov 22 02:00:18 2010 (4CEA1502)
Marvell Aux NV Bridge DLL - related to mv91xx SCSI HD Controller
Link Removed

mv91xx.sys Mon Nov 22 02:00:45 2010 (4CEA151D)
Marvell MV91xx AHCI/RAID driver
Link Removed

If all of this doesn't fix things (and nothing new reveals itself), then we move on to hardware diagnostics: Link Removed

Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Wed Nov 28 09:53:12.486 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112812-9079-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:29:06.673[/B]
BugCheck Code: [B]BugCheck 1A, {41284, 1e725001, a498, fffff70001080000}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000000001e725001
Arg3: 000000000000a498
Arg4: fffff70001080000
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]firefox.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 19 11:52:50.336 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111912-9672-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]4 days 8:31:57.148[/B]
BugCheck Code: [B]BugCheck 1E, {0, 0, 0, 0}[/B]
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by :[B]Rt64win7.sys ( Rt64win7+1d65d )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x1E_Rt64win7+1d65d[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 12 20:54:41.001 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111212-9391-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]3 days 7:00:23.861[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff800030d60db, fffff8800b1cde30, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800030d60db, Address of the instruction which caused the bugcheck
Arg3: fffff8800b1cde30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME: [B]Photoshop.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!KiInsertTimerTable+13b[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  9 13:53:07.394 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110912-9344-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]12 days 23:59:28.681[/B]
BugCheck Code: [B]BugCheck 24, {1904fb, fffff8800a192578, fffff8800a191dd0, fffff800030c0dbe}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!DeleteNodeFromTree+14e )[/B]
BugCheck Info: [B]NTFS_FILE_SYSTEM (24)[/B]
Arguments: 
Arg1: 00000000001904fb
Arg2: fffff8800a192578
Arg3: fffff8800a191dd0
Arg4: fffff800030c0dbe
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID: [B]X64_0x24_nt!DeleteNodeFromTree+14e[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 27 13:52:27.262 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102712-9672-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]7 days 13:40:02.074[/B]
BugCheck Code: [B]BugCheck 1E, {0, 0, 0, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
Arguments: 
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Wed Nov 28 09:53:12.486 2012 (UTC - 5:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[B]RtNdPt60.sys                Sun Jul 19 22:27:32 2009 (4A63D614)[/B]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
ICCWDT.sys                  Wed Aug 18 04:27:45 2010 (4C6B9981)
AsIO.sys                    Mon Aug 23 21:53:02 2010 (4C7325FE)
[B]AiCharger.sys               Wed Oct 20 08:00:33 2010 (4CBED9E1)[/B]
mvxxmm.sys                  Mon Nov 22 02:00:18 2010 (4CEA1502)
mv91xx.sys                  Mon Nov 22 02:00:45 2010 (4CEA151D)
SYMDS64.SYS                 Mon May 16 18:15:03 2011 (4DD1A1E7)
ndisrd.sys                  Fri Aug 12 06:14:50 2011 (4E44FD1A)
LHidFilt.Sys                Fri Sep  2 02:23:09 2011 (4E60764D)
LMouFilt.Sys                Fri Sep  2 02:23:15 2011 (4E607653)
ASUSFILTER.sys              Tue Sep 20 11:46:33 2011 (4E78B559)
asmtxhci.sys                Wed Nov  2 23:00:22 2011 (4EB203C6)
asmthub3.sys                Wed Nov  2 23:00:32 2011 (4EB203D0)
HECIx64.sys                 Wed Nov  9 19:52:25 2011 (4EBB2049)
SYMNETS.SYS                 Sat Nov 12 16:11:53 2011 (4EBEE119)
Ironx64.SYS                 Mon Nov 14 21:00:53 2011 (4EC1C7D5)
SYMEVENT64x86.SYS           Tue Nov 22 13:30:48 2011 (4ECBEA58)
IntcDAud.sys                Tue Dec  6 06:23:07 2011 (4EDDFB1B)
iaStor.sys                  Wed Feb  1 19:15:24 2012 (4F29D59C)
Rt64win7.sys                Fri Feb  3 08:00:02 2012 (4F2BDA52)
iusb3hub.sys                Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys                Mon Feb 27 05:56:53 2012 (4F4B6175)
iusb3hcs.sys                Mon Feb 27 05:58:49 2012 (4F4B61E9)
igdkmd64.sys                Mon Mar 19 19:31:54 2012 (4F67C1EA)
RTKVHD64.sys                Tue Mar 27 05:01:50 2012 (4F7181FE)
tixhci.sys                  Tue May  1 20:24:17 2012 (4FA07EB1)
tihub3.sys                  Tue May  1 20:24:23 2012 (4FA07EB7)
SYMEFA64.SYS                Fri May 18 21:29:56 2012 (4FB6F794)
ccSetx64.sys                Wed Jun  6 23:00:55 2012 (4FD01967)
SRTSP64.SYS                 Mon Jul  2 14:20:28 2012 (4FF1E66C)
SRTSPX64.SYS                Mon Jul  2 14:20:37 2012 (4FF1E675)
EraserUtilRebootDrv.sys     Tue Jul 31 19:36:50 2012 (50186C12)
eeCtrl64.sys                Tue Jul 31 19:36:51 2012 (50186C13)
IDSvia64.sys                Tue Aug 28 22:48:40 2012 (503D8308)
EX64.SYS                    Wed Sep  5 18:31:45 2012 (5047D2D1)
ENG64.SYS                   Wed Sep  5 18:33:39 2012 (5047D343)
BHDrvx64.sys                Fri Oct 19 00:40:41 2012 (5080D9C9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 19 11:52:50.336 2012 (UTC - 5:00)**************************
tixhci.sys                  Mon May 16 20:51:45 2011 (4DD1C6A1)
tihub3.sys                  Mon May 16 20:52:00 2011 (4DD1C6B0)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 12 20:54:41.001 2012 (UTC - 5:00)**************************
BHDrvx64.sys                Fri Sep 28 20:24:10 2012 (50663FAA)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[jackclangston]

Thank you guys! I am going to check all of this out this weekend. I will let you know the results in the upcoming week.

 

[jackclangston]

It is up and has been working fine for a couple of days now. Thanks Guys!

 

[usasma]

Glad to hear it! Thanks for letting us know.