BSOD happened. Even when idling :S

[digigon247]

Window 7 home premium 64bit, random Blue screen at time and even idling. :S

 

[koolkat77]

Welcome

There is only one dump of 8-20-2012.
Did you get any BSoDs after that?

Seeing the one dump I would suggest you to uninstall ESET and use MSE (At least to test)
→ Microsoft Security Essentials - Free Antivirus for Windows

Run Disk Check on your hard disk for file system errors and bad sectors on it
→ http://www.sevenforums.com/tutorials/433-disk-check.html

Also look for an update on your BIOS version:

BIOS Version/Date	INSYDE V1.16, [COLOR="Blue"]8/9/2010[/COLOR]

Observe if your system is stable.

If not, Take memtest. Run for 8 passes.
→ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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 Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffb5801eba8bb, 0, fffff80003ed0d7f, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )

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

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

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: fffffb5801eba8bb, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003ed0d7f, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80004116100
 fffffb5801eba8bb 

FAULTING_IP: 
nt!MiAgeWorkingSet+425
fffff800`03ed0d7f 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  SSUService.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880037e77c0 -- (.trap 0xfffff880037e77c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=fffff680003b8148
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ed0d7f rsp=fffff880037e7950 rbp=00000000003b814e
 r8=0000000000000001  r9=fffffa8007169ec8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiAgeWorkingSet+0x425:
fffff800`03ed0d7f 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh] ds:0007:00000000`0000001b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003e8de97 to fffff80003ee71c0

STACK_TEXT:  
fffff880`037e7658 fffff800`03e8de97 : 00000000`00000050 fffffb58`01eba8bb 00000000`00000000 fffff880`037e77c0 : nt!KeBugCheckEx
fffff880`037e7660 fffff800`03ee52ee : 00000000`00000000 fffffb58`01eba8bb 00000000`00000000 92704800`a3e2e005 : nt! ?? ::FNODOBFM::`string'+0x43cd1
fffff880`037e77c0 fffff800`03ed0d7f : 00000003`00000000 92600000`6dc2d867 00000000`00000000 00000000`00000126 : nt!KiPageFault+0x16e
fffff880`037e7950 fffff800`03f5f4b5 : fffffa80`07169ec8 fffff880`00000001 00000000`00000001 fffff880`037e7bb0 : nt!MiAgeWorkingSet+0x425
fffff880`037e7b00 fffff800`03ed10d6 : 00000000`000007e5 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4cd46
fffff880`037e7b80 fffff800`03ed158b : 00000000`00000008 fffff880`037e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`037e7bd0 fffff800`0417de6a : fffffa80`03cef850 00000000`00000080 fffffa80`03cd1040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`037e7d40 fffff800`03ed7ec6 : fffff880`009b1180 fffffa80`03cef850 fffff880`009bc0c0 efdfffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`037e7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+425
fffff800`03ed0d7f 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+425

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425

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

Let us know the results

 

[digigon247]

Welcome

There is only one dump of 8-20-2012.
Did you get any BSoDs after that?

Seeing the one dump I would suggest you to uninstall ESET and use MSE (At least to test)
→ Microsoft Security Essentials - Free Antivirus for Windows

Run Disk Check on your hard disk for file system errors and bad sectors on it
→ http://www.sevenforums.com/tutorials/433-disk-check.html

Also look for an update on your BIOS version:

BIOS Version/Date	INSYDE V1.16, [COLOR="Blue"]8/9/2010[/COLOR]

Observe if your system is stable.

If not, Take memtest. Run for 8 passes.
→ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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 Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffb5801eba8bb, 0, fffff80003ed0d7f, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )

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

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

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: fffffb5801eba8bb, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003ed0d7f, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80004116100
 fffffb5801eba8bb 

FAULTING_IP: 
nt!MiAgeWorkingSet+425
fffff800`03ed0d7f 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  SSUService.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880037e77c0 -- (.trap 0xfffff880037e77c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=fffff680003b8148
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ed0d7f rsp=fffff880037e7950 rbp=00000000003b814e
 r8=0000000000000001  r9=fffffa8007169ec8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiAgeWorkingSet+0x425:
fffff800`03ed0d7f 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh] ds:0007:00000000`0000001b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003e8de97 to fffff80003ee71c0

STACK_TEXT:  
fffff880`037e7658 fffff800`03e8de97 : 00000000`00000050 fffffb58`01eba8bb 00000000`00000000 fffff880`037e77c0 : nt!KeBugCheckEx
fffff880`037e7660 fffff800`03ee52ee : 00000000`00000000 fffffb58`01eba8bb 00000000`00000000 92704800`a3e2e005 : nt! ?? ::FNODOBFM::`string'+0x43cd1
fffff880`037e77c0 fffff800`03ed0d7f : 00000003`00000000 92600000`6dc2d867 00000000`00000000 00000000`00000126 : nt!KiPageFault+0x16e
fffff880`037e7950 fffff800`03f5f4b5 : fffffa80`07169ec8 fffff880`00000001 00000000`00000001 fffff880`037e7bb0 : nt!MiAgeWorkingSet+0x425
fffff880`037e7b00 fffff800`03ed10d6 : 00000000`000007e5 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4cd46
fffff880`037e7b80 fffff800`03ed158b : 00000000`00000008 fffff880`037e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`037e7bd0 fffff800`0417de6a : fffffa80`03cef850 00000000`00000080 fffffa80`03cd1040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`037e7d40 fffff800`03ed7ec6 : fffff880`009b1180 fffffa80`03cef850 fffff880`009bc0c0 efdfffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`037e7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+425
fffff800`03ed0d7f 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+425

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425

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

Let us know the results

Thanks for responding back,

Actually i have alot of BSOD before this but i don't know why it only shows one. i think i have like 30+ since the beginning of 2011. but i never know this website existed.

anyway, i have installed the security essentials.
tried disk check and the image below appeared, i did the chkdsk /r like lastweek but it looks kinda fine i think. and ram also is ok.

for my laptop bios, i don't know where to find it. Laptop model Acer Aspire 5745G. Posted some image for you to look at. Hope this will help you get some idea whats going on with my laptop><

 

[koolkat77]

Click on Scan for and attempt recovery for bad sectors, deselect automatically fix file system errors

What were the results from memtest? If it's pending, start now and report back results

 

[digigon247]

Click on Scan for and attempt recovery for bad sectors, deselect automatically fix file system errors

What were the results from memtest? If it's pending, start now and report back results

This are the results after doing so.

 

[koolkat77]

3 passes only.
Well okay, observer your computer and let us know if there are more BSoDs

 

[digigon247]

3 passes only.
Well okay, observer your computer and let us know if there are more BSoDs

This just happened while i was doing my Uni assignment :S

 

[koolkat77]

Make a hard drive test from the hard drive manufacturers website

Hard drive test both short and long with
→ SeaTools for Windows

You may also go through these
→ Hard Drive Diagnostic Procedure

 

[digigon247]

Make a hard drive test from the hard drive manufacturers website

Hard drive test both short and long with
→ SeaTools for Windows

You may also go through these
→ Hard Drive Diagnostic Procedure

used the program and check my hard disk and everything is pass when i check. i used the blue screen view and saw that (image)

 

[koolkat77]

Did you take the long generic of seatools?

 

[digigon247]

Did you take the long generic of seatools?

It still pass. I just remember few years back i tried updating my bios.

 

[koolkat77]

OK, enable driver verifier
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[digigon247]

OK, enable driver verifier
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

It's just had a BSOD. so what do i do now?

 

[koolkat77]

Upload the dumps you got with verifier enabled.

 

[digigon247]

Upload the dumps you got with verifier enabled.

I'm assuming this is what you meant. I'm not sure

 

[koolkat77]

There is no dump
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

and your BIOS version is now of 2005?
how come?

BIOS Version/Date	INSYDE V1.19, 12/6/2005

 

[koolkat77]

Did you uninstall the things I listed in my post #2?

 

[digigon247]

There is no dump
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

and your BIOS version is now of 2005?
how come?

BIOS Version/Date	INSYDE V1.19, 12/6/2005

I tried updating it cause it was outdated right? v1.16 before. so i went and update it.