Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Please help BSOD!!!

06 Feb 2011   #11
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Can you post the DRAM and NB/IMC voltages

Quote   Quote: Originally Posted by CarlTR6 View Post
We will also need the voltage settings for the CPU, RAM and NB or equivalent.
NB or memory controller is important. CPU voltage is listed on the CPU tab, RAM voltage is listed but it's not the actual voltage; it's the recommended voltage.
AI Tweaker tab > DRAM Voltage and VCCIO (qpi/vtt/IMC) voltage

Page 3-7 of your motherboard manual.
ASUS P8P67 PRO

Next time for posting information like CPUZ, RealTemp, just about everything except crash dumps, use the snipping tool and post the picture, in JPG format. This makes it much easier for all to see without downloading files.
Enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums


Have you been checking your temperatures?

Use Speed Fan or Real Temp , run one of these and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Here are the CPUZ snips you posted.
Attachment 136855Attachment 136854Attachment 136853

Are your two RAM cards in slots A2 and B2, CPUZ will call them slots #2 and #4?

Are you overclocking CPU or GPU?


My System SpecsSystem Spec
.
06 Feb 2011   #12
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I looked at your latest five dumps; they show four different bugcheck codes. This indicates a hardware or hardware related problem.Two of the dumps blame ntfs.sys. This is the Windows file system driver. It is most likely not the real cause and can certainly be affected by a RAM problem. I do suggest that you run CheckDisk to make sure your file system is OK -
Quote:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.


You are in excellent hands with Dave. Follow his suggestions.


Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e40eb0
Debug session time: Sun Feb  6 04:07:41.437 2011 (GMT-5)
System Uptime: 0 days 0:03:33.359
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880090c90d8, fffff880090c8940, fffff8800146b2b1}

Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseFcbWithPaging+41 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880090c90d8
Arg3: fffff880090c8940
Arg4: fffff8800146b2b1

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


EXCEPTION_RECORD:  fffff880090c90d8 -- (.exr 0xfffff880090c90d8)
ExceptionAddress: fffff8800146b2b1 (Ntfs!NtfsReleaseFcbWithPaging+0x0000000000000041)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000003b
Attempt to write to address 000000000000003b

CONTEXT:  fffff880090c8940 -- (.cxr 0xfffff880090c8940)
rax=fffffa8008768d50 rbx=fffff8a002e61010 rcx=0000000000000033
rdx=fffff8a002e61010 rsi=fffff8a002e61010 rdi=fffffa8007b72510
rip=fffff8800146b2b1 rsp=fffff880090c9310 rbp=fffff880090c98a0
 r8=fffff8a002e61100  r9=0000000000000000 r10=fffff8a002e61010
r11=fffff880090c92e0 r12=fffffa8007755180 r13=0000000000000000
r14=fffff8a002e613a0 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Ntfs!NtfsReleaseFcbWithPaging+0x41:
fffff880`0146b2b1 48894108        mov     qword ptr [rcx+8],rax ds:002b:00000000`0000003b=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000003b

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eab0e0
 000000000000003b 

FOLLOWUP_IP: 
Ntfs!NtfsReleaseFcbWithPaging+41
fffff880`0146b2b1 48894108        mov     qword ptr [rcx+8],rax

FAULTING_IP: 
Ntfs!NtfsReleaseFcbWithPaging+41
fffff880`0146b2b1 48894108        mov     qword ptr [rcx+8],rax

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff88001504e3b to fffff8800146b2b1

STACK_TEXT:  
fffff880`090c9310 fffff880`01504e3b : fffffa80`07b72510 fffff8a0`02e61010 fffff8a0`02e61010 00000000`00000009 : Ntfs!NtfsReleaseFcbWithPaging+0x41
fffff880`090c9350 fffff880`014de38f : fffffa80`07b72510 fffff8a0`02e61140 fffff8a0`02e61010 fffffa80`07755180 : Ntfs!NtfsCommonClose+0x978
fffff880`090c9420 fffff880`014d4795 : fffffa80`07755180 00000000`00000000 fffff8a0`013d0c01 00000000`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`090c94f0 fffff880`01476b7c : fffffa80`07e1d2f0 fffffa80`07755180 fffffa80`03bed401 fffffa80`03bed400 : Ntfs!NtfsFlushVolume+0x75
fffff880`090c9620 fffff880`0146abed : fffffa80`07e1d2f0 fffff880`01344d01 fffffa80`06701b80 fffff880`090c9700 : Ntfs!NtfsVolumeDasdIo+0x1dc
fffff880`090c96d0 fffff880`0146bf78 : fffffa80`07e1d2f0 fffffa80`03ba2c60 fffff880`090c9801 fffffa80`03b9c700 : Ntfs!NtfsCommonRead+0x1e61
fffff880`090c9870 fffff880`0133823f : fffffa80`03ba2fb8 fffffa80`03ba2c60 fffffa80`03b9c730 00000000`00000000 : Ntfs!NtfsFsdRead+0x1b8
fffff880`090c9920 fffff880`013366df : fffffa80`066f88d0 00000000`00000001 fffffa80`066f8800 fffffa80`03ba2c60 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`090c99b0 fffff800`02f89669 : 00000000`00000000 fffffa80`03bed420 00000000`00000001 fffffa80`03ba2c60 : fltmgr!FltpDispatch+0xcf
fffff880`090c9a10 fffff800`02f90773 : fffffa80`03bed420 fffffa80`03bed420 fffffa80`03bed420 fffff880`031d3180 : nt!IopSynchronousServiceTail+0xf9
fffff880`090c9a80 fffff800`02c717d3 : 00000000`00000740 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631
fffff880`090c9b70 00000000`76f7fdba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04a8e128 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f7fdba


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsReleaseFcbWithPaging+41

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff880090c8940 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsReleaseFcbWithPaging+41

BUCKET_ID:  X64_0x24_Ntfs!NtfsReleaseFcbWithPaging+41

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

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e34eb0
Debug session time: Sun Feb  6 04:09:52.289 2011 (GMT-5)
System Uptime: 0 days 0:01:40.211
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff8a003c953c0, fffff8a003c95450, 50901a5}

GetPointerFromAddress: unable to read from fffff80002e9f0e0
GetUlongFromAddress: unable to read from fffff80002e0d210
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+528 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a003c953c0, The pool entry we were looking for within the page.
Arg3: fffff8a003c95450, The next pool entry.
Arg4: 00000000050901a5, (reserved)

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

GetUlongFromAddress: unable to read from fffff80002e0d210

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8a003c953c0 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d9b6d3 to fffff80002c66580

STACK_TEXT:  
fffff880`08e52698 fffff800`02d9b6d3 : 00000000`00000019 00000000`00000020 fffff8a0`03c953c0 fffff8a0`03c95450 : nt!KeBugCheckEx
fffff880`08e526a0 fffff880`014b19e8 : fffffa80`07754180 fffff880`08e52960 fffff8a0`6366744e fffff880`08e52878 : nt!ExDeferredFreePool+0x12c4
fffff880`08e52750 fffff880`014b9adc : fffffa80`08c69930 fffff8a0`06b03c70 fffff8a0`06b03b40 fffffa80`07754180 : Ntfs!NtfsCommonClose+0x528
fffff880`08e52820 fffff880`012e323f : fffff880`08e52901 fffffa80`089a9010 fffff880`08e58000 fffff700`00000002 : Ntfs!NtfsFsdClose+0x2dc
fffff880`08e52920 fffff880`012e16df : fffffa80`066efb20 fffffa80`089a9010 fffffa80`065a4f00 fffffa80`089a9010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`08e529b0 fffff800`02f7d14e : fffffa80`086fe400 fffffa80`0668fb10 fffffa80`08638b30 fffffa80`066efb20 : fltmgr!FltpDispatch+0xcf
fffff880`08e52a10 fffff800`02c6ac84 : fffff8a0`0386e030 fffffa80`08638b30 fffffa80`039e7080 fffffa80`039f0890 : nt!IopDeleteFile+0x11e
fffff880`08e52aa0 fffff800`02f7ced4 : fffffa80`08638b30 00000000`00000000 fffffa80`08a9eb60 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`08e52b00 fffff800`02f7cdd4 : 00000000`00000074 fffffa80`08638b30 fffff8a0`039084e0 00000000`00000074 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`08e52b90 fffff800`02c657d3 : fffffa80`08a9eb60 fffff880`08e52c60 00000000`77c73540 00000000`0027ed00 : nt!ObpCloseHandle+0x94
fffff880`08e52be0 00000000`77b8fe4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00bbe1b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b8fe4a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsCommonClose+528
fffff880`014b19e8 e9edfdffff      jmp     Ntfs!NtfsCommonClose+0x31a (fffff880`014b17da)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  Ntfs!NtfsCommonClose+528

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

FAILURE_BUCKET_ID:  X64_0x19_20_Ntfs!NtfsCommonClose+528

BUCKET_ID:  X64_0x19_20_Ntfs!NtfsCommonClose+528

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

Debug session time: Sat Feb  5 15:57:13.966 2011 (GMT-5)
System Uptime: 0 days 0:00:12.261
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff68000002fc0, b5, fffffa800819dcc0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+138f2 )

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

Debug session time: Sat Feb  5 15:54:33.871 2011 (GMT-5)
System Uptime: 0 days 0:01:58.166
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffff960001a5e75}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

Debug session time: Sat Feb  5 15:52:00.081 2011 (GMT-5)
System Uptime: 0 days 0:03:55.002
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88009a19e68, fffff88009a196d0, fffff880015416c0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
My System SpecsSystem Spec
06 Feb 2011   #13
Hopalong X

Windows7 Pro 64bit SP-1; Windows XP Pro 32bit
 
 

Download and then Open this. Then post a Snip in your next posting please.
PassMark RAMMon - Identify RAM type, speed & memory timings

No need to add to cart it is FREE!
Right side of the page at link select and click 32bit or 64bit according to your Win 7.
I beleive from your specs you will need the 64bit.

It will give us a lot of details on your RAM.

Mike
My System SpecsSystem Spec
.

06 Feb 2011   #14
Egg

Windows 7 Home Premium 64bit
 
 

hey all thanks for the responses. I think i may of found the problem, I'll explain below.

In response to dave76.

Here is the speedfan shot under idle temps
Attachment 136944

Also here is the bios screenshot
Attachment 136945

Sorry to ask but whats the best way to put the CPU under load so I can get a screenshot?

Yes I have definitely been using slot a2 & b2. I am not overclocking the cpu or gpu.

I am currently only using stick 1 in slot 4 as PC keeps on crashing. My PC crashed multiple times this morning couldn't even get into windows. Crashed in the bios screen as well which never happened to me before. Seems to run stable with one stick so far. I believe the second stick of ram (stick 2) is the issue, ran memtest again on it by itself and got multiple errors nearly straight away. But I will do further tests to make sure as per the previous instructions. This definitely didn't occur the first time I used memtest to test the ram sticks separately. I hope to get some more consistent results.

Thanks for the responses carltr6 & hopalong x. I will try your suggestions when i get back, just have to go to work now!!! running late too!! haha

Again thanks for everyones help.
My System SpecsSystem Spec
06 Feb 2011   #15
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Thank you, Mike. I appreciate the help.

@ egg - it does look like you have narrowed your problem down. Crashing while in BIOS certainly indicates a hardware problem. Continue to follow Dave's and Mike's suggestions. They are the pros at this RAM stuff.
My System SpecsSystem Spec
06 Feb 2011   #16
Hopalong X

Windows7 Pro 64bit SP-1; Windows XP Pro 32bit
 
 

Looks like you may have it down to a bad stick of RAM.

The RamMon software was just to help check the settings it won't tell you much if a stick is really bad as yours seems to be.

Good luck.
Mike
My System SpecsSystem Spec
07 Feb 2011   #17
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

The core temps look good at idle, evidently SpeedFan isn't ready for your motherboard yet.

Use Prime95 to put a load on your system, always have a CPU core temp program running to monitor your temps.

CPU - Stress Test with Prime95

Use RealTemp 3.67 for Sandy Bridge


It's not unusual for memtest86+ to pass on tests and then later fail, it is just the way electronics are.

Change the Command Rate to 2T and bump your VCCIO to 1.1v and run memtest86+ again with one RAM card in slot A2 (second from the CPU).

What is the part number of your RAM, CPUZ says it's F3-10666CL9-2GBRL, can't find that number on the G.Skill site. Closest one is F3-10666CL9D-4GBXL, is this your P/N?
My System SpecsSystem Spec
08 Feb 2011   #18
Egg

Windows 7 Home Premium 64bit
 
 

hey dave, the part number of ram is F3-10666CL9D-4GBRL, heres the link.

F3-10666CL9D-4GBRL

I have tried used memtest again per your last post (with adjustments to voltage & command rate) but have not got any errors. So far only tested stick 2 in slot a2.

Going to do the CPU test tonight. I will try post tomorrow. Thanks all.


CarlTR6 - Below is the CHKDSK results

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
110336 file records processed. File verification completed.
504 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
151596 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
110336 file SDs/SIDs processed. Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
Security descriptor verification completed.
20631 data files processed. CHKDSK is verifying Usn Journal...
36363072 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
110320 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
8316096 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

58510335 KB total disk space.
24977212 KB in 84863 files.
54176 KB in 20632 indexes.
0 KB in bad sectors.
214563 KB in use by the system.
65536 KB occupied by the log file.
33264384 KB available on disk.

4096 bytes in each allocation unit.
14627583 total allocation units on disk.
8316096 allocation units available on disk.

Internal Info:
00 af 01 00 23 9c 01 00 08 fa 02 00 00 00 00 00 ....#...........
73 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 s...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
My System SpecsSystem Spec
08 Feb 2011   #19
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Good news on the memtest.

Run the memtest with stick 1 in slot b2, assuming the first test you did with stick 1 was in slot a2.
Let it run for 7 passes, this might take several hours, you can let it run over night.

Let us know the results.
My System SpecsSystem Spec
08 Feb 2011   #20
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Good news on Check Disk, too. Check Disk did some minor cleanup of your files system and shows zero bad sectors. Your HD is probably OK.
My System SpecsSystem Spec
Reply

 Please help BSOD!!!




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 13:03.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App