Windows 7 random crashes 0x00000004e and plenty others

kickasspeanut · Jan 17, 2014

Hey my computer has been bsoding quite a lot recently 3 times today and about 50 times in the past 2 months.
I have brand new memory in my computer as my previous memory died. My spec's are listed in my profile, Since I ran SF diagnostics and put everything in a zip but i deleted like 40 of the .dmp files since they where from last year.

kickasspeanut · Jan 17, 2014

happened again dmp attached

kickasspeanut · Jan 18, 2014

Bump happened again, can someone help?

kickasspeanut · Jan 18, 2014

Happened this morning again, They're usually all bug check strings.

koolkat77 · Jan 19, 2014

Your BSOD seem to be caused by : cFosSpeed - The Internet Accelerator

Please remove this software.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Do some http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html

Install all updates and Service Pack 1: Learn how to install Windows 7 Service Pack 1 (SP1)

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Let us know the results.

Code:

Loading Dump File [C:\Users\Usra\Downloads\SF_19-01-2014keepshappening\SF_19-01-2014\011914-12667-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
[COLOR="Blue"]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/COLOR]
Machine Name:
Kernel base = 0xfffff800`04e17000 PsLoadedModuleList = 0xfffff800`05054e50
Debug session time: Sun Jan 19 02:46:49.169 2014 (UTC + 6:00)
System Uptime: 0 days 13:31:53.577
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80004e8ed6f, fffff88003218528, fffff88003217d80}

*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by : cfosspeed6.sys ( cfosspeed6+135819 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80004e8ed6f, The address that the exception occurred at
Arg3: fffff88003218528, Exception Record Address
Arg4: fffff88003217d80, Context Record Address

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!KiSwapContext+f
fffff800`04e8ed6f 0f29742430      movaps  xmmword ptr [rsp+30h],xmm6

EXCEPTION_RECORD:  fffff88003218528 -- (.exr 0xfffff88003218528)
ExceptionAddress: fffff80004e8ed6f (nt!KiSwapContext+0x000000000000000f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff88003217d80 -- (.cxr 0xfffff88003217d80)
rax=fffff88003218868 rbx=fffffa800b33e840 rcx=fffffa800b33e840
rdx=fffff8000500fc40 rsi=fffffa800b33e900 rdi=fffff80005001e80
rip=fffff80004e8ed6f rsp=fffff88003218768 rbp=fffffa800b33e840
 r8=fffffa80068e5850  r9=0000000000000000 r10=fffff80004e17000
r11=fffffa800b33e900 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010292
nt!KiSwapContext+0xf:
fffff800`04e8ed6f 0f29742430      movaps  xmmword ptr [rsp+30h],xmm6 ss:0018:fffff880`03218798=8956d10680f8ffff0000000000000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800050bf0e0
GetUlongFromAddress: unable to read from fffff800050bf198
 0000000000000000 Nonpaged pool

FOLLOWUP_IP: 
cfosspeed6+135819
fffff880`06d8e819 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80004e90052 to fffff80004e8ed6f

STACK_TEXT:  
fffff880`03218768 fffff800`04e90052 : fffffa80`0b33e840 fffffa80`0b33e840 fffffa80`00000000 fffffa80`00000000 : nt!KiSwapContext+0xf
fffff880`032188a8 fffff800`04e8c54b : fffff800`04e8c54b fffff880`06dcf600 fffff880`000000d5 fffffa80`000000d5 : nt!KiCommitThreadWait+0x1d2
fffff880`03218938 fffff880`06d8e819 : 1fffffff`00000003 fffffa80`0d7c6280 fffff880`00000001 00000000`00000000 : nt!KeWaitForMultipleObjects+0x271
fffff880`03218be8 1fffffff`00000003 : fffffa80`0d7c6280 fffff880`00000001 00000000`00000000 00000000`00000000 : cfosspeed6+0x135819
fffff880`03218bf0 fffffa80`0d7c6280 : fffff880`00000001 00000000`00000000 00000000`00000000 fffff880`03218c00 : 0x1fffffff`00000003
fffff880`03218bf8 fffff880`00000001 : 00000000`00000000 00000000`00000000 fffff880`03218c00 fffff880`03218c58 : 0xfffffa80`0d7c6280
fffff880`03218c00 00000000`00000000 : 00000000`00000000 fffff880`03218c00 fffff880`03218c58 fffffa80`0b33e948 : 0xfffff880`00000001


SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cfosspeed6+135819

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cfosspeed6

IMAGE_NAME:  cfosspeed6.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e11bdbb

STACK_COMMAND:  .cxr 0xfffff88003217d80 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_cfosspeed6+135819

BUCKET_ID:  X64_0x7E_cfosspeed6+135819

Followup: MachineOwner
---------

0: kd> lmvm cfosspeed6
start             end                 module name
fffff880`06c59000 fffff880`06df6000   cfosspeed6 T (no symbols)           
    Loaded symbol image file: cfosspeed6.sys
    Image path: cfosspeed6.sys
    Image name: cfosspeed6.sys
    Timestamp:        Mon Jul 04 19:18:51 2011 (4E11BDBB)
    CheckSum:         0019A733
    ImageSize:        0019D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

kickasspeanut · Jan 19, 2014

I've uninstalled Xfast LAN aka cfosspeed and I'll see if that proves to be the fix, if not i'll run a check on my hdd as its getting a bit old and might be the issue. Thanks for the help so far!

kickasspeanut · Jan 19, 2014

It seems removing Xfast Lan has not fixed the issue, DMP file attached, I will install service pack 1 and other updates and run a hard drive test and report my findings.

koolkat77 · Jan 19, 2014

another driver to update: Driver Reference Table - iusb3xhc.sys

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\xfastremoved\SF_19-01-2014\011914-11965-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`04e17000 PsLoadedModuleList = 0xfffff800`05054e50
Debug session time: Sun Jan 19 18:12:26.183 2014 (UTC + 6:00)
System Uptime: 0 days 5:43:05.417
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {22af22d10, 2, 1, fffff88011ef4d9b}

*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : hardware ( iusb3xhc+48d9b )

Followup: MachineOwner
---------

0: 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: 000000022af22d10, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88011ef4d9b, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800050bf0e0
GetUlongFromAddress: unable to read from fffff800050bf198
 000000022af22d10 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
iusb3xhc+48d9b
fffff880`11ef4d9b 2003            and     byte ptr [rbx],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  chrome.exe

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000ba2ad0 -- (.trap 0xfffff80000ba2ad0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa800af38920
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011ef4d9b rsp=fffff80000ba2c60 rbp=fffffa800a7d1000
 r8=0000000000000000  r9=0000000000000000 r10=fffff88011f27060
r11=fffff80000ba2c98 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
iusb3xhc+0x48d9b:
fffff880`11ef4d9b 2003            and     byte ptr [rbx],al ds:00000000`00000000=??
Resetting default scope

MISALIGNED_IP: 
iusb3xhc+48d9b
fffff880`11ef4d9b 2003            and     byte ptr [rbx],al

LAST_CONTROL_TRANSFER:  from fffff80004e88469 to fffff80004e88f00

STACK_TEXT:  
fffff800`00ba2988 fffff800`04e88469 : 00000000`0000000a 00000002`2af22d10 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba2990 fffff800`04e870e0 : 00000000`00000000 00000002`2af22d10 fffffa80`0a55cb50 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2ad0 fffff880`11ef4d9b : 00000002`2af22d10 fffff880`11ee3773 fffff880`11f17da0 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00ba2c60 00000002`2af22d10 : fffff880`11ee3773 fffff880`11f17da0 00000000`00000000 fffff880`11f26e00 : iusb3xhc+0x48d9b
fffff800`00ba2c68 fffff880`11ee3773 : fffff880`11f17da0 00000000`00000000 fffff880`11f26e00 00000000`00000000 : 0x00000002`2af22d10
fffff800`00ba2c70 fffff880`11f17da0 : 00000000`00000000 fffff880`11f26e00 00000000`00000000 00000000`00000000 : iusb3xhc+0x37773
fffff800`00ba2c78 00000000`00000000 : fffff880`11f26e00 00000000`00000000 00000000`00000000 fffff880`11ed9d75 : iusb3xhc+0x6bda0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iusb3xhc+48d9b
fffff880`11ef4d9b 2003            and     byte ptr [rbx],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  iusb3xhc+48d9b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_iusb3xhc.sys

BUCKET_ID:  X64_IP_MISALIGNED_iusb3xhc.sys

Followup: MachineOwner
---------

Code:

0: kd> lmvm iusb3xhc
start             end                 module name
fffff880`11eac000 fffff880`11f70000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Fri Jan 27 15:35:28 2012 (4F226FE0)
    CheckSum:         000C193B
    ImageSize:        000C4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

kickasspeanut · Jan 20, 2014

Computer now has service pack 1 and is full up to date but blue screens still persist. dmp attached

koolkat77 · Jan 20, 2014

Have you done these?

koolkat77 said:
Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Do some http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Also test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The 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.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

kickasspeanut · Jan 21, 2014

happened again, I'll put memtest on a usb and test my ram when I go to bed tonight. Will post results.

kickasspeanut · Jan 21, 2014

Ran memtest for 13 passes and no errors occurred ill do a diskcheck on my HDD's

koolkat77 · Jan 21, 2014

You haven't completed allot of steps that were mentioned earlier.

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Code:

Sidebar	%programfiles%\windows sidebar\sidebar.exe /autorun	NT AUTHORITY\LOCAL SERVICE	HKU\S-1-5-19\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Sidebar	%programfiles%\windows sidebar\sidebar.exe /autorun	NT AUTHORITY\NETWORK SERVICE	HKU\S-1-5-20\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
ASRockXTU		ELMO\Penis	HKU\S-1-5-21-1971409505-3046368944-4214636127-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
zASRockInstantBoot		ELMO\Penis	HKU\S-1-5-21-1971409505-3046368944-4214636127-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
AdobeBridge		ELMO\Penis	HKU\S-1-5-21-1971409505-3046368944-4214636127-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
puush	c:\program files (x86)\puush\puush.exe	ELMO\Penis	HKU\S-1-5-21-1971409505-3046368944-4214636127-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
DAEMON Tools Pro Agent	"c:\program files (x86)\daemon tools pro\dtagent.exe" -autorun	ELMO\Penis	HKU\S-1-5-21-1971409505-3046368944-4214636127-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Sidebar	%programfiles%\windows sidebar\sidebar.exe /autorun	ELMO\UpdatusUser	HKU\S-1-5-21-1971409505-3046368944-4214636127-1007\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
ASRockXTU		ELMO\UpdatusUser	HKU\S-1-5-21-1971409505-3046368944-4214636127-1007\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
zASRockInstantBoot		ELMO\UpdatusUser	HKU\S-1-5-21-1971409505-3046368944-4214636127-1007\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
AdobeBridge		ELMO\UpdatusUser	HKU\S-1-5-21-1971409505-3046368944-4214636127-1007\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
puush	c:\program files (x86)\puush\puush.exe	ELMO\UpdatusUser	HKU\S-1-5-21-1971409505-3046368944-4214636127-1007\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
DAEMON Tools Pro Agent	"c:\program files (x86)\daemon tools pro\dtagent.exe" -autorun	ELMO\UpdatusUser	HKU\S-1-5-21-1971409505-3046368944-4214636127-1007\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
IgfxTray	c:\windows\system32\igfxtray.exe	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HotKeysCmds	c:\windows\system32\hkcmd.exe	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Persistence	c:\windows\system32\igfxpers.exe	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
VIRTU MVP	c:\program files\lucidlogix technologies\virtu mvp\mvpcontrolpanel.exe /hide	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
AdobeAAMUpdater-1.0	"c:\program files (x86)\common files\adobe\oobe\pdapp\uwa\updaterstartuputility.exe"	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
MSC	"c:\program files\microsoft security client\msseces.exe" -hide -runkey	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Start WingMan Profiler	c:\program files\logitech\gaming software\lwemon.exe /noui	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Launch LCore	c:\program files\logitech gaming software\lcore.exe /minimized	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Nvtmru	"c:\program files (x86)\nvidia corporation\nvidia update core\nvtmru.exe"	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
ShadowPlay	c:\windows\system32\rundll32.exe c:\windows\system32\nvspcap64.dll,shadowplayonsystemstart	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Code:

Start Menu\Programs\DAEMON Tools Pro	Public:Start Menu\Programs\DAEMON Tools Pro	Public

Daemon Tools/Alchohol is known to cause BSODs:
How to remove sptd.sys from system
Registry and SPTD problems | DAEMON Pro Help

Code:

Start Menu\Programs\IObit Uninstaller	Public:Start Menu\Programs\IObit Uninstaller	Public

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

Code:

Start Menu\Programs\MSI Afterburner	ELMO\Penis:Start Menu\Programs\MSI Afterburner	ELMO\Penis
Start Menu\Programs\MSI Afterburner\SDK	ELMO\Penis:Start Menu\Programs\MSI Afterburner\SDK	ELMO\Penis

kickasspeanut · Jan 21, 2014

I've uninstalled Daemon tools reduced items on startup, the only thing left you've listed is a clean boot.

kickasspeanut · Jan 23, 2014

Still happening can someone please solve this, I wasn't having bluescreens for awhile but noticed my memory was set to half speed, once i set it back to proper speed and fixed the timings this started happening again, But the memory tests gave no errors or blue screens

kickasspeanut · Jan 23, 2014

Happened again dmp attached

Britton30 · Jan 23, 2014

Do all KoolKat has posted, installing SP1 is important. It may be you have a memory issue too.

RAM (memory) test:

This will require memtest on a bootable CD or USB stick.
RAM - Test with Memtest86+

kickasspeanut · Jan 23, 2014

I have installed sp1 and all updates from the update centre and I ran memtest for 13 passes with no errors

Britton30 · Jan 23, 2014

There's several more steps to do too, let us know if you did them, they are all designed to help you. We can't if you don't do them.

Windows 7 random crashes 0x00000004e and plenty others

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

R.I.P. 7/09/2014

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

R.I.P. 7/09/2014

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer