Navigation section

Windows 7 Been gettin BSOD while now( since couple days before new years). Please help.

C

caisa

New Member
Joined
Jan 13, 2012
Messages
42
Last week of 2011 been getting stop errors ending in 1f, now it seems to be 3b. My os is now installed fresh for about a week. I need to know if I have to buy new hardware and which one. Thank you.
 


Solution
Trouble
You need to run this Link Removed (get the correct version for your architecture).
Since you formatted you will likely need to reinstall your chipset driver ASUSTeK Computer Inc. - Motherboards- ASUS P5QC
If blue screens persist please;
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using...
Sort by date Sort by votes
I have attached 2 file from crashed last night.
Trouble said:
We are still looking at "memory_corruption"
DUMP SUMMARY:
Code: 
BugCheck 3B, {c000001d, fffff960001576c8, fffff88007ca4620, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
And
Code: 
BugCheck 50, {ffffffffdb010c5d, 1, fffff9600024b750, 2}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
Will you please;
1. Clean up your system disk, either by using the built in Disk Cleanup Utility or a third party program that you like. (I like Ccleaner by Piriform for such tasks)
2. Defrag you system disk at least twice rebooting between using the built in disk defrag utility.
3. Perform a check of you system disk by using the built in Check Disk utility. Launch and elevated command prompt and type chkdsk C: /R and hit enter, answer yes "Y" to the prompt and reboot.
4. Perform a check of your OS files using the built in System File Checker uitility. Launch an elevated command prompt and type sfc /scannow
If you are using any USB drive as a ReadyBoost drive unplug it or just remove the ReadyBoost option from the drive's properties.
Let us know the results
Randy
Click to expand...
 


Attachments

Upvote 0 Downvote
You have not reported as to the results of having run the System File Checker or the Check Disk utilities. Did either or both report any issues?
RECENT DUMP:
Blames your Nvidia Graphics Driver;
Code: 
BugCheck D1, {fffff8800f2ddcac, 2, 8, fffff8800f2ddcac}
Unable to load image   [COLOR=#ff0000][U][B]nvlddmkm.sys[/B][/U][/COLOR]  , Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
  [COLOR=#ff0000][U][B]Probably caused by : nvlddmkm.sys[/B][/U][/COLOR]   ( nvlddmkm+2fcac )

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: fffff8800f2ddcac, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8800f2ddcac, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310f100
 fffff8800f2ddcac 
CURRENT_IRQL:  2
FAULTING_IP: 
  [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]  +2fcac
fffff880`0f2ddcac ??              ???
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff8800504f6d0 -- (.trap 0xfffff8800504f6d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80060f0001 rbx=0000000000000000 rcx=fffffa80051dc000
rdx=fffff8800504f940 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f2ddcac rsp=fffff8800504f868 rbp=fffffa80060df000
 r8=fffff880045116d0  r9=0000000000000000 r10=0000000000003000
r11=fffffa80060dfa58 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
  [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]  +0x2fcac:
fffff880`0f2ddcac ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002edc1e9 to fffff80002edcc40
FAILED_INSTRUCTION_ADDRESS: 
  [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]  +2fcac
fffff880`0f2ddcac ??              ???
STACK_TEXT:  
fffff880`0504f588 fffff800`02edc1e9 : 00000000`0000000a fffff880`0f2ddcac 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0504f590 fffff800`02edae60 : fffffa80`051dc000 fffff880`0504f940 fffffa80`05e2cc70 fffffa80`060cd000 : nt!KiBugCheckDispatch+0x69
fffff880`0504f6d0 fffff880`0f2ddcac : fffff880`0f42398a fffffa80`04999820 fffffa80`060cd000 fffffa80`00000002 : nt![COLOR=#ff0000][U][B]KiPageFault[/B][/U][/COLOR]+0x260
fffff880`0504f868 fffff880`0f42398a : fffffa80`04999820 fffffa80`060cd000 fffffa80`00000002 00000000`00000000 : nvlddmkm+0x2fcac
fffff880`0504f870 fffffa80`04999820 : fffffa80`060cd000 fffffa80`00000002 00000000`00000000 00000000`00000000 :  [B] [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR][/B]  +0x17598a
fffff880`0504f878 fffffa80`060cd000 : fffffa80`00000002 00000000`00000000 00000000`00000000 fffff880`0440d57e : 0xfffffa80`04999820
fffff880`0504f880 fffffa80`00000002 : 00000000`00000000 00000000`00000000 fffff880`0440d57e fffffa80`060f1000 : 0xfffffa80`060cd000
fffff880`0504f888 00000000`00000000 : 00000000`00000000 fffff880`0440d57e fffffa80`060f1000 fffffa80`060cd000 : 0xfffffa80`00000002
STACK_COMMAND:  kb
FOLLOWUP_IP: 
  [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]  +2fcac
fffff880`0f2ddcac ??              ???
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:[B]  [COLOR=#ff0000][U]nvlddmkm[/U][/COLOR][/B]+2fcac
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][U][B]nvlddmkm.sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_[COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]+2fcac
BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_[COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]+2fcac
Followup: MachineOwner
I have seen much in the way of frustration and little in the way of actual solutions with various attempts at resolving this particular Blue Screen. Some have reported solving the problems by updating the Nvidia Driver, while others have reported success in resorting to an early version of the Nvidia Driver. I suppose there is a possibility of driver corruption here so which ever option you choose to pursue I would suggest using DriverSweeper to remove any remnants of the current installation.

SECOND DUMP:
Blaming Memory Corruption (Again);
Code: 
BugCheck 50, {fffff88005a5c455, 1, fffff9600012e958, 0}
Could not read faulting driver name
[COLOR=#ff0000][U][B]Probably caused by :    memory_corruption[/B][/U][/COLOR]       
Followup:      [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR] 
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88005a5c455, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff9600012e958, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c0100
 fffff88005a5c455 
FAULTING_IP: 
win32k!NtUserRedrawWindow+4c
fffff960`0012e958 c853d6fe        enter   0D653h,0FEh
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  [U][I][B]uTorrent.exe[/B][/I][/U]
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88005a69a10 -- (.trap 0xfffff88005a69a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c3af6c20 rbx=0000000000000000 rcx=0000000000040260
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600012e958 rsp=fffff88005a69ba0 rbp=fffff88005a69ca0
 r8=0000000000000000  r9=0000000000000005 r10=fffff9600012e90c
r11=fffff900c3af6c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
win32k!NtUserRedrawWindow+0x4c:
fffff960`0012e958 c853d6fe        enter   0D653h,0FEh
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002e399fc to fffff80002e8dc40
STACK_TEXT:  
fffff880`05a698a8 fffff800`02e399fc : 00000000`00000050 fffff880`05a5c455 00000000`00000001 fffff880`05a69a10 : nt!KeBugCheckEx
fffff880`05a698b0 fffff800`02e8bd6e : 00000000`00000001 fffff880`05a5c455 fffff900`c062b000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`05a69a10 fffff960`0012e958 : 00000000`7297b184 00000000`7efdb000 fffff880`05a69ca0 fffff800`02e9785a : nt!Ki[COLOR=#ff0000][U][B]PageFault[/B][/U][/COLOR]+0x16e
fffff880`05a69ba0 fffff800`02e8ced3 : fffffa80`03e64660 00000000`0036ec98 00000000`007d2230 00000000`00000020 : win32k!NtUserRedrawWindow+0x4c
fffff880`05a69c20 00000000`72952e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72952e09
STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    fffff9600012e958 - win32k!NtUserRedrawWindow+4c
    [ e8:c8 ]
1 error : !win32k (fffff9600012e958)
MODULE_NAME:     [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]  
  IMAGE_NAME:        [COLOR=#ff0000][B][U]memory_corruption[/U][/B][/COLOR]
FOLLOWUP_NAME:    [COLOR=#ff0000][B][U]memory_corruption[/U][/B][/COLOR]    
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
FAILURE_BUCKET_ID:  X64_  [COLOR=#ff0000][B][U]MEMORY_CORRUPTION[/U][/B][/COLOR]  _ONE_BIT
BUCKET_ID:  X64_  [COLOR=#ff0000][B][U]MEMORY_CORRUPTION[/U][/B][/COLOR]  _ONE_BIT
Followup:   [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
Update this driver
L1E62x64.sys 12/2/2009 Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller from here Link Removed
Additionally since it seems that you like using uTorrent please grab this program (get the correct version for your architecture) from here Microsoft Standalone System Sweeper Beta | Microsoft Connect and a blank CD. Double click the program and it will build a bootable CD for you that you can then use to boot your system (set BIOS to boot CD/DVD first boot device) and run a Full system scan.
 


Upvote 0 Downvote
Disk scan result: disk is clean. I attached a picture of the other scan result. An will finish the remaining steps right now.

Trouble said:
You have not reported as to the results of having run the System File Checker or the Check Disk utilities. Did either or both report any issues?
RECENT DUMP:
Blames your Nvidia Graphics Driver;
Code: 
BugCheck D1, {fffff8800f2ddcac, 2, 8, fffff8800f2ddcac}
Unable to load image   [COLOR=#ff0000][U][B]nvlddmkm.sys[/B][/U][/COLOR]  , Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
  [COLOR=#ff0000][U][B]Probably caused by : nvlddmkm.sys[/B][/U][/COLOR]   ( nvlddmkm+2fcac )

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: fffff8800f2ddcac, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8800f2ddcac, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310f100
 fffff8800f2ddcac 
CURRENT_IRQL:  2
FAULTING_IP: 
  [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]  +2fcac
fffff880`0f2ddcac ??              ???
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff8800504f6d0 -- (.trap 0xfffff8800504f6d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80060f0001 rbx=0000000000000000 rcx=fffffa80051dc000
rdx=fffff8800504f940 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f2ddcac rsp=fffff8800504f868 rbp=fffffa80060df000
 r8=fffff880045116d0  r9=0000000000000000 r10=0000000000003000
r11=fffffa80060dfa58 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
  [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]  +0x2fcac:
fffff880`0f2ddcac ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002edc1e9 to fffff80002edcc40
FAILED_INSTRUCTION_ADDRESS: 
  [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]  +2fcac
fffff880`0f2ddcac ??              ???
STACK_TEXT:  
fffff880`0504f588 fffff800`02edc1e9 : 00000000`0000000a fffff880`0f2ddcac 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0504f590 fffff800`02edae60 : fffffa80`051dc000 fffff880`0504f940 fffffa80`05e2cc70 fffffa80`060cd000 : nt!KiBugCheckDispatch+0x69
fffff880`0504f6d0 fffff880`0f2ddcac : fffff880`0f42398a fffffa80`04999820 fffffa80`060cd000 fffffa80`00000002 : nt![COLOR=#ff0000][U][B]KiPageFault[/B][/U][/COLOR]+0x260
fffff880`0504f868 fffff880`0f42398a : fffffa80`04999820 fffffa80`060cd000 fffffa80`00000002 00000000`00000000 : nvlddmkm+0x2fcac
fffff880`0504f870 fffffa80`04999820 : fffffa80`060cd000 fffffa80`00000002 00000000`00000000 00000000`00000000 :  [B] [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR][/B]  +0x17598a
fffff880`0504f878 fffffa80`060cd000 : fffffa80`00000002 00000000`00000000 00000000`00000000 fffff880`0440d57e : 0xfffffa80`04999820
fffff880`0504f880 fffffa80`00000002 : 00000000`00000000 00000000`00000000 fffff880`0440d57e fffffa80`060f1000 : 0xfffffa80`060cd000
fffff880`0504f888 00000000`00000000 : 00000000`00000000 fffff880`0440d57e fffffa80`060f1000 fffffa80`060cd000 : 0xfffffa80`00000002
STACK_COMMAND:  kb
FOLLOWUP_IP: 
  [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]  +2fcac
fffff880`0f2ddcac ??              ???
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:[B]  [COLOR=#ff0000][U]nvlddmkm[/U][/COLOR][/B]+2fcac
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][U][B]nvlddmkm.sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_[COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]+2fcac
BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_[COLOR=#ff0000][U][B]nvlddmkm[/B][/U][/COLOR]+2fcac
Followup: MachineOwner
I have seen much in the way of frustration and little in the way of actual solutions with various attempts at resolving this particular Blue Screen. Some have reported solving the problems by updating the Nvidia Driver, while others have reported success in resorting to an early version of the Nvidia Driver. I suppose there is a possibility of driver corruption here so which ever option you choose to pursue I would suggest using DriverSweeper to remove any remnants of the current installation.

SECOND DUMP:
Blaming Memory Corruption (Again);
Code: 
BugCheck 50, {fffff88005a5c455, 1, fffff9600012e958, 0}
Could not read faulting driver name
[COLOR=#ff0000][U][B]Probably caused by :    memory_corruption[/B][/U][/COLOR]       
Followup:      [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR] 
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88005a5c455, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff9600012e958, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c0100
 fffff88005a5c455 
FAULTING_IP: 
win32k!NtUserRedrawWindow+4c
fffff960`0012e958 c853d6fe        enter   0D653h,0FEh
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  [U][I][B]uTorrent.exe[/B][/I][/U]
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88005a69a10 -- (.trap 0xfffff88005a69a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c3af6c20 rbx=0000000000000000 rcx=0000000000040260
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600012e958 rsp=fffff88005a69ba0 rbp=fffff88005a69ca0
 r8=0000000000000000  r9=0000000000000005 r10=fffff9600012e90c
r11=fffff900c3af6c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
win32k!NtUserRedrawWindow+0x4c:
fffff960`0012e958 c853d6fe        enter   0D653h,0FEh
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002e399fc to fffff80002e8dc40
STACK_TEXT:  
fffff880`05a698a8 fffff800`02e399fc : 00000000`00000050 fffff880`05a5c455 00000000`00000001 fffff880`05a69a10 : nt!KeBugCheckEx
fffff880`05a698b0 fffff800`02e8bd6e : 00000000`00000001 fffff880`05a5c455 fffff900`c062b000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`05a69a10 fffff960`0012e958 : 00000000`7297b184 00000000`7efdb000 fffff880`05a69ca0 fffff800`02e9785a : nt!Ki[COLOR=#ff0000][U][B]PageFault[/B][/U][/COLOR]+0x16e
fffff880`05a69ba0 fffff800`02e8ced3 : fffffa80`03e64660 00000000`0036ec98 00000000`007d2230 00000000`00000020 : win32k!NtUserRedrawWindow+0x4c
fffff880`05a69c20 00000000`72952e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72952e09
STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    fffff9600012e958 - win32k!NtUserRedrawWindow+4c
    [ e8:c8 ]
1 error : !win32k (fffff9600012e958)
MODULE_NAME:     [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]  
  IMAGE_NAME:        [COLOR=#ff0000][B][U]memory_corruption[/U][/B][/COLOR]
FOLLOWUP_NAME:    [COLOR=#ff0000][B][U]memory_corruption[/U][/B][/COLOR]    
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
FAILURE_BUCKET_ID:  X64_  [COLOR=#ff0000][B][U]MEMORY_CORRUPTION[/U][/B][/COLOR]  _ONE_BIT
BUCKET_ID:  X64_  [COLOR=#ff0000][B][U]MEMORY_CORRUPTION[/U][/B][/COLOR]  _ONE_BIT
Followup:   [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
Update this driver
L1E62x64.sys 12/2/2009 Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller from here Link Removed
Additionally since it seems that you like using uTorrent please grab this program (get the correct version for your architecture) from here Microsoft Standalone System Sweeper Beta | Microsoft Connect and a blank CD. Double click the program and it will build a bootable CD for you that you can then use to boot your system (set BIOS to boot CD/DVD first boot device) and run a Full system scan.
Click to expand...
 


Attachments

  • scan result.webp
    scan result.webp
    25.9 KB · Views: 322
Upvote 0 Downvote
OK, well that doesn't sound too good
Windows Resource Protection found corrupt files but was unable to fix some of them
Click to expand...
you may need to check that CBS.log file and see if you can determine which files weren't fixed.
Additionally how about the Check Disk Log File.
Open event viewer, expand Windows Logs, right click Application and click find, type chkdsk for search parameters and hit enter.
 


Upvote 0 Downvote
I just crashed couple moments back too. Let me know If you'd like to see the files. Thanks Trouble.



Trouble said:
OK, well that doesn't sound too good you may need to check that CBS.log file and see if you can determine which files weren't fixed.Additionally how about the Check Disk Log File.Open event viewer, expand Windows Logs, right click Application and click find, type chkdsk for search parameters and hit enter.
Click to expand...
 


Attachments

Upvote 0 Downvote
You can of course attach any newer or more recent dump files and I will be happy to take a look and see what they might reveal, but you may be at the point where you might need to run Driver Verifier in order to actually find the specific offender.
This is not a step that I normally recommend as it can on occasion (although rarely) result in unintended consequences with can prevent you from getting back into windows without performing some sophisticated offline registry editing.
I refer you to this article by Link Removed - Invalid URL here Link Removed and let you decide if that is something you wish to attempt.
Regards
Randy
 


Upvote 0 Downvote
When you performed your testing with MemTest86 did you do so after leaving your computer off for a while (cold). IF not please do so, shut your computer down and leave it off for 15 minutes or so and then boot from the MemTest86 CD and run the test again five to seven passes.
Download, install and update all three to the most recent signature definition;
Free versions......
MalwareBytes
SuperAntiSpyware
Spybot Search and Destroy (pay close attention during the install do not install Tea Timer)
After updating all three to the latest signature definitions reboot into Safe Mode and run all three simultaneously. Remove anything found.
 


Upvote 0 Downvote
Trouble said:
When you performed your testing with MemTest86 did you do so after leaving your computer off for a while (cold). IF not please do so, shut your computer down and leave it off for 15 minutes or so and then boot from the MemTest86 CD and run the test again five to seven passes.
Download, install and update all three to the most recent signature definition;
Free versions......
MalwareBytes
SuperAntiSpyware
Spybot Search and Destroy (pay close attention during the install do not install Tea Timer)
After updating all three to the latest signature definitions reboot into Safe Mode and run all three simultaneously. Remove anything found.
Click to expand...


I did it cold too. I did the scans and nothing. This is second time i'm writing this message as I was having a CRASH 5 MIN AGO.
Right now i'm using safe mode with networking. I attached the latest dumps. Probably all within 24 hours.


Why don't you want to answer my question I don't understand. Let me ask you again. If you don't know just say so.


I asked you before you do you think my back usb ports will not charge my ps3 controller anymore. The front ones work just fine. Don't you think that is a red flag or some kind of clue about my problems?


Let me be clear. The ps3 controller charges just fine in front usb and other pc's as well.


The back usb ports handle my ext hdd a wd elements 2.5TB. the mouse usb receiver .


Also the ps3 official headset charges very screwy in the back usb as well. The red led doesn't flash at set interversal (ie every 2 seconds on and off) which is the normal way.


Instead is stays on indicating is fully charged and then after some time goes on and so on.




Thanks you.
 


Attachments

Upvote 0 Downvote
Trouble are you in trouble? :) I did some changes to my pc , like try to straight a bent pin on my mobo socket. Seems to be working way better than before. I get a random crash once in a while. I'd like you to tell me if it's something new or same old story. Please have a look. I'm using 7zip now and it doesn't seem to let me upload. So i uploaded just the crash file.



caisa said:
I did it cold too. I did the scans and nothing. This is second time i'm writing this message as I was having a CRASH 5 MIN AGO.
Right now i'm using safe mode with networking. I attached the latest dumps. Probably all within 24 hours.


Why don't you want to answer my question I don't understand. Let me ask you again. If you don't know just say so.


I asked you before you do you think my back usb ports will not charge my ps3 controller anymore. The front ones work just fine. Don't you think that is a red flag or some kind of clue about my problems?


Let me be clear. The ps3 controller charges just fine in front usb and other pc's as well.


The back usb ports handle my ext hdd a wd elements 2.5TB. the mouse usb receiver .


Also the ps3 official headset charges very screwy in the back usb as well. The red led doesn't flash at set interversal (ie every 2 seconds on and off) which is the normal way.


Instead is stays on indicating is fully charged and then after some time goes on and so on.




Thanks you.
Click to expand...
 


Attachments

Upvote 0 Downvote
I Fixed it :) . Finally !!!! I would like to think TROUBLE for all the trouble he went trough to help me and also I would like to thank my pants who supported my balls throughout the years . Thank you.
 


Upvote 0 Downvote
You must log in or register to reply here.
Back
Top