Windows 7 x64 Crashed BSOD Help please!

you cannot afford to make assumptions

Yes I know, you're absolutely right.
I'm sorry, I was too tired from my work and all these stuffs.
Maybe I should rest for a while

you need to run your system exactly as you gave it to your repairer with only the peripherals they used, no matter how much you or your little bro likes your keyboard this is necessary for debugging and once you find the bluescreen cause(s) you can then revert to personalizing your system :)

I will replace the keyboard with the one that compatible with Win7 and see if the BSOD persist to eliminate 3rd Party Peripheral Hardware Issue just in case.

My Logitech mouse and Samsung SyncMaster Monitor are the only other two different hardware from the repairer's test though I'm sure it is compatible but I will try replacing them for test sometimes later just to be sure.

about your electricity supply , can you check with local sources around your area and take opinions on your local supply, do you ever get lights dimming or power cuts ?

No I don't ever get lights dimming or power cuts on this new PC.

where debugger blames ntfs.sys this is simply a symptom and not the cause, if there was a problem with ntfs.sys your system would be crashing left right and center and barely work at all

I agreed because right now my system is up and running normally except that BSOD which was the first time in 11 days. Like I told you that It seems almost gone after a newer BIOs version has been installed.

to eliminate the possibility of this being a thermal problem could you download and install speedfan and once you have it setup watch your temperatures ?

Nothing abnormal about temp. As I burn my PC through almost 12Hrs.

take a look at performance information and tools\advanced tools and look for any warnings etc , also take a look at reliability monitor by typing reliability into your search bar from the start orb, click through anything found marked with an exclamation mark or red x looking for errors with the same timestamp as your bluescreen crashes ?

The only info in the exclamation mark I found was related to BSOD to the same time stamped does not tell anything much but

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff880052872b8, 0xfffff88005286b10, 0xfffff80002a78913). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 032810-19375-01.

the same dump file that your debugger blamed ntfs.sys

I already replaced the Delux Keyboard with Logitech Keyboard that compatible with Windows 7 and will see If my system can make it through 11 days without any BSOD.

Delux Keyboard is the only unknown-brand peripheral hardware in my system which has no driver and Windows 7 sees it as just some HID thing.

why 11 days?
because it was the longest time that this new PC ever made it without BSOD

and I found something.
I used Delux Keyboard on my good older system Windows XP Pro on Pentium 4 blah blah... it had problems so much. It couldn't find it when I turn on the system so it's just went alarming, after got in windows My system saw this keybaord as just some HID thing though all of the interface button worked but the alphabetical button's reponse time was so slow that it just couldn't keep up with my typical typing skill in MS word.

It might be a real culprit behind all this BSOD.
But It's too soon to conclude and I still won't rule out others possibility either.

further tests are on the way and I will report back here.

Unfortunately, replacing keyboard did not work out.
another BSOD had occurred today.

My little bros said he just left it turn on with his account for about 25 mins and he found that the OS was restarted.

I already checked the dump folder and found out that this was true.

Definite Clues:
The latest two of BSOD had occurred within an hour after turning on the system.
April 1st 2010-BSOD: Occurred immediately after I log on windows with my account.
April 2nd 2010-BSOD: Occurred after turning on for about 25 minutes
These could explain why tech guys didn't found any BSODs because they turned my system on for 3 days straight without any restarting and turning off.

Reliability History shows all BSODs (3 times now)
after BIOs has been updated to newer version (12 days ago)
with the same exact code in report.
Which is...
The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff880052872b8, 0xfffff88005286b10, 0xfffff80002a78913).

One conclusion is all 3 BSODs happened recently were from the same problem.

man...If we can just find out what is wrong with it.

Ps.BSODs about Win32k.sys was gone after tech guy updated my BIOs though I could not tell that they are all from the same problem as these currently BSODs ntfs.sys. tiring...

Okay, in the Windows Event Log Viewer shows so many critical errors.
All of it are details on BSOD.
Event ID: 41 Task: 63 Source: Kernel-Power
and I did google and found https://www.sevenforums.com/crash-loc...-what-try.html

Windows Memory Diagnostic found that there was a problem with my RAM.
I ran that test three times and all produced the same results.

I have two banks of value memory installed for Dual-Ch mode 4096MB (~4086-4088)
(Kingstion DDR3 1333MHz 2048MB)x2

So I began to pull it off and retest one by one using only Windows Memory Diagnostic and it found nothing this time, both of them has no problem.

Suprisingly, after I reinstall two of them and put it in the test in Windows Memory Diagnostic and it found nothing, no problem at all in BASIC, NORMAL and EXTENDED mode.

I will see if It can survive without any BSOD for 11 days.
and will use Windows Memory Diagnostic again if there is one occurs.

I welcomed any suggestion.

Razgriz said:

Okay, in the Windows Event Log Viewer shows so many critical errors.
All of it are details on BSOD.
Event ID: 41 Task: 63 Source: Kernel-Power
and I did google and found https://www.sevenforums.com/crash-loc...-what-try.html

Windows Memory Diagnostic found that there was a problem with my RAM.
I ran that test three times and all produced the same results.

I have two banks of value memory installed for Dual-Ch mode 4096MB (~4086-4088)
(Kingstion DDR3 1333MHz 2048MB)x2

So I began to pull it off and retest one by one using only Windows Memory Diagnostic and it found nothing this time, both of them has no problem.

Suprisingly, after I reinstall two of them and put it in the test in Windows Memory Diagnostic and it found nothing, no problem at all in BASIC, NORMAL and EXTENDED mode.

I will see if It can survive without any BSOD for 11 days.
and will use Windows Memory Diagnostic again if there is one occurs.

I welcomed any suggestion.

well keep the keyboard out of the equation for now until you have the problem nailed :)

a system that crashes only when it's being reebooted suggest to me either power supply or ram or a driver that doesnt like going in and out of power state ?

to quote since windows 95 Microsoft have stated about memory testing programs

Defective memory chips may not be detected by memory checking tools. Some memory checking programs are not adequate tests because they do not test RAM in the same way that Windows uses RAM. Most memory checkers use read/write cycles when scanning memory. Since Windows is executing code from memory, it uses execute cycles. Execute cycles are different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.

I suggest test your memory by burning to CD (using an ISO burner) & running from boot memtest86+ for at least 5 passes and moving the sticks between slots to verify motherboard ram slots work as well as the ram sticks.

If those tests come up with no errors try running your system with only one stick of ram and wait for another crash ?

If you still crash it may be time to run driver verifier but give the ram testing a few days first

I'm off for 10 days now so hopefully someone from the bluescreen team will jump in to help you get this sorted