metalmiketh
New member
- Local time
- 7:48 AM
- Messages
- 11
I've had many crashes and BSoD problems lately. Hopefully somebody here can help.
My Computer
At a glance
Windows 7 Home Premium 64 bit
- OS
- Windows 7 Home Premium 64 bit
[LIST=1]
[*]Start Menu\Programs\GIGABYTE Public:Start Menu\Programs\GIGABYTE Public
[*]Start Menu\Programs\GIGABYTE\AutoGreen Public:Start Menu\Programs\GIGABYTE\AutoGreen Public
[*]Start Menu\Programs\GIGABYTE\ET6 Public:Start Menu\Programs\GIGABYTE\ET6 Public
[*]Start Menu\Programs\GIGABYTE\GHOST(6980) Public:Start Menu\Programs\GIGABYTE\GHOST(6980) Public
[/LIST]
GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge
May cause BSOD on Win7 systems - uninstall to test
Start Menu\Programs\avast! Free Antivirus Public:Start Menu\Programs\avast! Free Antivirus Public
rb:
rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; NVIDIA and restart the system. Delete remnants of its drivers/older drivers using Driver Fusion/SweeperThe goal is to test all the RAM sticks and all the motherboard slots.
Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
[FONT="Lucida Console"]STOP 0x00000019: BAD_POOL_HEADER
Usual causes: Device driver
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: csrss.exe
..................................................................
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM),
Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff8bf0fae5d8f, 8, fffff8bf0fae5d8f, 5}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+437c1 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: SearchIndexer.
..................................................................
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure,
Installing a faulty or mismatched hardware (especially memory) or a failure after installing it,
3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards,
Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard,
Missing Service Pack
BugCheck 7F, {8, 80050033, 406f8, fffff8800f6e1c88}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+2b7c88 )
Timestamp: Tue May 15 13:35:36 2012 (4FB20748)
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Stress.exe
..................................................................
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM),
Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
BugCheck 50, {ffffffffffffffd0, 1, fffff8000f8e432c, 0}
*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : AppleCharger.sys ( AppleCharger+1a9b ) [GIGABYTE On/Off Charge driver. See here for details - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm
May cause BSOD on Win7 systems - uninstall to test]
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
Timestamp: Wed Nov 02 08:46:00 2011 (4EB0AEE8)
..................................................................
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
BugCheck 1A, {41790, fffffa8004dd8ac0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: dllhost.exe
..................................................................
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
BugCheck 1A, {41790, fffffa8004dd8b20, ffff, 0}
Probably caused by : win32k.sys ( win32k!FreeView+a2 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: rundll32.exe
..................................................................
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM),
Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff8af02eb1010, 0, fffff8000f9b89bc, 5}
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: audiodg.exe
...................................................................
STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver,
Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
BugCheck 24, {1904fb, fffff88003593468, fffff88003592cc0, fffff8000f83ff75}
Probably caused by : ntkrnlmp.exe ( nt!RtlSubtreePredecessor+9 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System[/FONT]
Please uninstall the following software using the free version of Revo Uninstaller (Use advanced mode to uninstall):-
Code:
Start Menu\Programs\GIGABYTE Public:Start Menu\Programs\GIGABYTE Public
Start Menu\Programs\GIGABYTE\AutoGreen Public:Start Menu\Programs\GIGABYTE\AutoGreen Public
Start Menu\Programs\GIGABYTE\ET6 Public:Start Menu\Programs\GIGABYTE\ET6 Public
Start Menu\Programs\GIGABYTE\GHOST(6980) Public:Start Menu\Programs\GIGABYTE\GHOST(6980) Public
Quote:
GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge
May cause BSOD on Windows 7 systems - uninstall to test
Avast! antivirus is also contributing in BSOD-s. Please uninstall and replace with Microsoft Security Essentials at least to test.
Code:
Start Menu\Programs\avast! Free Antivirus Public:Start Menu\Programs\avast! Free Antivirus Public
avast! Uninstall Utility | Download aswClear for avast! Removal
Recommended antivirus program for Windows 7 based on stability compared to others:-
Microsoft Security Essentials - Free Antivirus for Windows
Malwarebytes - The Free version
Good and Free system security combination.
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.[/S]
Upload a screenshot of your hard disk using crystal disk info and summary tab using speccy:
Speccy - System Information - Free Download
CrystalDiskInfo - Software - Crystal Dew World
Screenshots and Files - Upload and Post in Seven Forums
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow
Full tutorial here:
SFC /SCANNOW Command - System File Checker
Run Disk Check on your hard disk for file system errors and bad sectors on it: [COLOR="Red"] Only carried out on C:\. Explorer repeatedly crashed during scan of D:\.[/COLOR]
Disk Check
Free up the start-up, nothing except the antivirus is usually needed.
Startup Programs - Change
Troubleshoot Application Conflicts by Performing a Clean Startup
Update the video card drivers in the following manner:
Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; NVIDIA and restart the system. Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper
Download link and stabled version:
Download NVIDIA Forceware 306.23 WHQL Vista 64 - FileHippo.com
*Report if there is any improvement.
Run a full scan with both (separately) once downloaded, installed and updated.
Run Memtest. I'll carry this out tomorrow evening.
Things do seem better since updating my GFX drivers though.
[FONT="Lucida Console"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {66724fc8, 2, 1, fffff88005c06f53}
Probably caused by : hardware ( USBPORT!USBPORT_EndpointFromHandle+1f )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000066724fc8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88005c06f53, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000fcc5100
GetUlongFromAddress: unable to read from fffff8000fcc51c0
0000000066724fc8 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_EndpointFromHandle+1f
fffff880`05c06f53 4550 push r8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: ArmA2OA.exe
TAG_NOT_DEFINED_c000000f: FFFFF88003571FB0
TRAP_FRAME: fffff88003571cb0 -- (.trap 0xfffff88003571cb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000013d600 rbx=0000000000000000 rcx=fffffa800ce5b0f0
rdx=0000000066725045 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005c06f53 rsp=fffff88003571e40 rbp=fffffa800cd17620
r8=0000000066725045 r9=00000000ffffffff r10=fffffa800ba2a1a0
r11=fffffa800ba2a1a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
USBPORT!USBPORT_EndpointFromHandle+0x1f:
fffff880`05c06f53 4550 push r8
Resetting default scope
MISALIGNED_IP:
USBPORT!USBPORT_EndpointFromHandle+1f
fffff880`05c06f53 4550 push r8
LAST_CONTROL_TRANSFER: from fffff8000fa95569 to fffff8000fa95fc0
STACK_TEXT:
fffff880`03571b68 fffff800`0fa95569 : 00000000`0000000a 00000000`66724fc8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03571b70 fffff800`0fa941e0 : fffffa80`0ba2a1a0 fffff880`03571cb8 fffff880`03571cb8 fffffa80`0ba2a050 : nt!KiBugCheckDispatch+0x69
fffff880`03571cb0 fffff880`05c06f53 : fffffa80`0ba2a1a0 00000000`00000000 fffffa80`0ba2a050 00000000`ffffffff : nt!KiPageFault+0x260
fffff880`03571e40 fffff880`05c11c7f : fffffa80`0ba2a050 fffffa80`0cef7ad0 fffffa80`0cd16010 fffffa80`0ba2a1a0 : USBPORT!USBPORT_EndpointFromHandle+0x1f
fffff880`03571e70 fffff880`05c02f89 : fffffa80`0ba2a050 00000000`00000000 fffffa80`0ba2ad02 fffffa80`0ba2ad28 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x6f
fffff880`03571ed0 fffff800`0faa06ec : fffff880`03542180 fffffa80`0ba2ad28 fffffa80`0ba2ad40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`03571f00 fffff800`0fa99105 : 00000000`00000000 fffffa80`0e7a5b50 00000000`00000000 fffff880`05c02db0 : nt!KiRetireDpcList+0x1bc
fffff880`03571fb0 fffff800`0fa98f1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`04c5eaa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_EndpointFromHandle+1f
fffff880`05c06f53 4550 push r8
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: USBPORT!USBPORT_EndpointFromHandle+1f
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------[/FONT]