Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › BSOD help please
New Posts  All Forums:Forum Nav:

BSOD help please - Page 4

post #31 of 41
Thread Starter 
yeh it is enabled in the bios, i`ll wait and see if it happens again and get back to you smile.gif
post #32 of 41
Quote:
Originally Posted by markshim View Post

yeh it is enabled in the bios, i`ll wait and see if it happens again and get back to you smile.gif

Excellent.
Quote:
Originally Posted by bigkahuna360 View Post

Quote:
Originally Posted by E-Peen View Post

Quote:
Originally Posted by bigkahuna360 View Post

E-Peen how aren't you a mod yet? Or did you apply this time?

Haha tongue.gif

I have applied, hopefully this is my time!

Wish you the best.

Thank you, my friend thumb.gif
post #33 of 41
Thread Starter 
hi guys,

thought i should post in this post about a BSOD i have just had. this time it looks different than the last one i had but im not sure?
everything was working fine untill now, i was dreffraging with defraggler when it happened.

can anyone help please, here is the who crashed report and my minidump.

Minidump.zip 20k .zip file

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 04/05/2012 15:28:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A011995370, 0xFFFFF8A011995361, 0x2285558C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 04/05/2012 15:28:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x7C9EF)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A011995370, 0xFFFFF8A011995361, 0x2285558C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



Conclusion

2 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
post #34 of 41
Hi mark, sorry to hear you're still having issues.

I've taken a look at the attached dump, it's a DE bugcheck with the culprit as ntkrnlmp.exe (not the cause, just pointing to that as Windows cannot find the actual cause). At this point, it's hardware, a 3rd party driver we'll need verifier for, or OS corruption. The dump mentions pool corruption, so it's possible this is driver related, or memory related.

I'd like you to do the following:

1. If any components in your system are overclocked, please return all of them to stock speeds as unstable overclocks will cause issues. You're more than welcome to OC after we label this as your issue if you are overclocked, or when we solve your issue in general.

2. Run a Memtest to test your memory for errors.

3. CHKDSK:
Quote:
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click .

4. If Memtest comes up clean, it may be a third party driver we're not being told of, so we'll need to enable Driver Verifier to hopefully catch what it is in the act. Once you crash, attach the verifier enabled dump (latest BSOD crash dump).

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\Minidump\050412-17955-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`030a1650
Debug session time: Fri May  4 11:28:04.442 2012 (UTC - 4:00)
System Uptime: 0 days 4:09:10.972
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DE, {2, fffff8a011995370, fffff8a011995361, 2285558c0}

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

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

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

POOL_CORRUPTION_IN_FILE_AREA (de)
A driver corrupted pool memory used for holding pages destined for disk.
This was discovered by the memory manager when dereferencing the file.
Arguments:
Arg1: 0000000000000002
Arg2: fffff8a011995370
Arg3: fffff8a011995361
Arg4: 00000002285558c0

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xDE

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002e8f84d to fffff80002ed9c80

STACK_TEXT:  
fffff880`0318c2d8 fffff800`02e8f84d : 00000000`000000de 00000000`00000002 fffff8a0`11995370 fffff8a0`11995361 : nt!KeBugCheckEx
fffff880`0318c2e0 fffff800`02ea7902 : 00000000`00000000 00000000`00000700 fffffa80`09c65278 fffff8a0`0d111300 : nt! ?? ::FNODOBFM::`string'+0x2ce51
fffff880`0318c3d0 fffff880`012bb9ef : fffffa80`076caa08 fffffa80`09c65230 00000000`00000000 fffffa80`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`0318c440 fffff880`012e984e : fffffa80`09c65230 fffff8a0`0d111310 00000000`00000000 fffff8a0`0d111301 : Ntfs!NtfsFlushAndPurgeScb+0x1bd
fffff880`0318c4d0 fffff880`012d7fe5 : fffffa80`09c65230 fffffa80`07090f20 fffffa80`079e1180 fffff8a0`0d111578 : Ntfs!NtfsOpenAttribute+0x80e
fffff880`0318c5e0 fffff880`012d3e3b : fffff880`0b0ca4a0 fffffa80`09c65230 fffff8a0`0d111578 fffff8a0`000000bc : Ntfs!NtfsOpenExistingAttr+0x145
fffff880`0318c6a0 fffff880`012d709f : fffffa80`09c65230 fffffa80`07090c10 fffff8a0`0d111578 fffff880`000000bc : Ntfs!NtfsOpenAttributeInExistingFile+0x5ab
fffff880`0318c830 fffff880`012e7166 : fffffa80`09c65230 fffffa80`07090c10 fffff8a0`0d111578 00000000`00000701 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
fffff880`0318c920 fffff880`012e4911 : fffffa80`09c65230 fffffa80`07090c10 fffff880`0318caf0 fffff880`0318cb40 : Ntfs!NtfsFindStartingNode+0x5e6
fffff880`0318c9f0 fffff880`01242945 : fffffa80`09c65230 fffffa80`07090c10 fffff880`0b0ca4a0 fffff800`02ee1200 : Ntfs!NtfsCommonCreate+0x3e1
fffff880`0318cbd0 fffff800`02ee3361 : fffff800`03079200 fffff800`031cf700 fffffa80`06af1000 00000000`00000000 : Ntfs!NtfsFspDispatch+0x26d
fffff880`0318ccb0 fffff800`03173fda : 00000000`00000000 fffffa80`06af1040 00000000`00000080 fffffa80`069ab990 : nt!ExpWorkerThread+0x111
fffff880`0318cd40 fffff800`02eca9c6 : fffff880`02f64180 fffffa80`06af1040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2ce51
fffff800`02e8f84d cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2ce51

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

FAILURE_BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2ce51

BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2ce51

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

post #35 of 41
Thread Starter 
hi there,

i do not have anything overclocked on my pc, everything is set to defult and auto in bios.
i will run memtest tomorrow morning b4 i go gym, is it ok to leave it running while i am out or is it not safe too ?

also with the CHKDSK: do i tick both boxes to auto fix or just the top one ?

thank for helping again e-peen smile.gif
post #36 of 41
Quote:
Originally Posted by markshim View Post

hi there,
i do not have anything overclocked on my pc, everything is set to defult and auto in bios.
i will run memtest tomorrow morning b4 i go gym, is it ok to leave it running while i am out or is it not safe too ?
also with the CHKDSK: do i tick both boxes to auto fix or just the top one ?
thank for helping again e-peen smile.gif

You're fine to keep Memtest running whilst not attending the system, everything is automated. Let it run for at least 7-8 passes, it's important to let it run that long as errors sometimes do not show on certain DIMMs for a few passes, depending on the severity of the issue as well with your specific DIMMs. With this being said, you could even run Memtest overnight as well and check it when you wake up.

As far as CHKDSK, make sure you select Check Now, auto-fix as well.

Keep me updated smile.gif
post #37 of 41
Thread Starter 
hi there,

i have just ran memtest and it got to about 20mins in and found 2 errors already so i rebooted. what does this mean?

should i try and RMA the ram to corsair i have only had it since christmas. what do i do next, put my old ram back in for now ?

frown.gif
Edited by markshim - 5/5/12 at 4:35am
post #38 of 41
Thread Starter 
hello,

just letting you know that i have just tested one stick of ram at a time to see if i could find out which one is faulty, i tested for the same time as i got the last errors which was 20mins in.

both sticks did not have any errors come up. i think the ram i have isn`t compatible with my motherboard set on auto and defult settings. because i am not good at changing bios settings i have put my ols sticks of ram back in for now, untill i get my new asus sabertooth 990fx board when the piledriver comes out.

if i still get the BSOD with my old sticks of ram back in then at least i will know that its either drivers or my motherboard.
post #39 of 41
It may be that the RAM isn't compatible, good call on testing the ram one stick at a time, mark!

I would actually recommend memtesting with the old RAM to see if you get errors. If you don't after at least 6-7 passes, it's possible the newer memory is bad and you're just not letting it go through enough passes, or as you said, the RAM isn't compatible with the board at all, or you need to set everything to its factory advised settings.

If that's the case, I'll help you set everything up if you'd like.
post #40 of 41
Thread Starter 
the only way i can set the settings to the same as the settings for the ram is to overclock my cpu and motherboard, which i dont really wonna do. i will carry on using my old ram for now as its corsair dominator 4 gb so its ok untill i get my new motherboard. if the BSOD happens while im using theses tho then i will post back. smile.gif

thank you again .
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › BSOD help please