New
#1
BSOD on win7
Hello
Got two BSODs today.
The first one said someting about the NTFS.sys
and the second was the "NO OR LESS EQUAL" thing.
Reinstalled my win7 pro x64, like a month ago.
Any help would be nice.
Hello
Got two BSODs today.
The first one said someting about the NTFS.sys
and the second was the "NO OR LESS EQUAL" thing.
Reinstalled my win7 pro x64, like a month ago.
Any help would be nice.
Hello,
I can't help but wonder if libusb is causing this mess:Do you know what program is using it? If so, uninstall it. If not, go to C:\Windows\System32\drivers, and delete libusb0.sys. Also go to C:\Windows\system32, and delete libusbd-nt.exe.Code:Event[17930]: Log Name: System Source: Service Control Manager Date: 2011-06-08T16:59:43.651 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ikaros-PC Description: The LibUsb-Win32 - Daemon, Version 0.1.10.1 service failed to start due to the following error: The system cannot find the file specified. Event[17931]: Log Name: System Source: Service Control Manager Date: 2011-06-08T16:59:43.584 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-21-943333451-365008668-2012038470-1001 User Name: Ikaros-PC\Ikaros Computer: Ikaros-PC Description: A service was installed in the system. Service Name: LibUsb-Win32 - Daemon, Version 0.1.10.1 Service File Name: system32\libusbd-nt.exe Service Type: user mode service Service Start Type: auto start Service Account: LocalSystem Event[17932]: Log Name: System Source: Service Control Manager Date: 2011-06-08T16:59:43.556 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-21-943333451-365008668-2012038470-1001 User Name: Ikaros-PC\Ikaros Computer: Ikaros-PC Description: A service was installed in the system. Service Name: LibUsb-Win32 - Kernel Driver, Version 0.1.10.1 Service File Name: system32\drivers\libusb0.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:
Install updated ATI display drivers from here: AMD Graphics Drivers & SoftwareCode:atikmdag.sys Tue Mar 08 23:32:17 2011 (4D7702D1)Install these updated JMicron SATA/RAID drivers: ftp://driver.jmicron.com.tw/SATA_Con...17.63_WHQL.zipCode:Event[17972]: Log Name: System Source: Display Date: 2011-06-08T16:50:59.000 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Ikaros-PC Description: Display driver amdkmdap stopped responding and has successfully recovered.I don't see anything at all in the logs to point to a network error, but I do suggest you update your Realtek ethernet drivers from here: RealtekCode:jraid.sys Mon Nov 03 21:20:09 2008 (490FB159)
Your current drivers have been known to cause crashes with the latest Windows versions, and an update may save you later grief....Summary of the dumps:Code:Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
Code:Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Sun Jun 19 07:04:57.891 2011 (UTC - 4:00) System Uptime: 0 days 0:21:17.000 *** WARNING: Unable to verify timestamp for usbhub.sys *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys *** ERROR: Symbol file could not be found. Defaulted to export symbols for USBPORT.SYS - Probably caused by : usbhub.sys ( usbhub+1a193 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: LolClient.exe FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_usbhub+1a193 BiosReleaseDate = 12/10/2008 SystemProductName = EX58-UD3R ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Sun Jun 19 06:42:19.643 2011 (UTC - 4:00) System Uptime: 0 days 3:22:15.751 *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys Probably caused by : Ntfs.sys ( Ntfs+c8a57 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x50_Ntfs+c8a57 BiosReleaseDate = 12/10/2008 SystemProductName = EX58-UD3R ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Run the attached batch file, it will delete the files for you if they exist. Post a screenshot of the command window that opens, see here: A Preferred Method of Uploading/Posting Screen Shots
Looks like the files are already gone. Finish up whatever other suggestions you might not have done yet, and watch for more crashes. If you get them, please upload a new jcgriff2 report.
Not much I can say about that one, honestly. Cracked software is notorious for causing problems. Uninstall the cracked game, install a copy that you paid for, and we can go from there.
...Summary of the dumps:
Code:Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Mon Jun 20 07:57:17.561 2011 (UTC - 4:00) System Uptime: 0 days 1:18:27.670 *** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.sys - *** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys - *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : dxgmms1.sys ( dxgmms1!VidMmInterface+9d2c ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: Dungeon Siege FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VidMmInterface+9d2c BiosReleaseDate = 12/10/2008 SystemProductName = EX58-UD3R ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Got an other BSOD today
when playing mass effect 2.
Well start by installing updated Realtek wireless drivers from here: Realtek
Run driver verifier: Driver Verifier - Enable and Disable
Just something to try, update your BIOS: GIGABYTE - Motherboard - Socket 1366 - GA-EX58-UD3R (rev. 1.7)
...Summary of the dumps:
Code:Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Wed Jun 22 01:37:52.299 2011 (UTC - 4:00) System Uptime: 0 days 0:07:12.297 Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+2aa ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0xA_nt!KiCommitThreadWait+2aa BiosReleaseDate = 12/10/2008 SystemProductName = EX58-UD3R ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Wed Jun 22 01:29:30.004 2011 (UTC - 4:00) System Uptime: 0 days 0:29:03.001 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+448c6 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: services.exe FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+448c6 BiosReleaseDate = 12/10/2008 SystemProductName = EX58-UD3R ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Wed Jun 22 10:37:38.789 2011 (UTC - 4:00) System Uptime: 0 days 8:58:39.897 *** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.sys - *** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys - *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : dxgmms1.sys ( dxgmms1+1983 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: MassEffect2.ex FAILURE_BUCKET_ID: X64_0x50_dxgmms1+1983 BiosReleaseDate = 12/10/2008 SystemProductName = EX58-UD3R ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Mon Jun 20 22:47:23.456 2011 (UTC - 4:00) System Uptime: 0 days 0:31:09.673 *** ERROR: Module load completed but symbols could not be loaded for pci.sys Probably caused by : pci.sys DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x9F_3_rtl8192se_IMAGE_pci.sys ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``