random bluescreens ntoskrnl.exe

[squat251]

still having these problems, but went ahead and did a more thorough job of documenting the errors. have had 2 in the last 12hrs. this is simply unacceptable. have a crappy laptop that is like 3 years older than this, (my gaming machine) that is trouble free.

windows 7 ultimate x64
6gigs of ram.
500gb main drive, 1tb storage
random blue screens.
ps. this system is under a year old. willing to do a fresh install, but would prefer not to.

 

[zigzag3143]

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[squat251]

up to the 3rd pass of memtest still no errors. don't really think that is the problem, but heck, ill give it a shot.

if that runs clean, will reformatting the drive for a fresh install work? could it be the hard drive? btw i have no idea why there is a dump from 2009 this system was put together from fresh parts (except one of the disk drives) last summer.

 

[squat251]

okay 6 passes 0 errors the driver stress thing didnt do anything that i could tell. no bsod from it atleast any ideas?

i thought that google chrome might have been causing it but after the first bsod on the 22nd I didnt use chrome and then i got another one. also it seems to only do it while I'm not using the computer.

 

[writhziden]

Driver Verifier sometimes needs to run for a day or two to get blue screen crashes.

If it usually crashes when you are not using the computer, it is likely a power state problem due to the computer entering a low power state as part of power management.

With Verifier on, you want to try to replicate the situations that cause blue screen crashes, so leave the computer be for a while and come back after an hour or so (or however long you usually leave it when you are "not using the computer") to see if any crashes have occurred.

 

[squat251]

how can i tell if verifier is working?

 

[writhziden]

Start Menu -> Type "Verifier" (without quotes) into the Search programs and files box (do not hit enter) -> Right click Verifier -> Run as administrator -> Display existing settings -> Post a screenshot of what you have in the two lists (http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html)

 

[squat251]

here it is

i disabled my wireless card since the only drivers are from 2009 we'll see if that helps

 

[writhziden]

Verifier looks good. Let it run for a few days and post any crash reports during that time.

 

[squat251]

Another bsod i look at nirsofts tool after each one, and though i know its not specific enough it shows the same address everytime for these more recent errors. ill put up the dump but with the programs you guys use you cant see where this is?

also, where would the log files be for the verifier program? so i can post those too.

 

[writhziden]

Antivirus software:

avgnt.exe	c:\program files (x86)\avira\antivir desktop\avgnt.exe	2480	8	200	1380	2/24/2012 5:31 AM	10.0.13.18	275.16 KB (281,768 bytes)	4/20/2011 10:24 AM
avguard.exe	c:\program files (x86)\avira\antivir desktop\avguard.exe	2040	8	200	1380	2/24/2012 5:30 AM	10.0.1.59	263.16 KB (269,480 bytes)	4/20/2011 10:24 AM
avshadow.exe	c:\program files (x86)\avira\antivir desktop\avshadow.exe	2124	8	200	1380	2/24/2012 5:30 AM	1.0.0.6	254.66 KB (260,776 bytes)	4/20/2011 10:24 AM
sched.exe	c:\program files (x86)\avira\antivir desktop\sched.exe	1772	8	200	1380	2/24/2012 5:30 AM	10.0.0.21	133.16 KB (136,360 bytes)	4/20/2011 10:24 AM

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


Loading Dump File [D:\Kingston\BSODDmpFiles\squat251\new minidump\022512-17565-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
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03256000 PsLoadedModuleList = 0xfffff800`0349be90
Debug session time: Sat Feb 25 20:54:51.342 2012 (UTC - 7:00)
System Uptime: 0 days 2:18:52.997
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fc500671f0, 82b0000112d15882, fffff68000032269}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc500671f0
Arg3: 82b0000112d15882
Arg4: fffff68000032269

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

TRAP_FRAME:  fffff88008b0c860 -- (.trap 0xfffff88008b0c860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80080a6060 rbx=0000000000000000 rcx=fffff8a00ce3e6a0
rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034015f7 rsp=fffff88008b0c9f0 rbp=0000000000001000
 r8=0000000000000001  r9=fffff80003256000 r10=fffffa800519c3c8
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!ExAllocatePoolWithTag+0x517:
fffff800`034015f7 4c8b4908        mov     r9,qword ptr [rcx+8] ds:fffff8a0`0ce3e6a8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032b32dd to fffff800032d6640

STACK_TEXT:  
fffff880`08b0c508 fffff800`032b32dd : 00000000`0000001a 00000000`00000411 fffff6fc`500671f0 82b00001`12d15882 : nt!KeBugCheckEx
fffff880`08b0c510 fffff800`03307a71 : 82b00001`12d15882 fffff6fc`500671f0 0000007f`fffffff8 fffff800`033022a0 : nt! ?? ::FNODOBFM::`string'+0x6061
fffff880`08b0c560 fffff800`032f425f : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`0345abc0 : nt!MiResolveTransitionFault+0x381
fffff880`08b0c5f0 fffff800`032e443b : fffff8a0`021d0b50 00000000`00000000 00000000`00000000 fffff800`03480340 : nt!MiDispatchFault+0x95f
fffff880`08b0c700 fffff800`032d476e : 00000000`00000000 fffff8a0`0ce3e6a8 fffffa80`08663300 fffffa80`0519c940 : nt!MmAccessFault+0xe1b
fffff880`08b0c860 fffff800`034015f7 : fffff8a0`0cdcd580 00000000`00000003 fffff8a0`00000000 fffff800`03401fbd : nt!KiPageFault+0x16e
fffff880`08b0c9f0 fffff800`035d058c : 00000000`00000003 00000000`00000001 fffff880`08b0cca0 fffff880`00000000 : nt!ExAllocatePoolWithTag+0x517
fffff880`08b0cae0 fffff800`0359b86b : 00000000`00000000 00000000`00000120 00000000`00000001 00000000`01544e01 : nt!SeQueryInformationToken+0x49c
fffff880`08b0cb70 fffff800`032d58d3 : fffffa80`080a6060 00000000`003321c0 00000000`00000000 fffffa80`08ecf2b0 : nt!NtCompareTokens+0x13b
fffff880`08b0cc20 00000000`76d81c0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00cdeea8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d81c0a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+6061
fffff800`032b32dd cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+6061

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6061

BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6061

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

Caused by Verifier, as anticipated. Typically, when Verifier blames Windows processes, you either have corrupted Windows files or a hardware problem. This particular crash report points to memory.

• Memtest86+ does not always find memory errors the first time it is run. Sometimes it needs to be run a few times for seven passes each to catch memory errors. Also, what memory do you have in the system? Can you download and install CPU-Z and upload screenshots of the CPU, Mainboard, Memory, and SPD tabs? In the SPD tab, upload an image of each slot.
  
  The screenshots can help determine if there is a conflict with your memory or an incompatibility.
  
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
  
• I also notice Avira installed on your system which is known to cause crashes on some systems. Please remove Avira through Start Menu -> Control Panel -> Uninstall a program and then run the Avira RegistryCleaner - Download to remove remnants. Replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall, at least to test to see if the system is then more stable.
  
  You may also check out the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

 

[squat251]

there we go, memory i know that slot 2 and 4 are supposed to increase the speed or something but yeah dunno why its still doing it, my bios settings are stock. as for avira, i think I'll leave it on, i have bad experience with MSE

 

[writhziden]

It is your choice whether you want to keep Avira, but remember the warning that it can cause crashes on some systems. What kinds of problems did you have with MSE?

Please upload the Mainboard, Memory, and CPU tab screenshots, as well. It will help to see what your memory settings are.

Also, run Memtest86+ again tonight.

Post back your results from the system file check.

Thanks.

 

[squat251]

after installing mse (same pc) i had constant freezing and stuttering, after removing it it all went away. the file system scan showed no errors. ill edit this post in a few for the pictures of the tabs (breakfast time)


apparently the only antivirus "guaranteed" not to cause errors is that one, it also forces updates and keeps track of things i dont necessarily want kept track of. on the whole, i dont approve of mse, I'm sure some people love it, i however do not. if it were so great it would be included in windows 7, but because it tracks us and we need to agree to separate terms, it is not. sorry for the mini rant, but you wanted the reasons i choose not to use mse, and those are the brunt of them.


I'll keep track of this thread from my laptop, and run memtest for 7 passes or what ever.


edit: thinking about it hell, i have nothing but time on my hands, especially since i cant use it for games now anyway ill run memtest till something happens, gotta be an error in like 12 passes right?

 

[squat251]

okay, so 9 passes 0 errors. atleast as far as memtest is concerned my ram is perfect.

is there a similar test i can run for the hard drive? perhaps there is an error there?

should i just run a clean re-install?

 

[writhziden]

http://www.sevenforums.com/tutorials/433-disk-check.html is the Windows method for checking the hard disk. You can also find manufacturer diagnostic tools. HD Diagnostic can be used to find the manufacturer and the appropriate diagnostic tools for your hard drive.

Memory settings all look good, by the way. Memtest86+ also does not always find errors. Sometimes if crashes are frequent enough, you can test the memory just by running Windows with one module at a time and see if the system is stable with each module and each slot. If you find a good module in a good slot, you can test the other slots with the good module to determine if you have a bad slot. Remember to use safe ESD steps. Avoid Static Damage to Your PC | PCWorld

 

[squat251]

disc check returned no errors

 

[writhziden]

disc check returned no errors

Alright, that is good news.

Are you comfortable testing your memory modules as I laid out in my previous post?

 

[squat251]

sure ill do that a little later tonight. thats going to be 3 days of testing atleast.

 

[writhziden]

Any news on the module testing?