New
#1
BSOD while playing Far Cry 3 Blood Dragon. Can't remember error number
Hello, I've been blue screening with a frequency that I don't really care for. The dump file is attached. Please take a look. Thanks
Hello, I've been blue screening with a frequency that I don't really care for. The dump file is attached. Please take a look. Thanks
MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).
If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.
systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.
Overclocking
If you are overclocking any hardware, STOP. Reset any changed values back to default.Code:MaxSpeed: 3600 CurrentSpeed: 4319
Code:RTCore64.sys Mon Mar 11 11:32:06 2013 (513D6C56)WarningThis is overclocking software and can lead to system instability and BSOD's.
Please reset all components to their stock speeds and then remove the software.
RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
Driver Reference Table - RTCore64.sys
Daemon Tools/Alcohol %
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)Code:sptd.sys Mon Oct 12 02:55:14 2009 (4AD24632)
Driver Reference Table - sptd.sys. Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ
As an alternative, many people recommend the use of Total Mounter or Magic ISO
TipRevo Uninstaller
Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems
Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).
Security App
Crashes indicate AVG being a possible cause. Remove AVG and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software
Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.
Microsoft Security Essentials, Free antivirus for windows
Malwarebytes Anti-Malware Free
WarningDO NOT start the free trial of MalwareBytes, unselect that option when prompted.
TipMake full scans with both separately.
Basic checks:
Please run these tests and report back the results
1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure
BSOD BUGCHECK SUMMARY
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800032d665b, fffff8801882fef0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiSearchForNewThread+26b ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff800032d665b, Address of the instruction which caused the bugcheck Arg3: fffff8801882fef0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!KiSearchForNewThread+26b fffff800`032d665b 66453b9080010000 cmp r10w,word ptr [r8+180h] CONTEXT: fffff8801882fef0 -- (.cxr 0xfffff8801882fef0) rax=0000000000000200 rbx=0000000000000000 rcx=fffff8800658d710 rdx=0000000000000000 rsi=fffff8000325a000 rdi=fffff880063e4180 rip=fffff800032d665b rsp=fffff880188308d0 rbp=0000000000000001 r8=fffffa8025093880 r9=0000000000000009 r10=0000000000000000 r11=fffff880063e4180 r12=0000000000000065 r13=0000000000000000 r14=0000000000000000 r15=fffff88006589180 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!KiSearchForNewThread+0x26b: fffff800`032d665b 66453b9080010000 cmp r10w,word ptr [r8+180h] ds:002b:fffffa80`25093a00=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: fc3_blooddrago CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800032d665b STACK_TEXT: fffff880`188308d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSearchForNewThread+0x26b FOLLOWUP_IP: nt!KiSearchForNewThread+26b fffff800`032d665b 66453b9080010000 cmp r10w,word ptr [r8+180h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiSearchForNewThread+26b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6 STACK_COMMAND: .cxr 0xfffff8801882fef0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!KiSearchForNewThread+26b BUCKET_ID: X64_0x3B_nt!KiSearchForNewThread+26b Followup: MachineOwner ---------
I think , the bsods is being caused by your drivers, you can either try updating them or simply disabling the device. Try updating first, if that doesnt help, try disabling.
-Click Start , and type "device manager" (without quotes) into the search field.
-Click Device Manager from the results list.
-In the Device Manager window that opens, double-click IEEE 1394 Bus host controllers .
-Select the 1394 Controller.
-Right click on it and select Update Driver software.
Select Search automatically for updated driver software.
If windows is not able to update automatically, download the updated drivers yourself and instead of letting windows search automatically, point it to the location of your downloaded drivers by selecting Browse my computer for driver software.
If you want to disable the device, then instead of selecting update driver software in the last step, choose disable.
Hopefully it will work.....
Koolkat, thanks for the advice. Been a few days with no bluescreen. It was likely AVG and Daemon tools that was doing it. I just got rid of those and no problems. My overclock has been stable for months, so I know that wasn't the issue :3 Thanks again for your help