New
#11
well got a new one for ya torretg
Random BSOD in Win7
-
-
New #12
Hi and welcome
just an FYI TorrentG is no longer here
this crash involved several things the x264x64 file, the directx component of the video driver, and a driver. I suspect it is a one off while playing a game.
You can
run a system file check type cmd in search>right click and run as admin
>sfc /scannow
reinstall the video driver if it happens again. if still happens download and run memtestx86 for 5 runs
Good Luck Mate
Ken J+
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\123009-17206-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`04019000 PsLoadedModuleList = 0xfffff800`04256e50 Debug session time: Wed Dec 30 09:53:36.599 2009 (GMT-5) System Uptime: 4 days 10:47:34.766 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffaa009fc5738, 2, 0, fffff80004096d99} Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+d9 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffaa009fc5738, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80004096d99, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800042c10e0 fffffaa009fc5738 CURRENT_IRQL: 2 FAULTING_IP: nt!KiTimerExpiration+d9 fffff800`04096d99 483958f8 cmp qword ptr [rax-8],rbx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: x264_x64.exe TRAP_FRAME: fffff88002f93cd0 -- (.trap 0xfffff88002f93cd0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffaa009fc5740 rbx=0000000000000000 rcx=0000000001780b1a rdx=000000000000001a rsi=0000000000000000 rdi=0000000000000000 rip=fffff80004096d99 rsp=fffff88002f93e60 rbp=0000000001780b1a r8=0000000000000000 r9=00000000000000c0 r10=000000000000001a r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!KiTimerExpiration+0xd9: fffff800`04096d99 483958f8 cmp qword ptr [rax-8],rbx ds:8000:fffffaa0`09fc5738=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000408a469 to fffff8000408af00 STACK_TEXT: fffff880`02f93b88 fffff800`0408a469 : 00000000`0000000a fffffaa0`09fc5738 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`02f93b90 fffff800`040890e0 : 00000000`00000000 0000037f`20e5e414 fffffa80`071ef000 00000000`00e5611d : nt!KiBugCheckDispatch+0x69 fffff880`02f93cd0 fffff800`04096d99 : 00000000`00000000 00000000`00000000 fffffa80`06968018 fffff880`13ef9336 : nt!KiPageFault+0x260 fffff880`02f93e60 fffff800`04096697 : fffff880`13ef92c0 fffff880`01780b1a 00000000`00000000 00000000`0000001a : nt!KiTimerExpiration+0xd9 fffff880`02f93f00 fffff800`04091065 : 00000000`00000000 fffffa80`08059060 00000000`00000000 fffff880`13f3f760 : nt!KiRetireDpcList+0x277 fffff880`02f93fb0 fffff800`04090e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 fffff880`06dccbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTimerExpiration+d9 fffff800`04096d99 483958f8 cmp qword ptr [rax-8],rbx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiTimerExpiration+d9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerExpiration+d9 BUCKET_ID: X64_0xA_nt!KiTimerExpiration+d9 Followup: MachineOwner ---------
-
New #13
awww bummer, he was a good guy =P
yeah, I saw the x264x64 in the dump, it's for video encoding. So I've already updated a couple of the things associated with that.
I did run memtest before (found no issues). I believe I only let it run through once, though. whatever the default is. if so, letting it run through 5 times would probably take ~12hrs or so.
as for the video driver I've updated it a couple times while having this issue. I just checked and there is not a never version. I can reinstall it if you think it'll help but it doesn't seem like it's the culprit.
SFC found no errors.
anything else I could possibly try?
-
New #14
-
New #15
this provide anymore insight?
this was a: "PAGE_FAULT_IN_NONPAGED_AREA"
-
New #16
Please try running Driver Verifier according to these directions:
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 "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.
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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Quote
Related Discussions