Author Topic: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1  (Read 4013 times)

Offline Sc0rPi0n

  • Contributor
  • ***
  • Posts: 10
Hi all,

System is stable overall but crashes with a BSOD with running Alt.binz . I tested with all latest versions to the latest one (0.39.2)
Searched for it here and came across a Microsoft patch with I requested (from Microsoft) but cant install because it it not applicable for my system...

When I'd used my machine without alt.binz No problem crash whatsoever. When I launched Alt.Binz, give it max 30 minuten *bam* bsod.
I've installed Debugging tools so here's the dump files attached. Note that de recent crashed both relate to altbinz.exe

I already check my memory with Memtest86+ and run it al least 8 hours (overnight) with no errors.

So can you guys know what the problem is and better yet fix it? I don't want to use another program but going to have to it these crashes keep coming.

greeting.
Frank

Crashfile from 18 july Same problem.
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03063000 PsLoadedModuleList = 0xfffff800`032a8650
Debug session time: Mon Jul 18 19:13:33.915 2011 (UTC + 2:00)
System Uptime: 0 days 0:07:41.829
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
....
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff800030e0c3f, 0, 3100}

Probably caused by : memory_corruption

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

4: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff800030e0c3f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000003100, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!KiGeneralProtectionFault+bf
fffff800`030e0c3f 0f              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000003100

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

BUGCHECK_STR:  0x1E_c000001d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  altbinz.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000312e5d8 to fffff800030e2d00

FAILED_INSTRUCTION_ADDRESS:
nt!KiGeneralProtectionFault+bf
fffff800`030e0c3f 0f              ???

STACK_TEXT: 
fffff880`0b51de28 fffff800`0312e5d8 : 00000000`0000001e ffffffff`c000001d fffff800`030e0c3f 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b51de30 fffff800`030e2382 : fffff880`0b51e608 80000000`8d671867 fffff880`0b51e6b0 fffffa80`04442ec8 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0b51e4d0 fffff800`030e04df : fffff880`0b51e6b0 fffff960`00175c00 7a80a080`00000000 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0b51e6b0 fffff800`030e0c3f : fffff900`c082d7d0 fffff900`c082d7d0 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0b51e840 fffff800`0314cdd8 : fffff680`00025318 fffff880`0b51ea40 fffff700`01080000 fffffa80`04442ec8 : nt!KiGeneralProtectionFault+0xbf
fffff880`0b51e9d0 fffff800`030f01ee : 00000000`00000001 00000000`04a63000 fffff880`0b51ec20 fffff680`00025318 : nt! ?? ::FNODOBFM::`string'+0x2a7fb
fffff880`0b51eac0 fffff800`030e0e2e : 00000000`00000001 00000000`04a63000 00000000`00000001 00000000`0002e000 : nt!MmAccessFault+0x5de
fffff880`0b51ec20 00000000`77062373 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018f5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77062373


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
15 errors : !nt (fffff800030e0bc0-fffff800030e0c78)
fffff800030e0bc0 *d8  88  01  00  00  41  f6  42 *99  80  74  3c  b9  02  01  00 .....A.B..t<....
fffff800030e0bd0 *78  0f  32  48  c1  e2  20  48 *dd  c2  49  39  82  b8  00  00 x.2H.. H..I9....
fffff800030e0be0  00  74  25  49  39  82  b0  01 *db  00  74  1c  49  8b  92  b8 .t%I9.....t.I...
fffff800030e0bf0 *1a  00  00  41  0f  ba  6a  4c *89  66  41  ff  8a  c4  01  00 ...A..jL.fA.....
...
fffff800030e0c40 *71  6d  40  8b  05  b7  43  1f *e7  89  85  0c  01  00  00  8b qm@...C.........
fffff800030e0c50 *17  e0  00  00  00  48  f7  85 *56  00  00  00  00  02  00  00 .....H..V.......
fffff800030e0c60 *b4  01  fb  b9  01  00  00  10 *41  02  00  00  00  44  8b  8d ........A....D..
fffff800030e0c70 *f5  00  00  00  41  81  e1  ff *68  00  00  4d  33  d2  4c  8b ....A...h..M3.L.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

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


Yesterdays crash file
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325e650
Debug session time: Tue Jul 26 08:02:02.640 2011 (UTC + 2:00)
System Uptime: 0 days 0:11:26.655
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.....
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 4686, 439d00008d1b}

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

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000004686
Arg4: 0000439d00008d1b

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  altbinz.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000302c79c to fffff80003098d00

STACK_TEXT: 
fffff880`0aba4ab8 fffff800`0302c79c : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`00004686 : nt!KeBugCheckEx
fffff880`0aba4ac0 fffff800`03096e2e : 00000000`00000001 00000000`03e40000 00000000`0008e301 00000000`000b2000 : nt! ?? ::FNODOBFM::`string'+0x4700d
fffff880`0aba4c20 00000000`77012373 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018f5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77012373


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4700d
fffff800`0302c79c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4700d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+4700d

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+4700d

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


Offline DariusIII

  • Contributor
  • ***
  • Posts: 49
I don't think that it is Alt.Binz related.Maybe Alt.Binz usage triggers the error, but i believe something else is at fault here.Probable cause are drivers on your system, and also possible cause can be:

Probably caused by : ntkrnlmp.exe witch according to Microsoft has to do with

CAUSE
This problem occurs if one or more of the processors in the computer:
•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions.


Btw, i have also windows 7 x64 SP1 and Alt.Binz runs without any problem so far.

Offline dacaid

  • Contributor
  • ***
  • Posts: 246
Where does Alt.binz download/unrar files? system disk, secondary disk or lan disk ?
Does it occur when downloading or unraring only or just idle?
Answering those 2 might lead you to an HD problem, if you're downloading to an old secondary HD or a too busy NAS for instance

Did you try to wipe your settings? maybe you're keeping an old setting file that make your OS crash, i had that once.


Offline Sc0rPi0n

  • Contributor
  • ***
  • Posts: 10
Re: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1
« Reply #3 on: August 24, 2011, 03:10:42 pm »
So in the meantime I installed Alt.binz 0.25 again (over 0.39.2) and applied the 0.39.2 update again.
Also set the memory speed to 1333 in stead of 1600

Since then no crashes at all.

I think it was because I re-installed Windows 7 on my SSD (Program folder of Alt.binz is located on a secondary hard drive)
Since re-install I would start the exe of alt.binz without the 'prober' way of installing alt.binz first.

Alt.binz installs and registers more files on the system then only the program folder I guess :)

First I thought is was the secondary hard drive so I bought a new disk but the BSOD still remains.
Well now I got 1,75 TB to spend on data  :D
« Last Edit: August 24, 2011, 03:13:31 pm by Sc0rPi0n »

Offline Rdl

  • Administrator
  • *****
  • Posts: 4050
Re: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1
« Reply #4 on: August 24, 2011, 06:09:07 pm »
I can guarantee that you don't need 0.25 'installer'
Installer just copies files in program folder. No registry (except for uninstallation), no system files.
Based on what you told us I still think it was h/w problem (memory speed)


Offline Sc0rPi0n

  • Contributor
  • ***
  • Posts: 10
Re: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1
« Reply #5 on: August 29, 2011, 11:19:21 am »
Weird because Windows Debugger points to altbinz.exe .

Anyway my system is quite stable now (thank god)

Offline Sc0rPi0n

  • Contributor
  • ***
  • Posts: 10
Re: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1
« Reply #6 on: October 26, 2011, 09:41:12 pm »
Still keep getting BSOD only because of Alt.binz.

Burned a DVD and letting Alt.binz download (did) nothing special (AFK) and suddenly my system reboots.

After reboot I debugged crash dump file and again point to altbinz.exe
Code: [Select]

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


Loading Dump File [C:\Windows\Minidump\102611-10748-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`03494670
Debug session time: Wed Oct 26 01:28:08.186 2011 (UTC + 2:00)
System Uptime: 0 days 1:59:46.201
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 421b, 3fd4000084ed}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000421b
Arg4: 00003fd4000084ed

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  altbinz.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033370fc to fffff800032cbc40

STACK_TEXT: 
fffff880`0c7059c8 fffff800`033370fc : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0000421b : nt!KeBugCheckEx
fffff880`0c7059d0 fffff800`032d919e : 00000000`00000001 00000000`067ee000 fffff880`0c705c20 fffff680`00033f70 : nt! ?? ::FNODOBFM::`string'+0x2a80f
fffff880`0c705ac0 fffff800`032c9d6e : 00000000`00000001 00000000`067ee000 fffffa80`0a5b8001 00000000`00010000 : nt!MmAccessFault+0x5de
fffff880`0c705c20 00000000`774d2373 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018f5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774d2373


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+2a80f
fffff800`033370fc cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a80f

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a80f

Followup: MachineOwner

Someone got any ideas?

Offline DariusIII

  • Contributor
  • ***
  • Posts: 49
Re: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1
« Reply #7 on: October 27, 2011, 11:43:53 am »
Alt.Binz triggers the error, but i still believe the fault is elsewhere. Check your drivers, OS updates and HW, the problem lies there.

Offline Sc0rPi0n

  • Contributor
  • ***
  • Posts: 10
Re: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1
« Reply #8 on: November 05, 2011, 01:40:45 am »
Hmm with 0.39.3 it got worse. BSOD 10 seconds after starting alt.binz and it started downloading.
moved back to 'stable' 0.39.2

Weird thing is that my system is quite stable and no other programs causes crashes till I start up alt.binz than is becames instable.

Offline Hecks

  • Contributor
  • ***
  • Posts: 2011
  • naughty cop
Re: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1
« Reply #9 on: November 05, 2011, 03:09:56 am »
And stranger still is that you're clearly the only user experiencing this problem.  BSOD on Windows invariably means driver issues. Obviously no other app uses your system - memory, network, CPU - in the way that Alt.Binz does.
« Last Edit: November 05, 2011, 03:14:33 am by Hecks »

Offline opentoe

  • Contributor
  • ***
  • Posts: 103
Re: Alt.binz (all ver.) crashes with Memory_management W7Ultimate x64 SP1
« Reply #10 on: November 05, 2011, 06:57:10 am »
Run AltBinz in safemode with networking support and see what happens.