Windows 7: bsod 1st time

gangbang · 04 May 2010

i was reassembling my pc to check the hardware that causes bsod earlier. i found out that my fan controller "maybe" causes bsod . i removed my fan controller then logged to windows, and nothing happens. but after black-out (power interruption). for the first time bsod appears again.

can you please check what causes this bsod. thanks

heres the dump file i got.

Jonathan_King · 04 May 2010

Looks like bad RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\050410-25662-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
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e90e50
Debug session time: Tue May  4 21:40:52.717 2010 (GMT-4)
System Uptime: 0 days 0:14:24.044
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffb80059a5258, 0, fffff80002cf63e0, 7}


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

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

gangbang · 04 May 2010

ok i saw 6 errors on memtest. any advice to repair the error??? are my rams need to be replace ??

thanks

Jonathan_King · 04 May 2010

Errors = Bad RAM or bad motherboard slot. Try testing each stick separately, in each slot.

gangbang · 13 May 2010

another bsod

can u check it please thanks

heres the dump file

Jonathan_King · 13 May 2010

We already know the cause. It is either bad RAM or a bad motherboard slot. Test each stick individually. If you find a good stick, test it in the other slots.

That way you can determine if you need a new Mobo or RAM.

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\051310-21793-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
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Thu May 13 22:30:50.925 2010 (GMT-4)
System Uptime: 0 days 0:16:00.955
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002c516de, fffff88009987e40, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )

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

gangbang · 22 May 2010

hello

can you check this out???

thanks

zigzag3143 · 22 May 2010

Quote: Originally Posted by gangbang

hello

can you check this out???

thanks

Three guesses. Still Memory corruption. Have you run memtestx86 for at least 5 runs? what were the results?

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 22 21:53:53.634 2010 (GMT-4)
System Uptime: 0 days 0:01:04.055
BugCheck 50, {fffff6837f7e6a70, 0, fffff80002fd8e37, 5}
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )
BUGCHECK_STR: 0x50
PROCESS_NAME: spoolsv.exe

gangbang · 23 May 2010

will try that now, result later

thanks boss

gangbang · 23 May 2010

ok i just memtest it til test 8 nothing wrong. but i adjust the dram config at bios making xmp profile, 1.6v on dram voltage, it works perfect, well for now

any advice??? my i5 750 hits 77c when playing games is that ok

btw thanks

Windows 7: bsod 1st time

bsod 1st time problems?