New
#11
If you plan on replacing the hard drive..( this will involve a clean installation of Windows ) I would wait and see if your problem continues .. No sense in looking for an old problem ...
Blue Screen On Windows 7 64 Bit Random
-
-
New #12
-
New #13
Follow these instructions and be sure to run the tool as administrator and Ill take a look...
https://www.sevenforums.com/crashes-d...tructions.html
-
New #14
OK. I did what you asked. I did it in the morning. Posting it now. See attached files.
I have also attached my previous dump files. Will attach new ones once I get a BSOD.
-
New #15
Your .dmp file is showing a stop error of 4E which is memory corruption with a PFN corruption argument ... Most PFN errors are caused by a bad driver, but lets cover all of the bases....
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes. If memtest shows errors, you will need to test each module until you find one that passes, then test each slot to eliminate mother board problems ... Replace any bad modules ...
The following drivers are out of date and need to be replaced..Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, 12b268, 2, 13ace7} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 000000000012b268, page frame number Arg3: 0000000000000002, current page state Arg4: 000000000013ace7, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_99 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002b5338c to fffff80002ac3740 STACK_TEXT: fffff880`035e77f8 fffff800`02b5338c : 00000000`0000004e 00000000`00000099 00000000`0012b268 00000000`00000002 : nt!KeBugCheckEx fffff880`035e7800 fffff800`02a7351d : ffffffff`ffffffff 00000000`00000001 ffffffff`ffffffff 00000000`00000001 : nt!MiBadShareCount+0x4c fffff880`035e7840 fffff800`02bca37a : fffff800`02c4fb40 fffff880`035e7a50 fffffa80`00000000 fffff800`00000012 : nt! ?? ::FNODOBFM::`string'+0x20403 fffff880`035e7a30 fffff800`02b45912 : fffffa80`04f1bb60 fffff880`00000000 00000000`00000000 fffff880`035e7ba0 : nt!MiEmptyWorkingSet+0x24a fffff880`035e7ae0 fffff800`02ad7ee2 : 00000000`00008252 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x49554 fffff880`035e7b80 fffff800`02ad80e8 : 00000000`00000008 fffff880`035e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`035e7bd0 fffff800`02d67c06 : fffffa80`04f1bb60 00000000`00000080 fffffa80`04eea040 00000000`00000001 : nt!KeBalanceSetManager+0x138 fffff880`035e7d40 fffff800`02aa1c26 : fffff880`009b1180 fffffa80`04f1bb60 fffff880`009bc0c0 5f3953cc`8691c6a3 : nt!PspSystemThreadStartup+0x5a fffff880`035e7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiBadShareCount+4c fffff800`02b5338c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiBadShareCount+4c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c Followup: MachineOwner ---------
Code:fffff880`02e54000 fffff880`02f72000 dump_iaStorV dump_iaStorV.sys Wed Apr 08 12:57:17 2009 (49DCD76D ... Intel Storage drivers ... http://downloadcenter.intel.com/Default.aspx fffff880`06057000 fffff880`06175000 hiber_iaStorV hiber_iaStorV.sys Wed Apr 08 12:57:17 2009 (49DCD... Intel Storage drivers ... http://downloadcenter.intel.com/Default.aspx fffff880`01205000 fffff880`01323000 iaStorV iaStorV.sys Wed Apr 08 12:57:17 2009 (49DCD76D)... Intel Storage drivers ... http://downloadcenter.intel.com/Default.aspx fffff880`05bba000 fffff880`05bbe980 Lycosa Lycosa.sys Fri Jan 18 03:51:42 2008 (4790689E) ... Razer Tarantula Keyboard Driver ... Razer Support
-
-
New #17
I think there is some problem with my Razel Lycosa Keyboard. When i updated the driver for Keyboard I started getting BSOD even with 1 Module of RAM installed. There was a BSOD with every module. But as soon as I removed the keyboard there was no BSOD. Can this be keyboard fault. Currently I am using my old crappy keyboard, I want to use the lycosa again. But as soon I isntall it i start getting BSOD.
I have attached my new Dump file.
-
New #18
Continue to run memtest overnight without your lycosa keyboard overnight for testing purposes ... but it looks like the lycosa driver may be the cause of your problem, but we shall see..
-
New #19
As asked by you I ran the memory test overnight for 8 hours approx with 5 pass and 0 errors. Seems like the memory is fine and there was problem with Lycosa Keyboard. I will now wait to see if BSOD happens again and post here.
Any other thing you recommend?
Also what you recommend to install back Lycosa?
See posted Memshot screenshot (via camera).
-
New #20
Go ahead and reinstall the Lycosa drivers, if you start to get BSODs' again, then you know the problem... the keyboard... Let us know how it comes out..
Quote
Related Discussions